I have an administrative view which is hidden for the “normal” user. When I use the following code, the “normal” user get an error on @DbLookup when he try to open a document.
TempVar1 := @Middle(@GetField(“MT”);1;1);
@Implode(@Name([CN];@DbLookup(“”:“NoCache”;“”:“QSYS.NSF”;“”;TempVar1;“RCP”));“,”)
As standard we use frameset and page when we open the database.
How can I avoid this error.
Subject: Error on @DbLookup for a hidden view
Roger,
What error do they get? Is it “entry not found in index?” or something else
Mike
Subject: RE: Error on @DbLookup for a hidden view
It says that it cannot find the column which the @DbLookup use as source.
The user only has “reader” access. Maybe this is the reason?
If so, is the only solution to make a @If command on the @DbLookup command or is it another solution?
Subject: RE: Error on @DbLookup for a hidden view
What if you change the column name to a number (the column number)
Does it still error?
Subject: RE: Error on @DbLookup for a hidden view
Is the view hidden with parentheses or hidden using the security tab? One means the user won’t normally see the view in menus, the other means the user cannot access the view (and therefore can’t use it for lookups).
Subject: RE: Error on @DbLookup for a hidden view
I use the hide code on my outline and have an entry called “administration”
with the “hide when” code:
@IsNotMember(“role>]”;@UserRoles)
Under this “main entry” I have 4 outlines which all are of type “named
element”, view and computed as source.
The problem for my users are accelerating and I need to use the @DbLookup
command, so I hope anyone can help me.
Subject: RE: Error on @DbLookup for a hidden view
I didn’t ask how you were hiding the link, but how you are hiding the view. If you want to use the view for lookups, it cannot be hidden from the users using the security tab of the view properties.
Subject: RE: Error on @DbLookup for a hidden view
The view is only accessed by an outline entry, and only by 2 workflow administrators.
The hide command is only connected to an outline entry, so there is no hide command on the view.
But…
I managed to solve the problem by adding specific roles to the security tab and mark them out. So by removing the “All readers and above” mark things worked.
I still cannot understand why users with reader-access (and editor-access…!!!) was denied access to the view. The mark for “All readers and above” should have given them access, or…???
Subject: RE: Error on @DbLookup for a hidden view
Yes, it should have – in fact, that was what I was asking about. You cannot use anything other than “All readers and above” on a view used for lookups. Try reselecting the property – it may be that the view needed to be “jiggled”.