I am having trouble with my Section Access/Section Application configuration. In both of the configurations below, I add a "Role" column which I use to determine which objects a user has access to. The "ResourceLoginID" column acts as the field which joins to my data model to limit which records the user has access to.
With the first configuration below, I created an ADNAME as an artificial reduction field. I can access the .qvw application locally as Employee2 and only view Employee2's data & objects, as expected. However, when I deploy the application with the first configuration on the server, I get a message saying "Failed to open document. You don't have access to this document." I'm not sure why this works okay locally but doesn't work when deploying to server.
With the second configuration, I am able to access the application locally and on the server, but I don't have the ability to assign a Role of 'Supervisor' to Employee1.
Do you have any suggestions of what I can do to assign each employee a Role as well as determine whether they have access to only their own data or all of the data?
ResourceLoginID is a field which shows up in every record of my data model, because each record is pertinent to a specific Employee and contains their login ID. I want to make it so that Agent employees only see their own records, but Supervisor employees see all records.