<img src="https://secure.leadforensics.com/133892.png" alt="" style="display:none;">

Have you been trying to get a massive data file into D365 and found out that 150,000 records were imported successfully but about 600 errored out?

Then you start thinking, “ugh, I'll have to go over each one of those records and figure out why D365 rejected them. Why isn’t there a way to generate a file with all the errors and the records we tried to import?!” 

Well, guess what? There is a way to do it. Get your Chrome browser ready, a “vlookup” and… voila!

Let’s do it!

First, download this cool Chrome extension called Table Browser Caller for D365FO (I know, I'm using Chrome, but unfortunately this is not available for Edge or Internet Explorer).

Once installed, configure the Table Browser Caller to point to as many environments as you wish. Once you’ve selected your environment and the right company, click on Table list. (If you know the name of the table you are looking for, just past it in the search bar and hit enter.)

y1 y2
The table that holds the staging errors for all the Data Management jobs is called "DMFStagingValidationLog".

This table might not be exposed on the table list, so just go ahead and type the name on the Table Browser Caller search bar and hit enter.


We'll focus on the four table fields below:

  • ErrorMessage: Contains the import error for each record.
  • Execution ID: A Data Management Import job generates a Job ID each time it is used. This ID can be found under the Job History form (navigate to the Data Management workspace, open the Data Project and click Job History).
  • Staging Table Name: This is the second table we'll need to extract in order to match the error message with the staged record. The "StagingTableName" will change based on the entity used for the import.
  • Staging RecID: Identifies the staged record. Will be used to “vlookup" primary key to match an error message with its staged record.

Use the column "ExecutionID" to filter the Job ID you're looking for.





In our example, the "StagingTableName" is "VendInvoiceJournalLineStaging," as we are trying to import AP Invoices via an AP Invoice journal.

Using the Table Browser Caller, open the staging table and use the "ExecutionID" table field to filter on a specific executed job. Then use the "RecID" table field to match the record with its error message.




So there you have it, with the help of the D365 Table Browser, you can export all the staging data error messages and their associated records. Happy exporting!

Next read: Is it that easy to enter an order in Business Central from Outlook?  Yep.


Discuss this post

Recommended posts

The complexity of warehouse operations in the past decade has increased, thanks to rapid technological changes and the ascending demand for better products and services. Managing these intricate processes requires precise and comprehensive analytics.
Big Data and Analytics have introduced paradigm changes in nearly every industry today. The fresh produce industry is of particular interest in this regard—in how data and analytics is enhancing current performance and readying the industry for the future.
Where are you on your data journey? Several companies mistakenly think they are much higher up on the curve until they eventually realize, "Oh, we're not quite as far as we thought we were." To determine what will generate the maximum value for your business, the first step is to determine the level of difficulty you are prepared to undertake.
I'm going to start this blog by citing Netflix's example—about it showcasing 'you may like' content snippets immediately after you've finished watching something on it. How does Netflix know your preferences? How does it predict your behavior? These recommendations are possible because Netflix knows about your viewing history.
Do you want to notice significant success in your business?
right-arrow share search phone phone-filled menu filter envelope envelope-filled close checkmark caret-down arrow-up arrow-right arrow-left arrow-down