Announcements
Hi All
When creating new fields in BC we select ENUM as type since OPTION will be deprecated in the future. However, when I look at CRM sync tables in BC, they use OPTION. So the question is should we use Enum or Option when creating new fields that need to be synched to Dynamics Sales
For example, code from Lead CRM sync table field in standard BC:
For a custom field new function Dataverse Option Mapping front end page is not available (only for 3 std entities payment terms, shipment method, shipping agent)
So you still have to manually create ENUM that match dataverse if you create custom fields. Is there a way to automatically create option field values in Dataverse if we add a new value in BC? For example for the option colour I have RED,GREEN. Now in BC I add BLUE and I want the BLUE to be added as value in Dataverse
You can use ENUM fields when trying to Sync from CE to BC.
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156