I have developed an application that contains several clients data within it. I am trying to use Section Access to determine which org units to load. Org units change and, rather than constantly going into the table and adding and subtracting units, I was hoping to use an asterisk as a wildcard since their is a naming system in place (numbers leading by a client abbreviation). After some research I've learned that wildcards will not be recognized. Is there a work around?
MIC - 001
MIC - 002
APP - 045
I've tried to use section access/application to data reduce a client field. Then in another table have a list of clients and their org unit abbreviation + wildcard.
Client: Org Units
However this results in the user seeing everything.
Exactly, * can be used as a wildcard in section acess only by itself.
A workaround is to use MIC* in Section Access, and to create a Link table in Section Application that expands MIC* into all values that start with MIC. For that table, you don't need to know what's in the Link field in Section Access. Just create a Link table based on [Org Units], like:
With this little difference. If you want to make your Section Access configurable by reading an external file, you'll need to read it twice (once in section access for IDs and ClientLimits, and once in Section Application for reading the combination of ClientLimit and Client). In my example, only Section Access will use an external file detailing User IDs and LinkField values. The rest is extracted automatically from the data.