Dynamics Community Forum Thread Details

D365 Electronic Reporting (ER) Invoice: Missing Line-Item Data with Parallel Report Generation

Hi,

We have a very unusual problem with generating an ER report.

I have created a custom project invoice ER format based on Excel. The data source for the ER model’s rows comes from data-provider class:

The invoice printout generally works correctly (most of the time). However, when two or more reports are generated simultaneously, a strange situation occurs: the generated report shows the header data normally, but the invoice’s line item data from the data source disappears. Same as if the invoice had no lines. Moreover, this happens in a certain sequence. Even when forcing two print jobs concurrently during testing, it occurs in roughly 20–30% of attempts.

Interestingly, on rare occasions the invoice would be generated without any lines and… without the “no lines” indicator. That no-rows-indicator element is defined earlier (right before the rows) and evidently its visibility formula still “remembers” the rows, whereas the grid of rows does not. Maybe this is a clue in solving this problem.

Of course, there are no changes to the line items in the meantime, since the invoice has already been posted and the lines are not being deleted.

The temporary table holding the rows is custom. If necessary, I can provide you the definition in AOT along with nodes and attributes. However, it’s defined exactly the same way as the header tmp table that does not have any problems.

Do you have any idea what might be causing the line items to disappear from the report’s data source?

Thanks in advance for your help!

Categories:

Dynamics 365 Finance

Good morning, afternoon, or evening depending on your location!

This is a tricky issue, but there are a few possible explanations for why line-item data disappears when multiple Electronic Reporting (ER) invoices are generated simultaneously. Here are key areas to investigate:

Potential Causes & Solutions
1. Issue with Temporary Table & Data Provider Concurrency

Since the line-item data is stored in a temporary table, check whether multiple concurrent report generations are causing data overwrites or conflicts in the temp table.
If the data-provider class fetches data dynamically, ensure that the execution context isn't getting overridden due to multiple requests hitting the same temp table.

Solution:

Try using session-based temporary tables instead of regular temporary tables to isolate each report’s data.
Add debug logging to confirm if the line data is retrieved correctly but lost before rendering.

2. ER Execution Order & Processing Delays

ER processes header and line data separately, so if there’s a delay in retrieving lines, they might not appear in the report before it finalizes.
The fact that the “No rows” indicator sometimes remembers the lines suggests that the data exists at some point but fails during rendering.

Solution:

Introduce a small delay in execution using batch job dependencies to ensure the line data is fully loaded before report generation.
Check if changing the sequence of data retrieval in ER helps.

3. Parallel Execution & Isolation in ER

If two reports are triggered simultaneously, ensure the data-provider logic correctly isolates the transactions for each report instance.
Some ER models reuse cached data, meaning one report execution might unintentionally remove data from another.

Solution:

Modify the ER model to force a fresh data retrieval for every report run.
Set data-provider logic to avoid shared dataset caching if reports are executing in parallel.

4. Debugging Steps

Run test cases where:
1. A single report runs alone → check if lines appear correctly.
2. Two reports run sequentially (instead of in parallel) → confirm whether both reports generate complete invoices.
3. Add logging to temp table population—verify whether data gets inserted and then disappears.