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
When exploring version 9+ of Dynamics 365 there are a ton of new changes. When I seen the changes to the global option set I just knew I needed to understand these changes.
Let's examine the new option set window first.
The two new fields are primarily used for integration stories:
When I think of some of the struggles with mappings external data sources to properly align to the Dynamics CRM option set values it can be a real pain at times. This really brings this story together allowing for the mapping to happen inside of Dynamics CRM in a single location. It's a time saver as you now will only have one spot to validate the mappings.
I hope this sheds a bit of light on the new global option set fields.
I have the same challenge with ODATA, have you found out ?
Some characters have been cut off. So the request is:
Would like to retrieve External Value "DE" with the same requet
Thanks for this good post. If a custom field on an entity is based on the OptionSet. Do you know if its possible to get the External Value with the OData request?
With the following exmaple, OData request: xxx.crm4.dynamics.com/.../accounts()$select=accountid,accountnumber,name, i get
But it would like to retrieve External Value, e.g. DE as well. Is this possible? Do you have an example how the OData request must look like
Business Applications communities