Has anyone successfully themselves, or via any lev...
# general
j
Has anyone successfully themselves, or via any level of NS Support, had the primary subsidiary changed on Customer or Vendor records?
e
A long time ago, using Merge functionality. Not sure if it is still possible or full of gotchas.
j
ooh
r
Yeah I've done that too. Definitely check me in a Sandbox, but I believe the process is: 1. Build a "shell" record with the subsidiary you want to switch it to, but with basically no other information on the record that's not required 2. Merge with shell record as the "main" record or whatever it calls the record to keep 3. The merged record will take the subsidiary from your new shell record and will pull in any information from the existing record where the field was blank on your shell 4. Manually (probably) clean up any data that was conflicting (may not be needed) I don't think there's a way to do this en masse though. Maybe via the API or script if you have a bunch of them. I think it takes the Int ID of the shell record since you're calling that the parent, so if you have anything keying off of Int ID, you'd need to deal with that.
Oh yeah and it then adds the subsidiary that was on the existing record as an available subsidiary on the subsidiary list if you have multi-customer on.
j
I tested the above and it does as you describe
Yeah we have all subsidiaries on all Customer records, problem is we will have cases against those customers for multiple Subsidiaries and need a team of people who can work on them…..
So we are thinking to make a subsidiary for “master data” and keep customers/vendors with that as their primary, then all cases can live under that.
s
You can do mass merges using the duplicate detection feature. It's a bit fiddly but I've done it with a similar use case - we created a fulfilment subsidiary and wanted all customers to have that as their primary. there are step by step guides around.