Subject: I am unable to get @UserRoles to work properly on a local replica?
Have you assigned an administration server? We have had some fun and games with similar problems to do with roles not being honoured on local replicas and found the admin server setting helped sometimes. THe other thing we tried was to allow doc locking in the db as this forces the lookup for the ACL to go back to the server.
I have also found portals very resistent to change until a restart or the client or a wipe of the cache file or even reloadin gthe db into the portal frame has occurred.
Subject: RE: I am unable to get @UserRoles to work properly on a local replica?
Hi Shane.
Thanks very much for the response.
Yes, we have applied an administration server.
I have tried wiping out the cache and desktop - No luck.
I have also tried adding the group to the local NAB database - No luck again.
I am a little hesitant to add the db property to allow document locking, since I am not sure of the immediate consequences.
I seem to remember having similar issues quite some time ago with a user that belonged to several groups. That database (as well as this one) used several different types of entry in the ACL to control access. For example…
*/ABCCorp
John Doe/ABCCorp
Unique Group
I know that one type of entry actually takes precedence over the other (group vs. canonical entry), but I can’t remember which. This particular user is not explicitly named in the ACL, & I really don’t want to clog up the ACL with heaps of individual names.
Perhaps this is the basis of my issue, but I would’ve expected the same issue on the server if this was the case.