Small and medium business | Business Central, N...

Creating BC drop down fields for synching to Dataverse (Dynamics Sales)

(0) Share

Report

Posted on by Samantha73

2,453

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:

field(10133; LeadSourceCode; Option)

{

ExternalName = 'leadsourcecode';

ExternalType = 'Picklist';

Description = 'Select the primary marketing source that prompted the lead to contact you.';

Caption = 'Lead Source';

InitValue = " ";

OptionMembers = " ",Advertisement,EmployeeReferral,ExternalReferral,Partner,PublicRelations,Seminar,TradeShow,Web,WordOfMouth,Other;

OptionOrdinalValues = -1, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10;

}

All responses (3)

Answers (0)

Samantha73 2,453 on at

Like (0)

Report

RE: Creating BC drop down fields for synching to Dataverse (Dynamics Sales)

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
Suggested answer

Nitin Verma 21,091 Super User 2024 Season 1 on at

Like (1)

Report

RE: Creating BC drop down fields for synching to Dataverse (Dynamics Sales)

You can use ENUM fields when trying to Sync from CE to BC.
Suggested answer

Francisco Bedolla 1,117 on at

Like (1)

Report

RE: Creating BC drop down fields for synching to Dataverse (Dynamics Sales)

please check

docs.microsoft.com/.../admin-cds-missing-option-values

HTH