Tool or utility to assist in reparenting of records
+4Customer/Engagements frequently move from 1 Salesforce Account ID to another Salesforce Account ID; we require a utility to help us move Relationship records to new Customer 360/Customer Info/Account records, including downstream update of child objects like CTAs/Timeline Activities/Scorecard histories. Need the ability to truly re-parent a Relationship record + all detail data, not just create a new record and manually transfer data over.
VMware has requested this as well.
+4This will likely be important for Autodesk, who has a very complex customer definition that is governed by another object (Enterprise Agreement) - it means the list of accounts related to it can change, merge, or be deleted more frequently that a model where an account is at the very top of the pyramid.
At Cisco, right now, when relationships need to be "moved" to other account record, we have to:
1. Create the new relationship
2. With rules engine, write all the GS Relationship attribute values on the old relationship to the new relationship. Run scorecard rules to set current score. Manual copy/paste scorecard comments and other long text fields to the new relationships.
3. Via rules engine or reports, download CTAs to a CSV, update the Account AND Relationship IDs in the lookup fields to the new IDs, then upload as new CTAs with an API Loader. Also includes a field to Call to Action called "old CTA ID to maintain the mapping.
Manually move long comments.
4. Now that we have new CTA IDs, output all the playbook tasks associated with the old CTAs, use VLOOKUP to post in the new CTA and Account and Relationship IDs, and then upload.
5. Manually copy timeline entries into new timeline entries under the new relationship.
6. Submit ticket to update the mapping on Scorecard history on MDA to the new Relationship.
7. Delete the old relationship.
8. Submit a ticket to have the old relationship, and sometime the old account, deleted from the standard objects.
Any short term ideals would be great - I know Sidhu's looking into allowing reparenting of Relationships, CTAs, etc. but help in the short term would really incur some good will:
Maybe enabling all fields for Load to SFDC on our Call to Action object so that when the new one is created (or even run it as an insert), the old CTA fields, including comments, can be queried and then applied to the new Relationship.
Can't believe I typed all that, but wanted to walk you through why this is a constant drumbeat from Cisco, and will come up more with both Enterprise SFDC users, and Enterprise on Native.
Have a good night!
At Cisco, right now, when relationships need to be "moved" to other account record, we have to:
1. Create the new relationship
2. With rules engine, write all the GS Relationship attribute values on the old relationship to the new relationship. Run scorecard rules to set current score. Manual copy/paste scorecard comments and other long text fields to the new relationships.
3. Via rules engine or reports, download CTAs to a CSV, update the Account AND Relationship IDs in the lookup fields to the new IDs, then upload as new CTAs with an API Loader. Also includes a field to Call to Action called "old CTA ID to maintain the mapping.
Manually move long comments.
4. Now that we have new CTA IDs, output all the playbook tasks associated with the old CTAs, use VLOOKUP to post in the new CTA and Account and Relationship IDs, and then upload.
5. Manually copy timeline entries into new timeline entries under the new relationship.
6. Submit ticket to update the mapping on Scorecard history on MDA to the new Relationship.
7. Delete the old relationship.
8. Submit a ticket to have the old relationship, and sometime the old account, deleted from the standard objects.
Any short term ideals would be great - I know Sidhu's looking into allowing reparenting of Relationships, CTAs, etc. but help in the short term would really incur some good will:
Maybe enabling all fields for Load to SFDC on our Call to Action object so that when the new one is created (or even run it as an insert), the old CTA fields, including comments, can be queried and then applied to the new Relationship.
Can't believe I typed all that, but wanted to walk you through why this is a constant drumbeat from Cisco, and will come up more with both Enterprise SFDC users, and Enterprise on Native.
Have a good night!
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.