From time-to-time, Ledgeview sees customers who end up getting surprised by how an action they apply to a record, affects the related records.
A common example of this would be re-assigning an account and how it affects the ownership of the related contacts.
By default, this relationship is configured as a Parental relationship, so in this scenario, all the related contacts are also assigned to the new account owner.
In many instances, this is the desired outcome, but in some cases, you’d rather keep the contact ownership the same.
Luckily you are not locked into this behavior if it doesn’t suit your organization’s needs.
In the customization’s area under each entity, you’ll see the lists of 1:N relationships and N:1 relationships. In the earlier example you would find the relationship under 1:N, and then you’d be looking for the relationship whose parent entity is account and related entity is contact.
Once you’ve opened that up you can see the type of behavior for the relationship is configurable. In this case, we can change the behavior from Parental to Configurable Cascading.
This would allow you to alter the Assign behavior to another option so it doesn’t update the owners of the child records.
Here are the options that are available, but keep in mind that not all types are available for all relationships in the system.