January Problem Solver of the MonthCongratulations to Sourav Dam for be selected in our monthly random drawing, Dynamics Community Problem Solver Sweepstakes.
Read aboug Sourav | Learn how to enter
2020 release wave 1 Discover 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 Timeline
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 am currently writing a plugin and want to set a field. I can read the field from the opportunity but I cannot write it back somehow. Here is the code:
// global class variableprivate const string FieldName_CloneFlag = "pref_cloneflag_boolean";
// [...some more plugin code to retrieve the entity...]
// check the clone flag...
tracingService.Trace("CloneFlag = false... Leaving now.");
tracingService.Trace("CloneFlag = true... Setting to false now.");
// remove the clone flag...
Entity e = new Entity(entity.LogicalName);
e.Id = entity.Id;
tracingService.Trace("attempting to update now...");
The result in the Plug-In Trace Log is as follows:
CloneFlag foundCloneFlag = true... Setting to false now.attempting to update now...PluginClone Exception: 'opportunity' entity doesn't contain attribute with Name = 'pref_cloneflag_boolean' and NameMapping = 'Logical'.
What is weird for me is that I can chose the field in the PluginRegistration toll as filter and read its value in the code. What could be the reason why CRM thinks that the field does not exist?
It seems like a crm issue and I have seen few thread now where CRM is not able to find the fields which actually exists.
Check this thread: community.dynamics.com/.../857035
Thanks for the link. Seems really like there is a new problem with publishing-related caching. Just yesterday I published an updated business process (for another customer) and the changes just did not want to show up on the form. Somehow, a couple of hours later, it worked.
I guess I give it some time and check back later.
Yup, I remember there was another thread which claims that it took 3 hours to appear the new field in plugin. Worth trying after some time. If this doesn't fix teh issue then I guess the best option si to contact Microsoft support as they can confirm if this is a bug or not (if you are sure that the field with the same schema name does exists in the system :) )
It does as I can
Pathetic. Blame the metadata cache in server side.
Yo can try this: Settings - Customizations - Customize the system (Default solution) - Publish All customizations.
This will iron out any wrinkles.
Which region your CRMOL is in? Like crm, crm5,crm8.
It's not like I have not tried to publish - both the custom solution as well as the default solution.
The issue of this case it that exactly that does not work.
The region is CRM4 and the version is: 1710 (220.127.116.1146) online
It works after the weekend so it is very likely something cache related (server side).
Business Applications communities