Breaking news from around the world
Get the Bing + MSN extension
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
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
Hi everyone, I have Dynamics 365 Online.
I have an entity called TrialEntity that has two field on the main form, let's call them A and B.
An onchange event is triggered on A, and a webresource opens. The webresource allows users to choose a value from a drop down list and to press a Submit button. On that button click the chosen value must be inserted in the B filed on TrialEntity.
I can't figure out how to do this except from using code shown below
parent.Xrm.Page.getAttribute("B").setValue("*value retrived goes here*");
Unluckilly the previous line of code is not working since the GetAttribute gives me a null object as return. Can someone give me a piece of advice on how to update?
Are you sure that field "B" exists? Because I replicated that scenario on my trial environment and it went ok, I put a webresource on Account's form and update "fax" attribute from there, like this:
var test = parent.Xrm.Page.getAttribute("parentaccountid");
And it updated ok.
Acutally I think i am missing that ClientGlobalContext.js.aspx script, let me try really quick and I'll reply again! Ty so far btw
Wait I forgot a "little" particular. This happens when a new record is created and the popup is created BEFORE data savings, so the record does not exists.
That's not a problem, supposedly. You are not manipulating guids, just fields on the form. The form exists and that's your context. I've just try it on the create of the record and it worked fine. Check if the ClientGlobalContext.js.aspx script has the right path. Sometimes it's the root folder but other times it's the previous one, like this:
My first question would be, could you re-design the process?
Without knowing what your webresource does its tough to know if this is feasible... Short term, field B could just be that option set, and the user may have to select it once in the webresource, and then again in field B.
Hope this helps,
Business Applications communities