FInstagram Profiles (Bug?)

In the FInstagram template, I want to know if you click a profile button like this:


(The “Profile” button is labeled with bright color.)
Will other users able to see other people’s profiles? Will they be able to edit? (I don’t want people to edit other people’s profiles.)
Question%20for%20deleting
Example of me being able to edit my account.

That would depend on how you set it up. Look into the tutorials that talk about per-user data or search here for some ideas and tips.

Like what? This profile part is really confusing.

You would need to create a duplicate of the Profiles sheet and use Query or some other method to populate it with the same data that’s in the original Profiles sheet. The original profiles sheet will only be used for the Profiles tab in the app. That’s the one that you can allow the user to edit since they will only see their own profile due to Per User Data. The relation column in the Posts sheet would then point to the duplicated profiles sheet. There you can turn off editing since it will only be used to view the profile of the user that submitted the post. @david @JackVaughan maybe this is something that could be updated in the template along with using the new relations option.

I’ve updated the FInstagram sample to use the new Relation columns in the Data Editor.

You can make a read-only copy of the user profiles by mirroring the Profile sheet in another tab, but this is a bit too advanced to include in the template.

Create a second tab in your sheet and put in cell A1: ={Profile!A:Z} to create a copy of the profile sheet. Now use this as the read-only profiles in the app that cannot be edited.

1 Like

Which tutorial have you looked at that you don’t understand? If you have done a search on the posts and found some that you had questions about, I would suggest you post your questions to those.

I’ve made you a FInstagram Advanced template with read-only user profiles, but the current user can edit their own.

3 Likes

Thank You !!! :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation: :grey_exclamation:

Thanks for sharing. Appreciated