Normally records with null reduction fields will not be visible to any user. They may be visible to admins if strict exclusion is unchecked.
I suggest that some analysis is required to determine the best approach to handling these null value fields before adding them as reduction field(s).
One Query -
While using section access with some field reduction in script then it is always necessary, to
make that field in upper case in data model ?
If Yes, then after changing that field in upper case then all of its values will reflect in upper case in final app and if again some user wants to see that field value in lower case then?
Standard fields on section access, like USERID, PASSWORD,... must be on uppercase. Reduction fields must be equal as your model field names.
If your reduction field is Country, on model must be Country.
The best way is change the field name on Section Access, with rename o with 'as' when you load your section access.
Thank you Manual.
One more query -
- Generally, if the section access has been applied on Country.
- I am managing the section access using excel file.
- And as we all know, if we want to apply the section access on multiple values from Country for single user
then we will need to add the separate line.
- So just to avoid adding separate line, is there any way to implement the section access on multiple Country values for single user in single line ?
Try like this, replace the null and blank values with a arbitrary values like NA and use the same in the data reduction . So that Admin will have access for all the data and rest will have access only for the data in data reduction field
In your original post, you mentioned that your Section Access should work with empty or NULL values. You can translate them on both sides into a text string (which does not clash with real values) like '*EMPTY*'.
In a later post you asked how you can avoid that users are confronted with dimension values in all upper case. When loading link field data in Sectiojn Application, create two fields in the same table, like
Upper(Country) AS COUNTRY, // Will link to section access
Country, // Will be dimension/selection field
And a third question somewhere was about how to avoid duplicate section access lines for users with multiple link values. There are a number of approaches available to you: