Do users have the ability to add columns from related tables?

  • 0
  • 2
  • Question
  • Updated 3 years ago
  • Answered

How do I limit a user's ability to add columns from related tables? (But still have the ability to add columns to a view from the existing table they are reporting from)

I believe that adding a column from a related table (when viewing a report) will actually add the column as a look up field automatically......If this is true....then how can I prevent users from adding the same columns?


thanks

Photo of rocketc

rocketc

  • 774 Points 500 badge 2x thumb

Posted 3 years ago

  • 0
  • 2
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 65,218 Points 50k badge 2x thumb
Adding a column on a report from a related table does not create a new field on the table.
Photo of rocketc

rocketc

  • 774 Points 500 badge 2x thumb
Mark, when I'm on a report/view (Table B -child table) and I hover over a column header -- and select "add a column" from the drop down.....a pop-up box/window opens up with a list of fields available to add from Table B (table the view/report resides)....it also gives me the option to select "fields from a related table (Table A - Parent table).......when I select a field(s) from the Related Table (Table A)..... and select OK.....it automatically creates a look-up field(s) fwithin Table B.....and gives them Field IDs....is there a on/off switch for this action....???
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 65,218 Points 50k badge 2x thumb
Ok, so I was wrong.  Live and learn.  I had never added a column that way.  But when I did a "Test as Role" for a Role that does not have the ability to change field properties, then it did not add the column to the report and did not create an extra field.  So can you have a "regular user" do a test and I think that you will find that they cannot cheat on their Role Permission levels.