Well I had my data fields all setup and ready to rock and roll only to discover the following below.
Apparently calculations more complicated than just “is this user the current user” are not able to be done? Am I misunderstanding something? What does it mean by “right now” lol
Hi there, @rdylina… that is literally one of the first limitations I ran into when I started using Bubble about 5 years ago, so that’s how long “right now” has been for me. So, at the risk of being blunt, make your peace with it and work around it because it is not likely to change any time soon. Sorry, man.
Best…
Mike
Privacy rules do not follow references to others data type.
If you want to make this data type visible only by a group of users you can add a list field of type User, then when you create data in the database you add to this field the list of users that will have permissions.
You need a bit more effort in the workflows for creating/modifying the data but you can set the privacy rule.
Has anyone developed a template with a group solution that might meet my needs? Probably worth a little dinero to save the brain damage.
As mentioned by the others this is a pain point that has to be worked around.
If you don’t want to change anything about your database setup (which is the best way overall) you can setup necessary conditions in the pages themselves
You can also use use the API to do a check if the current user is in the group.
I hadn’t thought about using bubble’s own API to extend its functionality. I’ll have to do a little research to see if there is a way to pull records directly based on a custom query.
Due to the number of records that would be returned, I don’t think building the display logic into the page would work. The user would be receiving 10s of thousands of records and then just only displaying the ones they have the ability to see. This really needs to be a server-level query for both resource and speed reasons.
This topic was automatically closed after 70 days. New replies are no longer allowed.
