When a user post a comment a dot shows under the author name instead of his name.
Here is a screen shot of my Data Chat Table: I hid the @ Sender ID (type: @ Email) column for privacy.
Here is the Layout editor and comment component General layout
That happens when the text of the author is too long. Maybe @comm_support_agent could trim the author name enough to see the date of the comment.
It looks like the name isn’t displaying at all for the 2nd user in the chat. This is likely due to the current user not being able to access the other user’s User Profile row (possibly due to row owners on the Users table). You may need to write the users’ names to static values in your Chat table, or look at giving each user appropriate access to the user profiles rows.
It also looks like you’re using the Author Photo as the name field. The 2nd user isn’t showing anything, again likely because the current user can’t access the other user’s user profile row.
What about the first one where we don’t see the entire date?
This is what the User’s table looks like:
When I created the User REL column, I used the @ Sender ID column to match value in User > @ Email.
For some reason, the data that the User REL column grab is the photo.
You’ve got Row Owners applied to too many columns. Remove them on all but the Email column.
Removed.
Result is still the same.
But when I change the Author Name to Email, Message it shows
Here is the User Name Lookup column looks like
If the user table is under row ownership and the current user is not an owner of the row that contains the user name and photo, then you can pretty much pretend that the other user doesn’t exist because the current user doesn’t have access to any other user rows other than their own.
Either remove row owners from the user table or write the user name and photo to the chat table instead of relying on lookup columns.
4 Likes
Hi Jeff,
That worked. I still want to have the Email column Row Owners for security reason. I’ll find another way to get that User Name and User Photo working.
Darren and Maxime, thank you as well!
2 Likes
The usual way to do that is to have a mirrored table that has records being added/updated/deleted to mirror records in the Users table. You can only store public info in that table (i.e rowID, name, photo) and do relations + lookups to get info based on those.
Would be better if we can set up tables like that using a live SQL query from the main Users table, for example. Or perhaps exclude some specific columns from row ownership effects. It’s complex.
1 Like
Anytime!