I have a view that shows me MY list of employees using the following selection criteria:
SELECT form=“Employees” & @Contains(Approvers; @Name( [CN] ; @UserName ) )
The “Approvers” field in the select above is a multi-valued readers field on the form that contains a list of approver names for a given employee (i.e. their supervisor, manager, vp, etc.). This field controls who can see the document. There is also a matching authors field with the same contents to control who edits the docment. I also have a single value text field called CurApprover which holds the name of the current approver for the employee document. This field drives a view column which lets an approver know if he needs to take action on and employee document with a Y for yes, N for no, or C for completed. This is reflected using the following formula:
tmpname := @Name([CN];@UserName);
@If(Status = “Complete”;“C”; tmpname = CurApprover; “Y”;“N”)
Problem:
The problem is sometimes when approver #1 opens this view to see his list of employees awaiting approval he may see all, some, or none of his employees even though his name is in the Approver’s reader field. If approver #1 goes in and just does and edit/save w/o changes on his employee documents, they will then show up in the view. If approver #2 opens the view he has to do the same thing approver #1 did (edit/save) to see his employee documents. Now, if approver #1 goes back to the view, he, again, will not see his employees and has to start all over again (edit/save) to get his documents to show up in the view.
This view should be straight forward, if my name is in the approvers field of a document, then I should be able to see it. If someone else edits another document, it should not effect me, and if my manager edits my employee’s document it should not proclude me from seeing the document since, again, I am in the approvers field.
I have made sure that the names in the approvers field are the individual’s names contained in the Notes NAB, so that is not an issue.
I have set the view’s indexing to be refreshed automatically after each use.
The problem is almost as if approver #2 is getting the view in a state left by approver #1, in which approver #2 now has to take steps to correct the view. Then when approver #1 goes back in he is getting the view in the state left by approver #2, or #5, or #3, etc., etc., etc.
I hope I have explained my problem in a way that makes sense enough for someone to give me a clue.
Thanks.