One Use case related to Data filtration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2024 12:53 PM
Scenario 1)
I have created a data filtration on incident table ,condition is like--incidents having assignment group as Hardware
should visible to users belonging to hardware group.
Image:-
So, filtrated records are 12..and these records are only visible to admin/ hardware group members.
Now, 2nd data filtration, I need a second scenario (OR scenario)
Scenario 2)
Here, condition should be like
Data condition--Assignment group is hardware & collaborator is dynamic me (collaborator is list type custom field)
Subject condition--Role is sn_collaborator" (custom role).
But then also, I am not able to see the records having assignment group as Hardware & Collaborator as logged-in user.
Actually, it should show one records more..for assignment group hardware && Collaborator logged-in
But, by default it is segregating through first data filtration.
I need both data filtration in OR condition.
Thanks in Advance
Utsav
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2024 05:42 PM
I would say It is not Data Filtration that is blocking the extra record, but ACLs.
Data Filtration is evaluated before ACLs, so if Data Filtration were to block the access, you would not get the "Number of records removed... : 1" message at the end of the list, which is thrown as a result of ACL evaluation.
I'm assuming the missing record is the hidden one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2024 10:53 PM
Actually, the message--"Number of records removed...1" is showing due to first data filtration, because the logged-in user does not belong to Hardware group.
Thanks & Regards
Utsav
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2024 03:14 AM
That message is NOT caused by data filtration, but by ACL(s).
I'm not saying that the record hidden is the one you are lokking for, I'm saying the record is hidden NOT by data filtration, but my ACL.