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

Announcements

Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / document approval
Microsoft Dynamics NAV (Archived)

document approval

(0) ShareShare
ReportReport
Posted on by Justauser 50

In Nav document approval, user can change the amount after a Purchase Order is approved and status changed to "Released" without having to send another request for approval.  Seemed to defeat the purpose of document approval.  Is this a design flaw?

*This post is locked for comments

I have the same question (0)
  • Justauser Profile Picture
    Justauser 50 on at

    More information, I am referring the above situation to PO where line Type = G/L Account.  Nav does not allow changes if Type = Item or FA, but why allow change on G/L account?

  • Community Member Profile Picture
    Community Member on at

    looking at the code, above you mentioned is right and that is standard, under TestStatusOpen() Function, if you have addt'l req,you need to modify it, Perhaps you can write here what is exactly you want to acheive regarding this matter.

  • Justauser Profile Picture
    Justauser 50 on at

    Perhaps Nav should provide setup option to select what Type to allow or disallow changes instead of hardcoding it.  I know this is just a simple code of adding Type = G/L account in TestStatusOpen() Function, but this is unnecessary costs to users who is at the mercy of Nav consultancy company.

  • Suggested answer
    Joel Donat Profile Picture
    Joel Donat 165 on at

    This is by design and the behavior was also present even without the Document Approval functionality in place. NAV 5.0 (when Document Approval was first introduced) inherited the system's design wherein the Release functionality serves as a trigger for Warehouse Management that an Item or a Fixed Asset is ready for movement.  Since the system is restricting the Item Type or the Fixed Asset Type only for editing after the Purchase Order is released, it is because the Item and Fixed Asset involves something that is physically accounted for hence, the trigger for Warehouse Management.

    No tables are being affected or updated when a Purchase Order involving a G/L Account or Charge (Item) is posted as Receive only (in essence changes the status to "Released"). On the other hand, if a Purchase Order involves an Item or Fixed Asset, the system will update some records or tables already.

    The system was designed so that it could cater for small charges such as small shipping costs that could be added to an approved Purchase Order.

  • Justauser Profile Picture
    Justauser 50 on at

    Thanks Joel.  Good to have response from Microsoft perspective. This only explained to me why change is restrict to Type Item/Fixed Asset, but still not address the concern the lack of control in Type G/L. Seemed to me like a lazy way of carrying forward an old system design (Warehouse Management)  which does not suit the new functionality (Document Approval).  Will Microsoft take this onboard.. understand this involves only a very minor change.

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

News and Announcements

Introducing our New Video Series: Community Spotlight

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans