Missing purchaser code in reports

(7) Share

Report

Posted on by CU15061140-0

Hello everyone,

We have noticed a strange issue in our Business Central SaaS environment during the last couple of days.

The "Purchaser Code" field is still populated correctly in the Purchase Order header, but it is no longer displayed when printing purchase documents.

We have verified the following:

The "Purchaser Code" field contains a valid value in the Purchase Order.
The issue affects all report layouts (Word and RDLC).
The field was printing correctly until a few days ago.
No changes have been made to the report layouts.
We are using Business Central SaaS (Online).
The issue appears to be related to the report dataset rather than a specific layout.

Has anyone recently experienced a similar issue with the "Purchaser Code" field in purchase reports?

Is there any known Microsoft update, regression, or reported issue that could cause this field to stop appearing in reports while still being populated in the source document?

Any feedback or similar experiences would be greatly appreciated.

Thank you very much.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

OussamaSabbouh 18,449 Super User 2026 Season 1 on at

Like
a
(3)

Report
Copy link

Link copied!

Hello,

I would first confirm this from the report dataset by printing the PO and using Send to > Microsoft Excel Document (data only); if Purchaser Code is missing there, then the issue is before the Word/RDLC layout and not layout-related. Also check Report Selection - Purchase to confirm the expected report ID is still being used and no extension/custom report replaced it. Since it started suddenly in SaaS and affects all layouts, I would raise a Microsoft ticket with the environment version, report ID, document no., screenshot, and data-only Excel output. I cannot confirm a public known Microsoft regression from the available docs, but this behavior should be treated as dataset/report execution related, not a normal layout issue.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 2,841 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

first thing I'd do is confirm it's really gone from the dataset and not the layout. Run the report and download the dataset (or use the layout's show-data option), and look if Purchaser Code is actually empty in the data itself. If it's empty there, your layouts are innocent, the problem is upstream.
Then I'd check Report Selection - Purchase. SaaS updates sometimes swap in a newer standard report version, and if the assigned report object changed, the column might just not be there anymore. I seen something similar once where the selection pointed to a different report after an update.

I don't know any specific Microsoft regression on Purchaser Code right now, won't pretend I do. But if the dataset is genuinely empty on a standard report and nothing on your side changed, that smells like a platform change and I'd open a ticket with Microsoft. Which version did you land on after the update, and is the report the standard one or custom?

Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
CU15061140-0 4 on at

Like
a
(1)

Report
Copy link

Link copied!
Hello,

Thank you for your suggestions.

I have carried out the checks you mentioned and can provide the following findings:

I have executed report 1322 and exported the output using “Send to > Microsoft Excel (data only)”.

The dataset contains the column SalesPurchPersonName, so the field is being passed to the report.

However, the value is empty in the dataset output.

Further validation:

The Purchaser Code is correctly populated in the Purchase Order header.

The corresponding record exists in Table 13 (Salesperson/Purchaser).

The record in Table 13 contains a valid Name value.

The report is standard (no modifications).

The issue affects all layouts (Word and RDLC), which confirms it is not layout-related.

Based on this, the issue appears to be happening at report dataset generation level, where the lookup from Purchaser Code to Table 13 and assignment to SalesPurchPersonName is not being correctly executed.

At this stage, it seems to be related to report execution logic rather than layout configuration or missing master data.

Any additional insights or similar experiences would be appreciated.

Kind regards,

Was this reply helpful? Yes No
DLDlutavia 14 on at

Like
a
(1)

Report
Copy link

Link copied!

We are seeing the same issue except it still prints successfully with the RDLC Report ID 10122.

The Word layout used SalesPurchPersonName. I tested changing this to PurchaserText (the only other field close to Buyer name) and it prints blank as well.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 23,136 Super User 2026 Season 1 on at

Like
a
(3)

Report
Copy link

Link copied!

This appears to be a known Microsoft issue in Report 1322 after the recent Business Central update. The Purchaser Code remains available on the Purchase Header, but the purchaser name is not being retrieved in the report dataset.

Microsoft has already logged and approved the issue here: https://github.com/microsoft/BCApps/issues/8517

As a temporary workaround, you can use a report extension/custom layout to retrieve and print the Salesperson/Purchaser name directly until Microsoft releases a fix.

Was this reply helpful? Yes No