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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / "Shipment Date" OnVali...
Small and medium business | Business Central, N...
Suggested Answer

"Shipment Date" OnValidate inconsistency logic between Sales Header and Warehouse Shipment Header

(1) ShareShare
ReportReport
Posted on by Craig Yu 80

Dear MS experts,

 

During our development, we found there could be an inconsistency of Shipment Date field OnValidate trigger between the Sales Header table and Warehouse Shipment Header table.

 

In Sales Header table, the Shipment Date OnValidate trigger has GuiAllowed check to avoid odata v4 page reports exception of CallbackNotAllowed when HTTP PATCH to modify the Shipment Date.

But in Warehouse Shipment Header, the Shipment Date OnValidate trigger does not have any GuiAllowed check, so our HTTP PATCH via odata v4 page to modify the Shipment Date always results in the CallbackNotAllowed exception.

 

For such inconsistency, we were wondering if it was by design, and if so, we were also wondering if the only way is to write our own event subscriber to skip the original OnValidate trigger logics, so that our odata v4 page can allow HTTP PATCH to modify the Shipment Date?

 

Thanks!

Screenshot 2026-08-28 121010.png
Categories:
Dynamics 365 Business Central
I have the same question (0)
  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    Grigorios Mavrogeorgis 3,278 Super User 2026 Season 2 on at

    Hi, I don't think it's by design, the Sales Header was cleaned  for API scenarios over the years and the warehouse tables never had the same pass. 

    For the workaround, first check if your version has an OnBeforeValidate event with IsHandled on that field. If it's there, subscribe, do your own logic, set IsHandled true and the Confirm never runs. If not, I'd stop PATCHing that field at all and put a bound action on the OData page instead, then inside the codeunit set the date and update the lines yourself without going through Validate. Bit more code, but you don't fight the base app on every upgrade.

    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
    OussamaSabbouh Profile Picture
    OussamaSabbouh 19,159 Super User 2026 Season 2 on at

    Hello Craig Yu,

    Your analysis is correct: the CallbackNotAllowed error is caused by standard validation logic trying to display a confirmation/dialog during a web-service session, and Microsoft explicitly states that code executed through OData/API must not assume UI interaction and should protect only the UI-dependent part with GuiAllowed. I would not consider the difference between Sales Header and Warehouse Shipment Header confirmed “by design” based on the documentation; if the Warehouse Shipment Header validation performs an unconditional confirmation while the equivalent Sales Header logic is guarded, it is reasonable to report this to Microsoft as a base-application inconsistency. As a workaround, avoid bypassing the entire Shipment Date validation because you could also skip important warehouse-line/date update logic; if Microsoft exposes an IsHandled integration event specifically around the confirmation/update logic, subscribe to that and suppress only the UI-dependent part for web-service execution. If no suitable event exists, a custom integration implementation may be required, but I would raise a Microsoft support/ALAppExtensions request first. Microsoft also recommends using dedicated REST API pages rather than exposing standard UI pages through OData for integrations, although the underlying validation still must be web-service safe.

    Regards,
    Oussama Sabbouh

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 July Top 10 Community Leaders

These are the community rock stars!

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 581 Super User 2026 Season 2

#2
Grigorios Mavrogeorgis Profile Picture

Grigorios Mavrogeorgis 384 Super User 2026 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 366 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans