Forum Discussion
EvanMartinez
7 years agoQrew Elite
Hi Esther,
This is not an unusual confusion that builders run into when working with a formula field and information being summarized up or passed down from another table. That checkbox only removes restrictions on the field level. So for example if my formula includes a field called Manager Markup and that field is normally hidden for every role but the Manager role checking that checkbox would allow me to include it in the formula so that my other roles could see the output without seeing the field. Unfortunately, if I also restricted them from seeing every record they would still see nothing, since even though they have permissions to see that single field they don't have permission to see any of the records, so to them that field is blank as there are no records visible (or it might be wrong/different if they can see some records but not all). There are a few options in this instance. You can adjust your permissions so that role is able to see all records, but is restricted so they aren't able to see any of the fields but the ones you need in the formula. Alternatively, you can also possibly host just the information you need in another table that is outside of the data you want to protect via an Action or Sync. This process just requires a bit more complex a build. This is a result of Quick Base permissions hearing that you don't want that role to see any records and choosing to listen to that restriction. I hope this information is helpful Esther.
This is not an unusual confusion that builders run into when working with a formula field and information being summarized up or passed down from another table. That checkbox only removes restrictions on the field level. So for example if my formula includes a field called Manager Markup and that field is normally hidden for every role but the Manager role checking that checkbox would allow me to include it in the formula so that my other roles could see the output without seeing the field. Unfortunately, if I also restricted them from seeing every record they would still see nothing, since even though they have permissions to see that single field they don't have permission to see any of the records, so to them that field is blank as there are no records visible (or it might be wrong/different if they can see some records but not all). There are a few options in this instance. You can adjust your permissions so that role is able to see all records, but is restricted so they aren't able to see any of the fields but the ones you need in the formula. Alternatively, you can also possibly host just the information you need in another table that is outside of the data you want to protect via an Action or Sync. This process just requires a bit more complex a build. This is a result of Quick Base permissions hearing that you don't want that role to see any records and choosing to listen to that restriction. I hope this information is helpful Esther.