I have a strange case. Could anyone help me.
I have tree rol levels in my application the first is Employee, the second, Boss, and the third is BossII. there is a view for each rol.
The Boss, review the documents from his employees in his view. But sometimes, after he edtit the documents and close it, the view shows documents that not belong to him.
Is like the view wasn’t refreshing.
Could help me please.
Subject: strange case in view
Are you using the name of the roles in a Readers type field in the documents? You should.
Subject: RE: strange case in view
Yes I just use some rols in readers and Author Fields… And the boss can have these rols.
Do you know something about that… ??
I will be gratefull.
Subject: RE: strange case in view
Check the Readers fields on those documents which the Boss is not supposed to see.
Subject: RE: strange case in view
The rol that this boss have is included into Readers Field, but the formula selection for the view compares the @Name([CN];@UserName) whit the field’s name into that document.
thanks…
Subject: RE: strange case in view
Ok, that is the problem. You should never use @UserName in view selection Formulas, but rather control the view contents with field values and/or readers fields in the documents, or use web agents to replace the view.
Subject: RE: strange case in view
thanks you, I will follow your advice, but why do you suggest not to use the @UserName formula in view selection… ??
Subject: RE: strange case in view
If you take a look at the Notes Designer Help, about @UserName, you will find the following:http://www-12.lotus.com/ldd/doc/domino_notes/6.5.1/help65_designer.nsf/855dc7fcfd5fec9a85256b870069c0ab/ff5d38111a26ffb885256e000049d1d9?OpenDocument&Highlight=0,%40username
So, using @UserName in public views (=in views in databases on domino servers which are seen by many people), the results are totally random. When one user opens the view, the server will store the index according to what he saw, and if there is no change in the view contents, the next user will see what was meant for the previous user. And then, if the server decides to index the view, users will see what the server should see according to the view selection formula. That is why you should not use @UserName in public view selection formulas, in private views it should be OK to use, but I still have my doubts about that too.
Subject: RE: strange case in view
Ohhh… that, its so interesting and unreconizable for me. I will be grateful to you…
Thanks.