Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
i'm trying to show a sheet within a qvw only to those assigned as Admins in our section access script. We currently load this from an excel file.
It won't allow me to use the field "Access" i'm assuming because of the section access function. Is there a way to specify the conditional show based on role.
I'm trying to avoid defining the admins explicitly (ie. OSUser() = MMOUSE), or loading the section access spreadsheet again as a table.
Access | NTName |
ADMIN | RF\MMOUSE |
ADMIN | RF\DDUCK |
ADMIN | RF\BBUNNY |
USER | RF\RRUNNER |
USER | PPLUTO |
I think there's no conflict in maintaining the SA spreadsheet since the duplicated table is loading * from your SA table.
You wouldn't need to maintain both SA table and the duplicated table.
Try
noconcatenate:
<Load your section access table>
Then use <Access> field for show hide condition.
Matthew, did Arthur's idea work for you? It is the only way of which I can think to use the field, and I hope it made sense, you basically need to reload the portion of the Section Access table that has the NTNAME and ACCESS fields into the regular data model such that you will be able to use those fields in your conditional show. It is similar to what you would do with Dynamic Data Reduction and the link between Section Access and Section Application fields... If this did work, be sure to use the Accept as Solution on Arthur's post to give him credit and let others know it did work for you.
The other thing you may want to do at that point potentially is make those fields 'hidden' as well using the following:
That should let you flag those fields such that folks will not see them, which I would think you likely want in this case, but you should still be able to use them in your expressions I believe.
Regards,
Brett
Hey All,
I'm actually looking for a solution that allows me to use the existing Section Access table created in my hidden script, rather than replicating that table in the data model and using the new field.
Reason being is that I only want to have to manage it from our current SA spreadsheet, rather than two places.
If the Section Access table can't be used directly, i'd rather just use a show condition of OSUser() = 'RF\BBUNNY'
I think there's no conflict in maintaining the SA spreadsheet since the duplicated table is loading * from your SA table.
You wouldn't need to maintain both SA table and the duplicated table.
Makes sense now, thanks Arthur!