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 by Microsoft - https://www.microsoft.com/en-us/download/details.aspx?id=55789).
Microsoft announced in an article that some important changes are coming out with next major release (Link: https://docs.microsoft.com/en-us/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming ). It is written that some client APIs will become deprecated. I've found out mentioned APIs are also used in web resources related to Dynamics CRM Portal (web resources with ADX prefix). For example Xrm.Page is used in: adx_ace\ace.js , adx_adx.js, adx_annotations\adx.annotations.js
How will changes from next major release affect to on premise portals? Do we have to reprogram adx web resources to provide Customer normal functioning of their existing portal after major release? What is the best praxis for solving problems like this? Will Microsoft release another open source version where these problems will be solved?
Thank you in advance. Best Regards,
it is very unlikely that MS would release a new open source version, their focus is on D365 Online Portals (now been re-labeled as Power Apps Portals)
the JS library mentioned is deprecated since 2017 but MS still didn't mention when that is actually going to be removed from Dynamics CRM
the JS will have to be updated to reflect the changes into the APIs, it would be very nice if the community updated the code within GIT Hub, but as the solutions are by default in a Managed state, I think each one would have to copy that code (again if shared) and paste into your own D365 environment
Thank you for your answer. Probably the best option for our customers is to migrate from self hosted portal to online version. I've seen a comment on MS page that XRM API was removed from list with items that will be deprecated with next major release. This API is widely used in managed solutions developed for example by company PowerObjects or other companies. I think PowerObject or company that developed a solution should upgrade the code. That is the only leggit way. Am I right?
yes.. any company that sells add-on products for D365 is already updating their solutions, but in the case of Community Portals nobody really owns it
Microsoft released for the community, so it is up to people willing to make the changes and share now
Thank you for your explanation.
Business Applications communities