I am trying to issue an electronic invoice using Electronic Invoicing in Dynamics 365 Finance and Operations. I created a custom format in Electronic Reporting (ER), derived from the standard UBL Sales Invoice and PEPPOL Sales Invoice formats.
The format runs successfully in Reporting Configurations within ER, where I can generate an XML file that fully meets the required specifications. To include additional fields, I derived the standard "Invoice Model", ensuring that all mappings are correctly configured. I have thoroughly verified that the mappings are properly set up, and the custom model has already been successfully used in other F&O features, such as generating invoice documents in the Free Text Invoice module.
However, when using Electronic Invoicing, deriving the standard PEPPOL feature, and applying my custom ER format, I receive an error in the submission log. The error refers to a JSON file that does not contain the new fields added in my custom model, specifically in the InvoiceCustomer definition.
To investigate further, I mapped the field where the error occurs to an existing standard field. This resolved the error for that specific field, but as soon as the system encounters another new field from the derived model, the same issue occurs again.
Given that I can successfully generate a file in Reporting Configurations, my main questions are:
- Is it possible to modify the JSON structure referenced in the error to include the fields from my custom model?
- Is there any configuration/feature that might be missing in order for Electronic Invoicing to recognize the new fields?
Any guidance on resolving this issue would be greatly appreciated.
Thank you!