Skip to main content

We’ve recently acquired a company and I am in the process of migrating their setup to our main GS environment. I am trying to use X-Org 2.0.

 

The first issue I ran into, currency issue, has been resolved. However, now I am trying to migrate one simple playbook at the relationship level. I built out a bundle in X-Org 2.0 and all of a sudden I have hundreds of dependencies popping up, in reality it is like 18 for one simple playbook.

 

 

I have the exact same relationship type and the CTA type is objective that certainly exists in both. There are not custom fields on the layouts so nothing needs to be synced for that.

 

Even if that was the case explain why these need to be synced;

Relationship Type Category: this playbook has nothing to do with this field

User Object: Why? There aren’t any custom fields?

Scoring Scheme Definition: Seriously? When do playbooks have anything to do with this object/feature?

 

I am not going to list out all my complaints. However, one of the main ones I have an issue with is Customer Stage/Status. I once added a dropdown as a dummy test in our sandbox org. Then when I migrated a rule it got brought over, even though it was not being used anywhere and now we are stuck with it in our prod environment.

 

What happened to the delta process? I did this same test migration in the old X-Org and you know what gets migrated? Just the playbook, nothing else.

 

At bare minimum you should at least allow us to unselect erroneous dependencies we know won’t fail when we run the migration.

 

 

Love that last point especially, but all of these. If you break that one out, I will upvote it like crazy (read: recruit people to upvote it).


Reply