Silly question. How would you explain the rule regarding when to use the initial column, verses the 'user profile" column?
User Profile will always be directed towards the signed in user’s profile row. On the other hand, the “initial” column is going to depend on which row in the user table the screen is linked to.
Imagine you are viewing someone else’s user profile. One way will show your user type while the other way will show their user type.
3 Likes
Thanks Jeff! So is there an instance where you would be creating a data point and want the initial column instead of the User’s profile column? Especially when they are both user tables?
I imagine it would only be if you wanted something to be consistent across the board for all user and not anything individual?
Sure. There’s lot’s of cases to use either initial or profile columns.
The initial is linked to the row you are viewing, so for example, as an admin I may want to view and edit details about each individual user in the user table.
On the other hand, the user profile will always be linked exclusively to your row as the signed in user. The user profile is always your row and can be accessed everywhere in the app without the need for any filtering, relations, etc.
It all depends on the use case. If you always need access to your personal user row, then use the user profile. If you have a case where you would be accessing other user’s rows, then use the Initial.
2 Likes