Small and medium business | Business Central, N...

Buyer field blank on Purchase Order report — reproduces on unmodified default layout

(3) Share

Report

Posted on by LS-17070636-0

Environment: US Business Central 28.2 (Platform 28.0.52286.0 + Application 28.2.50931.52241), SaaS

Issue:
The Buyer field is printing blank on the Purchase Order report (1322), even when using Microsoft's completely unmodified, out-of-the-box "Blue" Word layout — no customization involved.

Steps to reproduce:
1. Confirm a Purchase Order has a Purchaser Code assigned (in our case, PO 111182, Purchaser Code = JUSTIN).
2. Confirm the corresponding Salespersons/Purchasers record has a valid Name populated (confirmed: JUSTIN → "Justin_Cooney").
3. Print or preview the Purchase Order using the default Microsoft "Blue" Word layout for report 1322.
4. Buyer field is blank on the output, despite Payment Terms, Vendor Order No., and other header fields all rendering correctly from the same record.

What we've ruled out:
- Not a missing Purchaser Code (confirmed present on the order).
- Not a missing/incomplete Salesperson/Purchaser master record (confirmed Name is populated).
- Not a custom layout issue — reproduces on Microsoft's default, unmodified layout.

This points to the Buyer field not being populated correctly in the underlying report dataset/Word XML part for report 1322, rather than anything template-side.

Has anyone else seen this since the recent platform update? Any known issue or workaround would be appreciated — happy to provide more detail (screenshots of the order, the Salesperson/Purchaser record, and the printed output) if helpful.

Thanks!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Kumar Rahul 8 on at

Like (0)

Report
Copy link

Link copied!

This is a standard bug in the Format Document Codeunit (368). I have verified it in both v28.0 and v28.2.

In the SetPurchase procedure of Codeunit 368 (Format Document), the Salesperson/Purchaser record is not retrieved. This affects the standard Purchase Order report.

Solution: An event is available in the SetPurchase procedure that allows you to skip the standard code and implement your own corrected logic.

[EventSubscriber(ObjectType::Codeunit, Codeunit::"Format Document", OnBeforeSetPurchaser, '', false, false)]
local procedure OnBeforeSetPurchaser_FormatDocumet(var SalespersonPurchaser: Record "Salesperson/Purchaser"; Code: Code[20]; var PurchaserText: Text[50]; var IsHandled: Boolean)
var
PurchaserTxt: Label 'Purchaser';
begin
IsHandled := true;

if Code = '' then begin
SalespersonPurchaser.Init();
PurchaserText := '';
end else begin
SalespersonPurchaser.Get(Code);
PurchaserText := PurchaserTxt;
end;
end;

Before

After

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 102,811 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

I ran a quick test, and there were no issues. Please upgrade to version 28.3 and try again.
Version: W1 28.3 (Platform 28.0.52495.0 + Application 28.3.52162.52486)

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 18,890 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hello,

Yes, this is a confirmed Microsoft bug in Business Central 28. Microsoft has approved issue #8517, where the purchaser lookup was removed from codeunit Format Document, causing report 1322 Standard Purchase - Order to leave the Buyer/Purchaser name blank even with the standard layout. The issue is still open with no published fix version yet. As a temporary workaround, use another purchase order report/layout that still prints the purchaser correctly, or create a small report extension that retrieves the Salesperson/Purchaser Name directly from the Purchase Header’s Purchaser Code.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No