We've got a OneWorld account with multi-subsidiary...
# general
a
We've got a OneWorld account with multi-subsidiary customers. I set up a customer with a primary subsidiary of X, and create a child customer - the child customer automatically is given primary subsidiary of X and the primary subsidiary field is greyed out. If I try to change parent customer's primary subsidiary, I get an error that the parent and child subsidiaries must be the same... but I can't change the child subsidiary either as it's still greyed out. Seems like I'm stuck in a loop, has anyone run into this before? The only way I can figure to change the subsidiary would be to delete the parent/child relationship, change the parent customer sub, and then re-attach the child to the parent. But that would be super inconvenient, so i'm hoping someone else has a better way?
k
I am guessing they have consolidated payments turned on, in which case what you want to do cannot be done no matter how you want to try and do it.
Also, with consolidated payments turned on multi subsidiary customers Is not an option. They are fundamentally incompatible.
I would suggest creating a custom field for managing this reporting requirement
Read your post one more time, realized you are using multi sub customers and I am not tracking why you care about primary subsidiary in this case.
a
thanks @KevinJ of Kansas! i agree that primary sub doesn't matter that much but since it determines the default on a transaction they want to update it. i appreciate the info about consolidated payments, that's helpful to explain to them rather than me just saying "i dunno, just how NS is" haha.
k
To clarify my first messages were wrong
You are using multi subsidiary, which you are, they can't use consolidated payments
You could probably custom field this with a script or workflow
a
hmm consolidated payments seems to be enabled in their account right now, along with multi-sub. do you mean that the functionality just won't work if they try to use it?
suiteanswers is saying "Currently, it is not possible to use the Consolidated Payment featureĀ if there are parent and child customers in different subsidiaries" - i'm wondering if we had consolidated payments turned on from the start so it just prevented us from having parent/child customers in diff subs to maintain that functionality?
k
I must have missed the patch of that. It used to be turning on one prevented the other
Sound like maybe turning off consolidated payments should help
a
yeah, unfortunately that is a hard requirement to have consolidated payments so they're just gonna have to deal. like you said, it doesn't really matter since they're all multi-sub (and a script automatically applies all subsidiaries to all customers) so they can have transactions in any sub they want regardless of the parent/child primary sub.