Announcements
No record found.
A GP 2016 client is experiencing an issue where users are able to delete a Purchase Requisition after it has been submitted and then rejected.This is causing issues with their audit trail (the submission/rejection are lost) and Requisition numbering (as GP goes back and fills in the "missing" Requisition Number when another requisition is created). For the numbering issue, I don't see a PSTL option to stop this behavior for Requisitions, like we have for POs and Receipts.I don't see any PO Requisition options to disable the ability to Delete requisitions (and force a void).I also don't see the Delete action as a field available in Field-Level Security. (I see Delete Row Button, but not the Delete action.)(I even considered VBA for a short-term fix but I don't see Delete as an option either.)Any ideas?[GPPT is not an option for their immediate need. It will be a recommendation for their GP upgrade plan. ]
Lisa-
I looked on the Ideas site and there isn't anything out there about it, surprisingly. I can completely understand why this would be something to have the ability to turn on/off, like the ability to turn off deleting for SOP docs, etc. Or just not allow it period once submitted, like how you can't delete POs in POP once released.
Do you want to create the idea and I'll vote it, or do you want me to? :)
Joe
Thank you, Joe, for responding. I too had searched Ideas and didn't find it. I went ahead and created the following idea:
experience.dynamics.com/.../
I do this in Visual Studio so it may also be available in VBA. I believe you are looking for the LocalActionsButton_ValidateBeforeOriginal which includes a Cancel event if cancelling the operation is desired. You will need to inspect the value of the button that was clicked, which will be an integer, and unfortunately no way to determine the text value displayed on the button. The integer value is simply the index of the list of values shown when clicking the button...so the second option shown in the list will be button value 2 (for example).
We don't use Purchase Order Requisitions in our environment but assuming it is similar to the Sales Transaction Entry or Purchase Order Entry windows please note the following: The list of options when clicking the Actions button may be different depending upon the state of the current document and must be taken into account when doing your coding. So for example, in Sales Transaction Entry, Purchase may be the second option shown for a drop-ship order, so it is button value 2. But looking at a non-drop ship order the second option may be Void...also button value 2.
Hope this helps and please mark if answered.
Thank you, Craig, for the hint. I did end up finding the specific action in VBA. (I "cheated" and created a macro where I clicked the action I wanted so I can see what was saved in the .MAC file.) That helps stop the document from being deleted. However, the pesky "Save/Delete" prompt is also on the window. I have reached out to the client to see if a DELETE trigger on the table will help for their auditing. It is going to capture more than just the user deletes, but it may enough to get some reporting for audit requirements. (I am hoping this is a short-term fix as we hope to upgrade them to GP 18.3 - which includes a Dexterity customization on this window that I hope to incorporate Delete functionality into - in the very near future.)
Great. You mentioned the Save/Delete on the window. If you are talking about after changes are made and you go to print or move to another record and get the dialog box asking to save, delete or cancel the document...this can be captured with the BeforeModalDialog event. I provide a substitute window for the user to answer, check it against our business rules and then choose the actual GP response based upon that evaluation.
Great idea ... Thank you!
Hi Lisa
This is a simple customisation with GP Power Tools. No need to wait as GPPT is available for all versions of GP.
We can handle deleting of rows and the entire document with whatever business rules you want.
Install the free 30 day trial period and I will help you write the triggers.
Note that VBA is no longer a supported environment as it has reached End of Life and does not work on newer Operating Systems.
If you write it with GPPT, there is no deployment needed, no upgrades for new versions, it is more stable and reliable and does not need any external tools or environments.
Regards
David
PS: You should install GP Power Tools BEFORE upgrading so you can run Database Validation and ensure a smooth upgrade.
For those who are looking for similar kind of solutions on this window or in any other GP window, feel free to visit my blog. I don't think it's a very simple customization. DD-
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.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 617
André Arnaud de Cal... 461 Super User 2026 Season 1
Syed Haris Shah 298 Super User 2026 Season 1
