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

Changing of the VAT Prod. Posting Grp Field in an Approved Purchase Order.

(2) ShareShare
ReportReport
Posted on by

"Our client has multiple departments, with each Department Head responsible for approving Purchase Orders for their respective department in Business Central.

At the point when a Purchase Order is submitted for approval, the VAT Prod. Posting Group is not yet known and is therefore left blank.

Once the Purchase Order has been approved and released, a member of the Finance team reviews the document and enters the appropriate VAT Prod. Posting Group before posting it. However, when they attempt to update this field, Business Central displays an error stating that the Purchase Document must first be reopened.

The client's requirement is for the Purchase Order to remain released while allowing the Finance team to amend only the VAT Prod. Posting Group and proceed with posting, without having to reopen the document.

While reviewing the Business Central workflow responses, I identified the "Apply the new values" response. I configured this response as shown below and added the VAT Prod. Posting Group field, but when the workflow is enabled the following error message is received "The workflow does not contain a response to revert and save the changed field values." Am I missing a workflow response after the Apply the new values ?


I have the same question (0)
  • Suggested answer
    TarikJerkovich Profile Picture
    305 on at
    Hello,
     

    Based on the screenshot and the error message, this is not a matter of adding another response after Apply the new values. That response is intended for a field-change approval workflow where Business Central first reverts and stores the proposed field value, and later applies or discards it depending on the approval outcome.

    A released Purchase Order is protected from this type of direct modification in standard Business Central. The expected process is to reopen the document, update the required field, and release it again.

    Therefore, the clean standard solution is to change the approval process so that Finance enters or validates the VAT Prod. Posting Group before the final release. For example, the department manager approves the commercial content first, Finance completes the VAT setup, and only then is the Purchase Order finally released.

    If th requirement is specifically to keep the document in Released status while allowing Finance to modify only the VAT Prod. Posting Group, then this requires an AL customization. The customization should be carefully designed because changing the VAT Product Posting Group can affect VAT calculation and posting setup.

    Kind regards

  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    2,757 Super User 2026 Season 1 on at
    Hi,
    that error is literal, Apply the new values needs a pairing response upstream, Revert the value of the <Field> field on the record and save the change, added on the event where the field gets changed, before approval. That's what buffers the value for Apply to use later, you're missing it.
    Test carefully after adding it though. Revert/Apply/Discard is built for protected fields on Open records, classic case is Vendor Name. A Released document is different, that reopen error usually sits in the field's own validation as a status check, not something the workflow controls, and Apply the new values still runs that validation when it applies the buffered value. You might just trade one error for the same error further down.

    If so, this is extension territory, not pure workflow, something that lets Finance touch that one field while Released, maybe reopening and releasing behind the scenes. Cheap to test the pairing fix first though.
     
    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

     
  • Suggested answer
    YUN ZHU Profile Picture
    102,422 Super User 2026 Season 1 on at
    I agree with TarikJerkovich; changing your existing business process is the best solution.
    Otherwise, customization would be required to bypass the approval validation.
    Hope the following can give you some hints as well.
    Dynamics 365 Business Central: Can we skip/ignore field validation errors?
     
    Thanks.
    ZHU

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 695 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 422 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