29
The New Vendor workflow should prevent users from posting credit memos or invoices, etc. for the new vendor until it has been approved. With the current structure of the standard New Vendor workflow, I am able to enter a new vendor and post documents without getting the vendor approved UNLESS I manually request approval on the vendor record.

This seems precarious since users may forget to request approval and could start using these vendors right away.
Category: Purchasing
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team

Comments

E

User can not use the vendor/ customer/item to create any document before the master data is approved. Thank you

Category: Purchasing

E

To add to Elaine's post.
Currently the Vendor Approval Workflow starts with an When Event of 'Approval of vendor is requested'. This requires the user to manually request the Approval. There could be situations where like Elaine talks about where the User forgets to submit this for approval. They could use the Block field, but this again is an extra step. They could change the When Event to 'A vendor record is changed', but what this does is sends multiple requests for approval:

1. After entering in the Name and tabbing off.
2. Another is sent after the user exists the window.

Ideally if we had the 'A vendor record is changed' When Event and allowed the user to fully enter in the Vendor Card and only send the Request for Approval when the user exits the page.

Category: Purchasing