You’re offline. This is a read only version of the page.
55
Dear all
I want to apply a filter on urchase requisitions where each user could see only PRs created by users of his/her department. or by reason (in our case reason = department).
Please advise on how to apply the record level security in the explained cas.
I have tried creating RLS on a role with filter on purchase requisition table, and a filter on the field created by. The result is good on the form all purchase requisition, the user could see only the appropriate PRs but when clicking ''New'' in order to create new PR, we get an error.
Please to give advise on how to set the RLS in purchase requisition on the field ''reason'' .
Best regards.
Hello,
Here is a link explaining the Record level security set in :
Purchase order
Purchase requisition
https://www.youtube.com/watch?v=mPe6UIzQX98
Best regards.
Hello,
I have finally found how to set the RLS on PRs by filtring on created by filter.
The problem was resoved by adding new table ''PR lines'' on RLS and user the same filter for the PR table.
Thanks to all for your support.
Best regards.
Hi dalila,
Can you share a screenshot to illustrate exactly what you mean with no access to create a new line? Do you get an error or is the grid not enabled?
Thanks a lot André Arnaud, but I don't have technical resource for implementing XDS, I have seen that needs minimum of developing skills.
I have tried the advice on the filter, it works, the new PR is created but no access to create new line and the workflow action pane is no displayed... for your information I used the same previous role privilege wich allowed users to create PR normally.
On the RLS filter, I have set the below filters :
Item group table : *
Item invent table : *
Purchase requisition table :"",user1,user2...
So which table should be add to the RLS filter ? or is it another problem ?
Thanks in advance.
Best regards.
I would still recommend to use XDS, but to bypass this error, you can try to include an empty value in the filter. So instead of
user1, user2
use
"",user1, user2
Hi Dalila,
As mentioned , XDS is recommended and RLS is depreciated. But if you still want to use RLS:
You are filtering on field CreatedBy which will be updated during the actual insert not before that (when creating a new PR) , the message you get clearly shows that RLS is doing its job based on the filter criteria you provided.
Regards
Thanks for your proposal, here is the error message :
Cannot create a record in Purchase requisition (PurchReqTable).
You are denied access to create a record in the table due to the filter criteria set for the row level security.
Thanks for your proposal, here is the error message :
Cannot create a record in Purchase requisition (PurchReqTable).
You are denied access to create a record in the table due to the filter criteria set for the row level security.
Hi dalila,
Please have a look at Andre's blog where you can find a lot of good examples how to implement XDS.
Yet, before doing that I would like to know why you need 'record level security' / XDS for purchase requisitions.
I mean, those data are typically non business critical and 'top secret'.
So, what's the value added from applying this for purchase requisitions?
Best regards,
Ludwig
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (