web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

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

(0) ShareShare
ReportReport
Posted on by
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!
I have the same question (0)
  • Suggested answer
    Kumar Rahul Profile Picture
    8 on at
    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
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 694 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 481 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 328 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans