Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Can you please let me know I am developed a new SSRS report with using DP Class. I want to move my entire report in to UAT server.
Please let me know how to move SSRS report from one environment to another environment.
Please give me more she'd on this
There are different options for example deployment through XPO, model files etc . You can follow any one of those, For SSRS reports XPO is also fine . If you are moving through XPO , just make sure you take all the objects.
You can try following steps:
1. Export related tables, Contract class, RDP class as XPO files for MorphX;
2. Export the SSRS report Project from Visual studio;
3. Import the XPO files and build them;
4. Import the VS project, build and deploy the SSRS report.
.xpo files aren't intended for code deployment.
A model deployment is likely the right choice in this case. Make sure you read Deploying Customizations Across Microsoft Dynamics AX 2012 Environments; it contains many important details.
I also strongly recommend that the model file is generated by a build server. It guarantees that all code is coming from version control and it allows traceability.
If people just take some objects (which don't have to be in version control) and put them to UAT, chaos I guaranteed. Nobody know what's been deployed and what not, there may be changes not existing in version control (and lost in case of a failure), .xpo can't transfer information about object deletes (therefore objects deleted in DEV will be kept in UAT) and so on.
Business Applications communities