"400 - bad request" when trying to sync Master Data NAV/D365BC

Question / Problem: 

We get a error "400 - bad request" when trying to sync Master Data

Answer / Solution: 

If the API call for sending vendors from NAV to the AP Essentials (formerly ReadSoft Online) API fails with a 400 Bad Request, the data sent is not valid (from AP Essentials (formerly ReadSoft Online)’s point of view). This could be, for example:

• Suppliers missing supplier number
• Suppliers with same supplier number
• Suppliers missing name

When the AP Essentials (formerly ReadSoft Online) API sends a 400 Bad Request, it also sends back information about exactly what’s wrong. However, the current NAV integration (created and maintained by Microsoft) does not show those details. You can debug the NAV code (or sniff the https traffic on your NAV server) and look at the full xml response to see all details returned.

Applies to: