Role filtering in table not working

Report a Bug
1

To my memory, no changes have been made to the users table or the chapter events table where the row visibility/view filtering is now not working. The chapter events table rows are currently invisible to anyone with a role and is only visible when the user is set to “anyone”, which is pretty much the opposite of how it’s set up. We do have this happen with Glide somewhat often where nothing has changed but the logic seems to be applying inconsistently, and then it reverts back eventually.

Users: Has one column named “Role”

Chapter events table: Has four columns that are each set as row owner. We have 4 types of roles and each chapter event is always visible by two of those roles, and then is visible or invisible to the third and fourth roles.

chapter events
chapter events1187×160 42.9 KB

This typically has the outcome of when we reference this table in the app layout, all chapters’ events are visible to Admins and ELMs, and then only Coaches or BOD assigned to a given chapter will see the chapter’s events. Currently, no rows/events are visible to anyone.

We are on a maker plan with unlimited users, and unlimited syncs. We have 1895 rows of data in use.

UPDATE: I was experimenting with adding a “fields” component and in doing so, found out that the app sees everyone’s Role column as empty. Which would explain why filtering based on a Role would have challenges generally, but doesn’t explain why it allows “anyone” to see all the chapter event rows when the row ownership is based on someone having a specific Role assignation

3

UPDATE II: I removed row ownership and waited overnight. Then next day after all events started showing for everyone, I reinstated row ownership. It seems to be working more completely now, though tables that filter on role are still weird until I remove and then reinstate identical filtering and visibility settings. It’s frustrating because I don’t want to have to undo and redo everything to get stuff to work, especially because it seems that nothing was wrong with the settings in the first place.

4

A few things to note:

  1. Roles can only be set when a user row is created by another user with the same role (not when it’s created automatically on first sign in), or it can be set manually via the data editor (by you), or it can be set via any server side workflow (not the app interaction workflow). This could explain why you saw blank values if they weren’t properly set. They may temporarily appear to be set, but it’s not permanent unless the rule is set in one of the three ways I mentioned above.
  2. Changing the preview as user can be a bit squirrelly. I recommend refreshing the browser if you change the user you are previewing as to make sure it loads properly. The data editor has access to both owned and unowned rows, whereas the app front end would only have access to owned rows. Sometimes changing the preview as user doesn’t propagate properly.
  3. I wouldn’t expect filtering and visibility to break when using role in the filter, maybe I’m missing something or the above is causing a side effect. I would make sure the role is being set properly and sticking.