topic Re: Section Access - hide a field based on the value in another table in App Development

Section Access - hide a field based on the value in another table

twanqlik — Tue, 09 Oct 2018 11:03:03 GMT

I'm struggling with Section Access:

Goal: I want to make the 'Email' Field visible for Dashboard users that have a specific value in the 'Business Group'.

The rest of the fields in the Master_Users table should always be visible to all the dashboard users.

I don't think this is possible with Section Access.

Re: Section Access - hide a field based on the value in another table

marcus_sommer — Tue, 09 Oct 2018 13:40:04 GMT

It should be possible to control the visibility of this field with section access if you filled there the field OMIT with Email or leaving it blank based on the data in BUSINESS_GROUP: Introduction to Section Access.

- Marcus

Re: Section Access - hide a field based on the value in another table

twanqlik — Tue, 09 Oct 2018 13:51:28 GMT

I already have read the introduction to section access page, but couldn't find a way to accomplish this.

Re: Section Access - hide a field based on the value in another table

marcus_sommer — Tue, 09 Oct 2018 13:59:38 GMT

Take a look on the example 5 there on page 17.

Re: Section Access - hide a field based on the value in another table

twanqlik — Wed, 10 Oct 2018 08:41:49 GMT

With Omit, the field will be hidden, but i want to hide values in the field itself.

Re: Section Access - hide a field based on the value in another table

marcus_sommer — Wed, 10 Oct 2018 09:11:07 GMT

Now I understand what do you want to do but it's not possible with the "standard" logic of section access which allowed the visibility of a column and/or a record for an user or not but nothing in between them.

This means you need some additionally measures to get it. This could be to use two different mail-fields and depending of which field is available within the datamodel it will be displayed within the UI (the field could be replaced through a variable in which such a check is applied). Quite similar is the approach of duplicating the records and one record has a mail-value and the other is blank and per your field BUSINESS_GROUP you controls which of the records will be reduced.

Another way could be to Mask or de-identify data for certain users using Section Access.

- Marcus