Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Hi all,I wish to have 2 environments for 1 Dynamics 365 portal.The first environment would be a portal attached to a sandbox CRM instanceThe second one would be the production environment.As the portal uses CRM solutions, sandbox and prod does not pose any particular problem...However, how do you migrate the record setup data from the SANDBOX portal instance to the production CRM instance?Do we use "migration tool" from SDK or the ADX studio tool (copy site)
Thanks by advance!
Yes, Configuration Migration tool would be the best option to migrate the data from sandbox to production as it maintains the same Guidbetween the environment.
Check the below links-
As of now, Configuration Migration tool is the best way to do portal deployment.
You can go through my below article to get detailed steps for the same :
Thank you for your opinion. I tested this a few weeks ago and I have a problem when the pages are displayed: no css seems to be used. The security is checked and I have not seen anything in default.
Configuration Migration Tool is best option to move records from one instance to another.
But with more advantages and benefits ,"Portal Records Mover" tool available in "XrmToolBox" is the best tool for deployment ( though it is third party application). It has following benefits over the Configuration Migration Tool.
1. You can deploy records for specific portal only ( if multiple portals are installed for your instance)
2.You can deploy specific records created or modified after particular date
3.You can deploy only active records
To open tool - > Go to XrmToolBox -> Search for "Portal Records Mover"
Please mark as answer if you find this post helpful.
It's official now:
Have a look MS article.
We use Portal Record mover for a few deployments, and tend to move complete groups of entities by creating a settings file for the objects we are using, and not for any of the time based entities (like history, logging …)
The main thing to watch out for is that it does not do "deletes" on the target, so if pages or meta data are deleted then they will need deleting on target.
Business Applications communities