ERROR DUAL WRITE INTEGRATION SALESORDER HEADER (VATNUM IN TAXVATNUMTABLE)

(1) Share

Report

Posted on by GRA

We have a bi-directional Integration Dual Write Finance and Operation/Dataverse . I am trying to create an Salesorder. When I create a Quote header I don't get this error, so when I create an SalesOrder header I do.

The TaxVATNumTable table contains the value:H99999999 When I try to convert from a Quote to an Order, I get the following error:

Error:

Dual Write core application error-Dual Write core application error-Unable to write to Finance and Operations apps due to following error(s): {"Write failed for entity CDS sales order headers with unknown exceptionFor information on troubleshooting see https://go.microsoft.com/fwlink/?linkid=2244045. - Matching record with key 'VATNum': H99999999 for the data source 'TaxVATNumTable' does not exist"} Please rectify your data and try again. If issue persists after multiple retries, please contact your system administrator.

Returns the same error for all the VaTNum

We stoped the syncronization. Update Dual Write version.

Pluggin that show the error: Microsoft.Dynamics.Integrator.DualWriteFpRuntime.Plugins.PreCommitPlugin,

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (7)

Answers (2)

Jonas "Jones" Melgaard 4,919 Most Valuable Professional on at

Like (0)

Report

Have you checked that the VAT number exists in F&O?

The field contains validation that a record exists in the VAT number table, so that's most likely why it fails.

Was this reply helpful? Yes No
GRA 59 on at

Like (0)

Report

Hello Jonas,

thank you for your response. We check the VAT exist in F&O, so the issue is with every VAT...

Was this reply helpful? Yes No
GRA 59 on at

Like (0)

Report

Show you the error in Dataverse

and the check in FO:

Was this reply helpful? Yes No
Verified answer

Jonas "Jones" Melgaard 4,919 Most Valuable Professional on at

Like (1)

Report

Last time I configured Dual-Write, we had to change the ISO codes of the country on the accounts, since they didn't match the code in F&O.

That might be the reason why it's not matching. Can you check that?

Was this reply helpful? Yes No
Layan Jwei 8,097 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Did u run the map for VAT with initial sync?

Was this reply helpful? Yes No
GRA 59 on at

Like (0)

Report

Thank you Jonas! we mapped this field correctly and the syncronization is running right.

Thanks a lot

Was this reply helpful? Yes No
Verified answer

Jonas "Jones" Melgaard 4,919 Most Valuable Professional on at

Like (0)

Report

No problem, I'm glad to hear it got fixed (-:

If it's okay, can you mark this reply as confirmed?

I've fixed this in most of my implementations, and I think it would be good if this thread popped up when you search the error.

Was this reply helpful? Yes No