450
Not what I want to happen. I recently wanted to move 100 or so accounts over to a different reps name...but in doing so, all the previous notes, calls, emails, etc have switched to the new reps name. This is not good for tracking past interactions and experiences with the customers. Any suggestions?
Thank you
*This post is locked for comments
FYI to anyone in the future finding this thread, use the "Activity Cascade Rules" tool in XRMToolbox to easily and quickly change the Reassign cascade rules. Worked great for me!
Hi Scott, sorry for my late answer, crazy work weeks!
Umm, I fix it changing the configuration of the relationship between the entities Account and Appointment as @Jerry suggest me to do it in the above post.
In your case I'll look at the entity Calls and change the configuration of all the relations with the Activities entities (Appointmet, Phone Call, Emails, Tasks, ...) to work in cascading accordingly with your requirements.
I hope my suggestion help you to fix your issue
Victor, sorry I know it's nearly 2 years later, but I seem to be having this exact same problem. Did you ever sort it out?
My scenario:
Intention: all cases are to be owned by the TEAM, not USER. When a user PICKS or ROUTES the case from the Queue, the ownership of the Case was going to the Picking user (or the Routed To user). As this was undesirable, we created a workflow that would automatically assign the case back to the Team. However, because of cascading, the first PICK/ROUTE updates all associated activities to be owned by the PICKING or ROUTED TO user (expected, based on Cascade All setting on Assign), BUT, when the workflow fires and assigns the Case back to the Team, it does NOT cascade the assignment to the Activities, oddly. This means the Activities may now be owned by individuals and not visible to other users on the Team.
I'm very curious how you resolved this issue.
I have a similar situation here, the first time when I assign the Accounts to a different user, all the activities was automatically assigned to the same new owner of the Account. however for the second time in front the activities don't change the owner. Could you provide me information that if this is the normal behavior or if I have some issue here.
Thanks.
Change to "Cascade None"
I have the same issue, when I change the ownership of a account to a different user. The activities changes to the user who made the change in this case to me.
I have edited the relationships for the all of the six actions for all activates type (email, phone call, etc..) to Cascade Active and have published the changes, but the behavior is the same. For example, Account_Appointments-1:N, I changed relationships behavior to configurable cascading and then changed Cascade Active for all the six actions (assign, share, etc.. delete and merge are grayed out for me.
Any help on this will be appreciated.
Thank you,
Ankit
This is a due to the cascading settings. You will need to go into Customizations - Account Entity and then look at the 1 to many relationships for each of the related entities - notes, etc. Change the Type of Behavior to Configuable Cascading. And then change the Relationship behaviors.
From the help system.
Configurable Cascading (Any action taken on a parent entity record can also be applied to any child entity records that are related to the parent entity record. You can define the behavior for each type of action. For example, you can set it up so that if you share a record in the parent entity, any related records for the child entity are not automatically shared. But if you delete a parent entity record, any related child entity records are automatically deleted.)
If you selected the Configurable Cascading relationship type, for each of the six actions listed below, you can select the behavior for the action.
If you set all the behaviors for the actions to match the behaviors for the actions for the other relationship types, when you save the relationship, the type of behavior is automatically set to the other type. For example, if you set all the actions to Cascade All, the relationship type is changed from Configurable Cascading to Parental.
Assign (The related records will be assigned to the same user.)
Share (The related entity records will also be shared with the same user or team.)
Unshare (The related entity records will no longer be shared with the same user or team.)
Reparent (If the owner of the primary entity record changes because the primary entity record was reparented, the owner of any related records will be set to the same owner as the primary entity record.)
Delete (The related records can be deleted, unlinked from the primary entity record, or the delete action can be canceled.)
Merge (The related records associated with the subordinate record will be reparented to the master record.)
The behaviors for these actions include:
Cascade All (Apply to all related records.)
Cascade None (Apply to no related records.)
Cascade Active (Apply to active related records only.)
Cascade User-Owned (Apply to related records if they are owned by the same owner as the owner of the parent record.)
Remove Link
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
