This creates a lot of overhead to update a few specific components. Portal Data Updates are typically an “all or nothing” process, meaning you cannot just move specific web pages or other elements but must move everything.Duplicate Web Pages if you forget to shut off the Portal Web Page plug-ins.Missing relationships between records, which will cause portal errors and navigation issues.In my experience, I have found the following issues: There are issues and the tool is not designed specifically for Dynamics 365 Portals but rather Dynamics 365 configuration data in general (such as the unified service desk configurations). The process is outlined in this community blog posting. The “semi-official” (although described as unsupported) way to move Portal configuration data is via the Configuration Data Migration tool. The downside is that the portal metadata stored as Dynamics 365 records means that it is not solution aware and it is difficult to transfer the portal configuration from one system to another, for example, from a development or test portal to a production portal. This provides a high level of configuration options when building a website that needs to expose Dynamics 365 data to external stakeholders. Dynamics 365 Portal ConfigurationĪnyone that has worked with the Dynamics 365 Portal knows that the portal configuration data is stored in a series of portal-specific entities in Dynamics 365 such as websites, web pages, web templates, entity lists, entity forms, content snippets, etc. If you want to see this in action, check out my contribution to the CRM MVP YouTube Channel here. The XrmToolBox Portal Data Mover has been recently updated and when used correctly is an easy-to-use method to copy portal configuration data.
Semi-official method of using the Configuration Data Mover has potential to leave gaps and data and other pitfalls.There are challenges copying Dynamics 365 Portal Data from one instance to another due to the complexity of the entity structure.
0 kommentar(er)
