I have a table called Feedback that has many rows/feedback pieces. There’s a column there called User Email representing an unique email from a user, but the same user can share multiple pieces (rows) of feedback, of course.
I want to create a separate table called User List, which is meant to be an analysis from the user point of view AKA “let me see the feedback given by specific users”.
The User List table main column should be User Email as well, but in this case it should be unique and dynamically populated having the column from the Feedback table as source.
I’ve checked the community high and low but for some reason nothing works.
I was kind of expecting this would be a somewhat simple lookup setup. Anything that I’m doing terribly wrong?
Your solution seems a good option for version 1, as I’m wasting too much time in this and it gives a good enough interface to search for information.
However, as I’m considering 3 types of entities (Feedback, Users, Companies) and the relationships between them (Users provide Feedback, Users belong to Companies), I think it would make sense to have 3 different tables.
Having different tables would also allow to, for example, add new Columns, such as Tags, to Users or Companies. These tags would be directly related with those entities and not to the Feedback items, which are represented as rows in the original table.
I hope the above makes sense!
However, I’m still puzzled why it’s so difficult to achieve what I’m looking for…
You need to add the rows to the user table somehow, and buttons are just how you perform that action. Once you’ve completed the button, you can make a relation column between Feedback & Users, and make the values to be as such: