Forum Discussion
CharlieMurawski
8 years agoQrew Cadet
Hi Gil,
This is certainly achievable (if I'm understanding correctly) but the setup is a bit tricky...especially if you have a lot of tables and/or a deep hierarchy. I mocked up a basic example below. Keep in mind this is security by obscurity, since form rules are NOT database permissions; and QB doesn't currently support field level (conditional) user permissions.
The basic idea is to write a formula in your table that contains users; that resolves to the value of 1 if it's the current user's record and 0 if its not. THEN you can summarize that value up to your companies table, and pass it over to any child tables as a lookup. THEN you can use this field to control hide/show form rules.
I hope that makes sense!
Charlie
This is certainly achievable (if I'm understanding correctly) but the setup is a bit tricky...especially if you have a lot of tables and/or a deep hierarchy. I mocked up a basic example below. Keep in mind this is security by obscurity, since form rules are NOT database permissions; and QB doesn't currently support field level (conditional) user permissions.
The basic idea is to write a formula in your table that contains users; that resolves to the value of 1 if it's the current user's record and 0 if its not. THEN you can summarize that value up to your companies table, and pass it over to any child tables as a lookup. THEN you can use this field to control hide/show form rules.
I hope that makes sense!
Charlie
GilbertSpigelm2
8 years agoQrew Cadet
Hi Charlie,
Although this wasn't my topic, I like your idea. I was wondering how to use a User table to make this work.
Avinash, Charlie's idea would work for you.
Although this wasn't my topic, I like your idea. I was wondering how to use a User table to make this work.
Avinash, Charlie's idea would work for you.