Generic Inquiry behaves differently for different users

Hi @darylbowman! I have seen issues like this in the past and it can come down to a couple different things, but narrowing it down should help identify the cause.

I’ve seen an issue where the NoteID relation is being used in the GI to link to something the user does not have access to like, a note (!), or  a customization field, or restriction group possibly.

I would start by de-activating all the joins in the GI except one and see if the navigation works, then add them back one at a time to see which join is causing the problem (if this is the case).

You can also try to deactivate the restriction groups to verify they aren’t interfering with navigation, as sometimes the record will display because the user is part of allowed group, but also part of restricted group and so there is some confusion on GI form.

Otherwise I would try having no cusotmizations running to see if it could be an access issue to customized data coming in.

Lastly, I’ve seen this issue a lot with the INItemXRef table being joined in, if applicable.

Hope this can help!

@darylbowman Does the out of the box cases primary list work correctly? Please test the steps mentioned above to peel back the layers of joins in the GI and then re-add them while testing the navigation with each join re-added.

@darylbowman That is interesting, but not out of the scope of behavior I’ve seen in a GI. Are you also displaying the supporting Contact details like ContactCD or is the DisplayName by iteself?

Sometimes if a field which is unbound is displayed on its own then it can act strange or not display a value at all until the field is it bound to is also displayed.