Our requirement is to show all the record and report contents to a specific grou

We are using Entity-Backed records

Could you provide a little more insight? For example, what do you mean by request?

We are implementing an application where users can raise Issue tickets to get their problems resolved by the admin team. Admin team members should be able to see all the requests/tickets raised by users but users can only see the tickets/requests raised by them.

The best way to implement this would be to build two separate Record Types - since they serve fundamentally different purposes.

By doing this you can configure the Record Type security to be tailored to whomever you like (say one for Admins and one for All Users)

You could even use the same SAIL rules - but the most important difference would be that the All Users Record Type should have a default filter that only shows records for that user.

Hope that helps!

Hi Angad,

Thank you for the reply.

I have implemented this in another way without creating two separate record types, by creating a default filter on the record as follows:

Record Field: initiator
Operator: includes
Value:
=if(
isusermemberofgroup(
loggedInUser(),
cons!AdminGroup
),
null,
tostring(loggedInUser())
)

I did sanity testing and this method is filtering the data properly based on the user. Is there any problem that might occur with this approach?

There are a few drawbacks to that approach:

1) Using the conditional filter is less readable - other developers that come in and see the code will have a more difficult time understanding what is happening

2) Facets will be the same for both groups - and any attempt to change these based on user sets would need a separate Record Type

3) From a display point of view the records would also be identical to both user sets - things such as the list view details and the Record Type name will be the same for Admins and All Users

4) The filter will evaluate when you open the Record Type - this may be tougher on performance given the volume of records or the amount of users in the system

These may not all be relevant issues for your use case, but should be take in to consideration when making this decision

Thank you Angad.