Personalized Community is here!
Quickly customize your community to find the content you seek.
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 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 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
I'm having an issue and I don't figure out what could be.
at line 9 sometimes says "it can't read property addOnChange of null" but the field "rs_principal" exists and I'm not writing wrong, because sometimes it works well. (refreshing f5) even in other devices.
I'm using chrome. but with another browser happens the same , sometimes works other not.
Can anyone help me?
Dynamics 365 Online
Server Version: 9.1.0000.7625
Client Version: 1.3.2119-190813-224452
Can you see if changing from Xrm.Page.getAttribute to formContext.getAttribute changes the behavior?
Take a look at the following link for using the new Client API reference:
Hope this helps.
Hi Aric Levin,
Yes, the behavior changes, Idk why on common Interface works well but it seems that in Unified Interfaces forces you to pass a context because of Xrm.Page is obsolete. Thank you.
Xrm.Page is deprecated syntax and therefore will throw errors in UCI, if you change this to formContext it should change the behaviour as it is supported syntax.
Business Applications communities