Hi Molly,

There are a few possible reasons for this. Most commonly, this happens if the affected user doesn’t have permission to see the object, field, or record that the filter is referencing.

Is the user seeing this issue for all filters on the page, or just one filter? Are other pages affected?

If you haven’t already done so, I’d recommend logging in as other users that share the same profile to see if they’re impacted. I’d also recommend verifying that the affected user has a Skuid license, and the Skuid Page Viewer permission set.

Let me know what you find. We can keep digging if this doesn’t shed enough light on the problem.

Hi @molly.moeschler 

Have you resolved your question? 

@MillaZ I have not!

@Mark DeSimone thank you for the insight. Confirming their permissions at the perm set/profile/etc match those of users not experiencing the issue. 

They are experiencing this on all filters on that page. 

The affected user does have a Skuid license and permission set assigned. 

Any further help would be greatly appreciated! Thank you

Hi Molly, I noticed that the filter in your screenshot might be referencing your org’s user object. Is that accurate? If so, I would recommend confirming that your users have the necessary access to see the user object & records. Roles might also be involved, depending on how things are set up. 

I’d also recommend reading through our documentation about metadata caching. You can determine whether your org has this feature enabled by reviewing the steps described in the above link. If it is enabled, I would recommend following the steps linked here to refresh it. If the feature isn’t enabled, we can rule it out as a factor in the issue.