Portals 365 deployment with DMM 365: recipe of granular Portal deployment using Saved Views as filters
Given:
Deploy specific Webform Steps and and specific Webform
Metadata.
Conditions:
modified since last deployment on
31 of August for Portal X
exclude Webform Step “Step6”
Prerequisites:
DMM365 connected to source CRM instance has rights to
read required Saved views, Site Settings and Web Files entities.
DMM365 connected to target CRM instance with rights to writeSite Settings and Web Files entities.
DMM365 connected to target CRM instance with rights to writeSite Settings and Web Files entities.
1.
Backup your Target instance with Dynamics 365
Admin pane, Create backup
2.
Create Saved View in source crm instance:
View for Webform Steps.
Conditions:
-
Modified on or after 1 of September
-
Parent portal “Portal X”
View
for Webform Metadata. Conditions:
-
Modified on or after 1 of September
-
Parent portal “Portal X”
-
Step name is not equal “Step 6”
NOTE:
You can create a
separate view/s to excluded entities with more sophisticated algorithms. In
this case utilize “Reverse (Exclude Results)” option to exclude from result
set.
3.
Export whole portal with Configuration Migration
tool.
4.
Run DMM365 tool. Create project based on
exported package and connection to source crm.
5.
Select Webform Steps and Webform Metadata in
“List of Entities in Schema file”. Multi selection is supported.
6.
Select (click) “Webform Metadata” and available
views will be displayed in “List of Public Saved views”
7.
Double click a required view to move it to
“Select View to Set Import Settings”. If you need more view – double click on
each.
If you need to remove view from “Select View to Set Import Settings” –
double click.
8.
Select (one click) view in “Select View to Set
Import Settings” to see its fetch in “Query Display”.
Some fetch nodes were modified to be more informative. Don’t worry,
original view fetch is not affected.
Once view is selected you may set “Reverse” option if necessary.
9.
Once you done with views related to “Webform
Metadata” related views execute same steps for Webform Steps.
10.
Press “Modify and Save Data” button when you’re
ready. Folder with package ready for import will be opened.
11.
“Process Records Monitor” allows you to check
which and how many entities were moved to import package.
12.
If you’re satisfied, import package to Target
Crm instance.
NOTE:
Before update you can backup specific target pages using
same steps.
NOTE:
In real life you may have a limited number of views for day
to day deployment. Don’t Forget to change filters parameters in the view!
NOTE:
If you’re updating Web File entity or any entity with
updated Attachments please use “Portals365 Sync” tab to copy new attachment to target. See Portal deployment with DMM365: recipe of duplication.
Happy engineering :)
Comments