Issue with Purchase Requisition permissions in workflow

(1) Share

Report

Posted on by VJ VM

122

Hi. I recently configured a Purchase Requisition Workflow. The workflow runs the below steps:

1) Purchase Request submission by any department

2) Approval by Purchase supervisor/manager who also updates the price

3) Approval of the price by sales manager

4) Final approval by Finance Manager

Once the first approval is done by Purchase Supervisor with after updating the price (step 2), the price or qty or other details in the request should no longer be changeable.

However, it is currently changeable until the final approval. What can I do to stop anyone from editing the details in the Purchase Request after the first approval.

PURCHREQTABLE AND PURCHREQTABLELISTPAGE - Create and Update permissions are currently granted.

I have the same question (0)

All responses (5)

Answers (0)

Kevin Xia Microsoft Employee on at

Like (1)

Report

Hi,

You can limit whether users can edit PR workflows from a security perspective. You can refer to this blog post: alexdmeyer.com.

alexdmeyer.com.

Best regards,

Kevin

Was this reply helpful? Yes No
VJ VM 122 on at

Like (0)

Report

Hi. Thanks for your response.

Yes, I am aware of this but I am not able to limit the options since the user initiating the PR needs to be able to create a new record in PURCHREQTABLE AND PURCHREQTABLELISTPAGE to add the request and the item. So he needs the "create" permission.

We want it to be disabled only once the PR is submitted so that no further editing is possible.

When I give the user the "Create" access rights, he is able to edit all the details throughout the workflow, no matter what stage of approval it is in.

Was this reply helpful? Yes No
Kevin Xia Microsoft Employee on at

Like (0)

Report

Hi,

Best regards,

Kevin

Was this reply helpful? Yes No
VJ VM 122 on at

Like (0)

Report

Hello Kevin. Thanks for getting back to me. I understand, however, all I need is for the fields to be locked and not edited once the PR has been submitted. The case did not get solved with security either.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,210 Super User 2025 Season 2 on at

Like (0)

Report

Hi Vijay,

You can consider a customization, e.g. implement a security policy (XDS) where you can restrict users from editing a record. In case it is only about a set of fields, you can't use XDS for this purpose.

Was this reply helpful? Yes No