User is not able to see other demands besides theirs

[_Alex]

I have a weird issue going on in my instance, within the demand, I have a group called demand_users. I gave a user that role but for some reason when I open demand > all, that user can only see the demand record they entered. When I select any other user who have same role, the can see all demand records including their own. Cannot seem to figure out why just that one user cannot see any other demand other than theirs. Can I get some help here

Thank you 

[Deborah Brown L]

Hi @_Alex , make be there is a "argument" set for that module. Please check it once.

1. Open the module edit of that table.

2. Check for the arguments if they have included any "sysparm_fixed_query".

If  you find this useful, please give a thumbs up and mark it as an accepted solution.

Thanks,

Deborah Brown

[_Alex]

Argument does not exist but if this were the cause, would it not affect other users with same role the same way. In the case however,other users can see any demand 

[Sohail Khilji]

Hi @_Alex ,

the issue may be with user search preferences....

If a single user is unable to see records that should be appearing from a global search, this may be because they have adjusted their search groups. Before the Jakarta release users could select specific search groups or tables within a search group to not be searched when a global search was done. It is very likely that the user has made these kinds of selections and a quick check of the user preferences will confirm that. To see if the user has any preferences which may be restricting their global search results take the following actions:

1)  Go to the sys_user_preference table

2)  Filter the list where the User is your affected user and the name starts with "ts.group" or name starts with "ts.table"

If you find records that are ts.group.<sys ID> or ts.table.<sys ID> where the value is false it means that the group or specific table has been restricted for that user. Here are some sample preference names:

ts.group.8c59970e0a0a0b07013feb5e0d09c952

ts.table.8c5906a90a0a0b0700f8f2a9cc9ebce0

3) Deleting these user preference records will resolve the issue.

The sys ID in the ts.group entry above refers to a record in the ts_group table to exclude while the sys ID in the ts.table preference refers to a record in the ts_table to exclude.