{"title":"Handling missing option values","url":"https://jonas-paprotka.de/docs/admin-cds-missing-option-values/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/admin-cds-missing-option-values, MicrosoftDocs/dynamics365smb-docs at 46907ac (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/admin-cds-missing-option-values","source":{"name":"Business Central application docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-docs","commit":"46907ace177f8d31deba47a2fdb57c3336e66252","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn how to prevent full synchronization from failing because the options differ in mapped fields. This process requires help from a developer.","date":"2024-09-16","meta":{"topic":"how-to"},"outline":[{"level":1,"title":"Handling missing option values","slug":"handling-missing-option-values","at":0,"chars":5620},{"level":2,"title":"Extending option sets in Business Central","slug":"extending-option-sets-in-business-central","at":2772,"chars":1011},{"level":2,"title":"Update Dataverse option mapping","slug":"update-dataverse-option-mapping","at":3783,"chars":1592},{"level":2,"title":"Related information","slug":"related-information","at":5375,"chars":245}],"text":"# Handling missing option values\nThis article is intended for a technical audience. The processes it describes require the help of a developer.\nDataverse contains three option set fields that contain values that you can map to Business Central fields of the Option type for automated synchronization. During synchronization, nonmapped options are ignored and the missing options are appended to the related Business Central table and added to the Dataverse Option Mapping system table to handle manually later. For example, by adding the missing options in either product and then updating the mapping.\nThe Integration Table Mapping page contains three fields that contain one or more mapped option values. After a full synchronization, the Dataverse Option Mapping page contains the nonmapped options in the three fields.\nRecord|Option Value|Option Value Caption\nPayment Terms: NET30|1|Net 30\nPayment Terms: 2%10NET30|2|2% 10; Net 30\nPayment Terms: NET45|3|Net 45\nPayment Terms: NET60|4|Net 60\nShipment Method: FOB|1|FOB\nShipment Method: NOCHARGE|2|No Charge\nShipping Agent: AIRBORNE|1|Airborne\nShipping Agent: DHL|2|DHL\nShipping Agent: FEDEX|3|FedEx\nShipping Agent: UPS|4|UPS\nShipping Agent: POSTALMAIL|5|Postal Mail\nShipping Agent: FULLLOAD|6|Full Load\nShipping Agent: WILLCALL|7|Will Call\nThe content of the Dataverse Option Mapping page is based on enum values in the CRM Account table. In Dataverse, the following fields on the account table are mapped to fields on the customer and vendor records:\n Address 1: Freight Terms of data type Enum, where values are defined as follows:\n```al\nenum 5335 \"CDS Shipment Method Code\"\n{\n    Extensible = true;\n    value(0; \" \") { Caption = ' '; }\n    value(1; \"FOB\") { Caption = 'FOB'; }\n    value(2; \"NoCharge\") { Caption = 'No Charge'; }\n}\n```\n Address 1: Shipping Method of data type Enum, where values are defined as follows:\n```al\nenum 5336 \"CDS Shipping Agent Code\"\n{\n    Extensible = true;\n    value(0; \" \") { Caption = ' '; }\n    value(1; \"Airborne\") { Caption = 'Airborne'; }\n    value(2; \"DHL\") { Caption = 'DHL'; }\n    value(3; \"FedEx\") { Caption = 'FedEx'; }\n    value(4; \"UPS\") { Caption = 'UPS'; }\n    value(5; \"PostalMail\") { Caption = 'Postal Mail'; }\n    value(6; \"FullLoad\") { Caption = 'Full Load'; }\n    value(7; \"WillCall\") { Caption = 'Will Call'; }\n}\n```\n Payment Terms of data type Enum, where values are defined as follows:\n```al\nenum 5334 \"CDS Payment Terms Code\"\n{\n    Extensible = true;\n    value(0; \" \") { Caption = ' '; }\n    value(1; \"Net30\") { Caption = 'Net 30'; }\n    value(2; \"2%10Net30\") { Caption = '2% 10; Net 30'; }\n    value(3; \"Net45\") { Caption = 'Net 45'; }\n    value(4; \"Net60\") { Caption = 'Net 60'; }\n}\n```\nAll of the Business Central enums are mapped to option sets in Dataverse.\n## Extending option sets in Business Central\n1. Create a new AL extension.\n2. Add an Enum extension for the options that you want to extend. Be sure that you use the same value.\n```al\nenumextension 50100 \"CDS Payment Terms Code Extension\" extends \"CDS Payment Terms Code\"\n{\n    value(779800001; \"Cash Payment\") { Caption = 'Cash Payment'; }\n    value(779800002; \"Transfer\") { Caption = 'Transfer'; }\n}\n```\n> IMPORTANT\n> You must use the same option ID values from Dataverse when you extend the Business Central enum. Otherwise synchronization will fail.\n> IMPORTANT\n> Do not use the \",\" character in the enum values and captions. This is currently not supported by the Business Central runtime.\n> NOTE\n> The first ten characters of the new option value names and captions must be unique. For example, two options named \"Transfer 20 working days\" and \"Transfer 20 calendar days\" will cause an error because both have the same first 10 characters, \"Transfer 2\". Name them, for example, \"TRF20 WD\" and \"TRF20 CD.\"\n## Update Dataverse option mapping\nNow you can recreate the mapping between Dataverse options and Business Central records.\nOn the Integration Table Mapping page, choose the line for the Payment Terms map, and then choose the Synchronize Modified Records action. The Dataverse Option Mapping page is updated with the following records.\nRecord|Option Value|Option Value Caption\nPayment Terms: NET30|1|Net 30\nPayment Terms: 2%10NET30|2|2% 10; Net 30\nPayment Terms: NET45|3|Net 45\nPayment Terms: NET60|4|Net 60\nPayment Terms: CASH PAYME|779800001|Cash Payment\nPayment Terms: TRANSFER|779800002|Transfer\nThe Payment Terms table in Business Central has new records for the Dataverse options. In the following table, new options are in bold font. Italic rows represent all options that can now be synchronized. Remaining rows represent options aren't in use and are ignored during synchronization. You can remove them or extend Dataverse options with the same names.\n|Code|Due Date Calculation|Discount Date Calculation|Discount %|Calc. Pmt. Disc. on Cr. Memos|Description|\n|10 DAYS|10D||0.|FALSE|Net 10 days|\n|14 DAYS|14D||0.|FALSE|Net 14 days|\n|15 DAYS|15D||0.|FALSE|Net 15 days|\n|1M(8D)|1M|8D|2.|FALSE|1 Month/2% 8 days|\n|2 DAYS|2D||0.|FALSE|Net 2 days|\n|2%10NET30|||0.|FALSE||\n|21 DAYS|21D||0.|FALSE|Net 21 days|\n|30 DAYS|30D||0.|FALSE|Net 30 days|\n|60 DAYS|60D||0.|FALSE|Net 60 days|\n|7 DAYS|7D||0.|FALSE|Net 7 days|\n|CASH PAYME|||0.|FALSE||\n|CM|CM||0.|FALSE|Current Month|\n|COD|0D||0.|FALSE|Cash on delivery|\n|NET30|||0.|FALSE||\n|NET45|||0.|FALSE||\n|NET60|||0.|FALSE||\n|TRANSFER|||0.|FALSE||\n## Related information\nMapping the Tables and Fields to Synchronize<admin-how-to-modify-table-mappings-for-synchronization>\nFind free e-learning modules for Business Central here<https://learn.microsoft.com/training/dynamics365/business-central>"}