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
some of our customers are using Self-hosted Dynamics 365 Portal (official open source release from Microsoft). Link to portal solution download page: https://www.microsoft.com/en-us/download/details.aspx?id=55789
I've found an article on internet about important changes coming out with next major release related to Dynamics 365 Customer Engagement. Link to article: https://docs.microsoft.com/en-us/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming
In this article is written that some APIs will become deprecated (for example Xrm.Page). I've found out these APIs are also used in web resources with adx prefix, so our customers will have to upgrade their portal to online version.
For example Xrm.Page is used in: adx_ace\ace.js , adx_adx.js, adx_annotations\adx.annotations.js .
What is the best way to migrate from open source MS Portal to online version without destroying customizations made by our company?
I predict that solution components for Dynamics CRM online portal are different from components included in current open source portal solution? What is best praxis to do migration?
Thank you in advance!
hello again Matej
first, you need to identify any changes made within the Portal source code, and see how (if possible) you can migrate those to a D365 Online Portals
in regards the Portal components itself, there is no major difference on how we make customization like creating entity list / entity form / metadatas / etc.. so this is all easy to migrate
I suggest you create a trial environment and push your portal data into it (as well as your custom entities/solutions etc)... so you can identify any possible gaps
The official guidance from Microsoft on moving from self-hosted to online can be found at cloudblogs.microsoft.com/.../migrate-from-adxstudio-7-to-portal-capabilities-for-dynamics-365
Long story short, you need to be on the open-source version of the code (so you have to upgrade if you're on Adxstudio v7), and then you can ask Microsoft to switch you over to the online version. The key is that you can't customize any of the code in the MasterPortal project. This is the code that Microsoft hosts for you, and you can't change. So if you have any functionality that involves editing that code, it will have to be reimplemented using either out-of-the-box features, or you'll need to do something like a Companion App to build out the features.
Hope that helps.
Thank you both for your help and answers. We are using open source version of portal with no major changes in code. All portal customizations were made within CRM (entity lists, web templates, etc..).
Business Applications communities