55
Hi,
When mapping an optionset on a virtual entity to its external data source got the following error:
Type mismatch of the external attribute of type sysyem.nullable[system.int32] expected a system.nullable[system.int32, microsoft.xrm.dataprovider.odata614d0bd27de7e9119c27005056876672
Unfortunately there are not so mucj documentations on virtual entitis optionsets!
Did you ever get this optionset mapped correctly?
my question is after they enabled CRUD on the Odata v4 Provider, are you able to change optionset values when updating this table?
Hello, while int32 is a supported type, it cannot be used for option sets. Int32 is only for numbers.
docs.microsoft.com/.../virtual-entity-odata-provider-requirements
In order to map an option set in CRM, you need to use an enumeration in your OData and then map all the options in your option set field.
<EnumType Name="MessageType" IsFlags="true">
<Member Name="Unknown" Value="0" />
<Member Name="Incident" Value="1" />
<Member Name="PlannedMaintenance" Value="2" />
<Member Name="MessageCenter" Value="4" />
</EnumType>
We did not use a custom provider. The external database were exposed as web api over oData. The type of data we are mapping is Int32 and mapping it to an optionset in CRM. According to MS documentations this type is supported, but there are no samples to show how to map an optionset.
Hello,
For these types of errors, it's either a problem with the mapping inside of CRM, or if you are using a custom provider, then it could also be a code problem.
Could you share more details about your scenario and configuration ?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (