Finance | Project Operations, Human Resources, ...

Strange dependency between values of the same fields in different invoices during the batch import

(1) Share

Report

Posted on by IS-27040848-0

I want to import vendor invoices into D365. For this purpose, a data project and a recurring data job were created (https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/data-entities/data-import-export-job). It includes the invoice header, its lines, and attachments. (https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/entity-vendor-invoice-header-vendorinvoiceheader etc.)
This job is used to import both single invoices and batches (packages, zip archives, with several invoices). Previously (v10.0.35), everything worked properly, but now (v10.0.38), there is weird behavior when importing a batch of invoices.
The invoice header contains the fields INVOICEDATE and DUEDATE. In the case of importing a single invoice, everything works fine. But when importing a group of invoices (as a batch), dependence on these fields arises between Different (!) invoices from the package.
For example, let's assume that the imported package contains two invoices. In this case, if both invoices have these fields filled in at the same time (possibly with different dates) or blank at the same time, then such a package will be imported successfully. But if one of the invoices has one of these fields filled in, and the other invoice does not have the same field filled in, then the package will not be imported. There will be a /Processed with error/: /The column in entity Vendor invoice header has incorrect data. Please correct the data and try the import again./
Can someone explain where the dependency between different invoices comes from and what to do in this case?
Thanks a lot.

All responses (2)

Answers (0)

Sort by

Suggested answer

Kevin Xia Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,

You can try to check the data mapping to make sure that the data mapping is correct and that the fields of each invoice are mapped in the correct location. May be, you can export some data and do the format mapping from the same column and row, let see if this works. On the other hand, the issue will arise if some data format is not correct, even though you see the data correct but the format of the data may be incorrect.

Best regards,

Kevin
IS-27040848-0 6 on at

Like (0)

Report
Copy link

Link copied!

Hi Kevin, thanks for your answer; unfortunately, it doesn't work in my case.
I use the same mapping both when sending (importing) single invoices and when sending several of them in a batch. For single invoices, everything always works well.
In the case of batch importing of invoices, I used the same mapping and values for the date's fields (DUEDATE and INVOICEDATE), but the success or failure of import did not depend on it, but only on how these fields were either filled in or not in different (!) invoices.

The following is about preparing the package for import into D365:
I take a package with two invoices, fill in the INVOICEDATE field in both (!) invoices - everything works. (if the DUEDATE field is also either filled in or left empty, but is the same in both(!) invoices)
if I leave the INVOICEDATE field empty in both invoices - import works again.
When I fill the INVOICEDATE field using the same value but only in one of the invoices (in the second, it is empty) - I get an error.
It seems to me that, in this case, it is difficult to talk about the incorrectness of the mapping or data. Because there are options when the same mapping with the same data led to the successful posting of invoices.

Best regards