The way in which Dynamics 365 Business Central handles certain data types affects the data that is pulled from the accounting platform into Codat. This article highlights things to look out for when you view datasets.
In Business Central, certain data types may display 'null' field values.
Invoices and credit notes without linked customers show the following values:
- CustomerName is
Customer not specified
- Id is
Bills and bill credit notes without linked suppliers show the following values:
- SupplierName of
Supplier not specified
- Id of
Line items of invoices, bills, credit notes, and bill credit notes without linked accounts show the following values:
- Name of
Account not specified.
- Id of
When the currency of a bill credit note is not set by the supplier, Codat uses the local, or base currency of the company. In Business Central, this is the LCY code on the General Ledger Setup page.
When pushing suppliers to Business Central, Codat auto-creates a placeholder payment method with the code "VNDDEFAULT" and the description "Do not use. Auto-generated by an external system". A payment method is required when creating a vendor in Business Central.
If the description was edited in Business Central, a validation error is returned on subsequent pushes. If the code was edited, the placeholder payment method is recreated.
Pushing Journals to Business Central is not currently supported by the integration. Therefore, when pushing Journal entries to Business Central all entries are posted to the general journal.
When pulling Tracking categories from Business Central, the
subCategories field within the tracking category tree model is not populated. This kind of relationship can't be modeled in Business Central.
Updated 11 days ago