Hi Team
I’d appreciate your help.
Context:
-
I’m trying to combine a mix of public and private data in a flow. Imagine private recipes, and public recipes, with each user being able to add public recipes to their private (without editing them)
-
We currently have a tab container with a collection per tab, 1) private, 2) public.
-
Right now these are two tables, but I think I can combine them into one using user-specific columns and some tweaks with data ownership
-
I’ve tried row ownership for the private ones, and role ownership for the public ones, tagged as (Public or similar, with a role like this), but it didn’t work. I thought this would apply as an “OR”, but I think it was an “AND” between email and role ownership
-
I’m considering some type of table combination with relations etc, but I’m looking for a more optimal & smooth setup, to avoid duplicating the rows in the private tables when a user adds a public recipe to their private ones
Any hints?
Thank you very much!
My initial thought is that you might be overcomplicating this. If a user can’t edit a recipe that’s been added to their “private” collection, how is that different from simply marking it as a favourite?
I’ve used row owners here before. Works well if you’re using multiple roles. Give every user a role of “public”. In the recipes table, create two row owner columns: a public column with the “public” value if the recipe is public and an email column for the recipes if they’re private. Then, if a user wants to make their private recipe public, you only need an action to write the “public” role in the public column.
Thanks Robert. I tried smth like this:
- User Table includes row ownership per email, and role (no row ownership)
- Table with data under examination:
- Row ownership per email
- Row ownership per role
But it didn’t work at the builder level. I will try again!
Did you configure the Role column in your User Profiles?
If by this you mean, going to the profile and assigning role to a column, then yes I did.
It worked! @Robert_Petitto , thank you very much!