Hi,
tldr: schema is created, now initial deployment form Portal A to Portal B is causing issues.
So I made my first steps with Configuration Migration Tool, seems to be straight forward:
1. Create schema including affected entities
2. Export data from source system using this schema
3. Import data from source system to target system using this schema
But how do you actually handle a full snyc between two individual Online Portals when you start with the highest level, i.e. the website record?
- Portal (A) of D365 organisation (A) has a Website record (A) - that record could be something like "Partner Portal" with an unique GUID in D365 organisation (A)
- Portal (B), e.g. an additionally purchased Portal based on monthly subscription in the same O365 tenant of D365 organisation (A), of D365 organisation (B) has a Website record (B) - that record could be something like "Partner Portal" with an unique GUID in D365 organisation (B)
- If I now copy over the complete configuration from (A) to (B), a new website record for (A) will be created alongside of (B), i.e. in D365 organisation (B) I now have to website records - each website record points towards a different URL
So for the very first deployment from (A) to (B), is it necessary to clear all configuration data from (B) and then importing all configuration data from (A) to (B)?
After this initial deployment, the GUIDs of the website records should match, so incrementel updates should not cause any issues.
OR
Do you
- export data from (A)
- go into the exported XML of (A)
- manually manipulate the GUID of website record (A), so the GUID in XML of (A) becomes the GUID of webiste record (B)?
Again, I am looking forward to exchanging best practices with you when it comes to deploying from one online Portal to another.
Thanks and best regards