We have an application where it is necessary to use Readers fields in the form to control access to sensitive data. There can be (and often is) more than one entry in each Readers field. The first column in the view is a TextList field containing the contents of the Readers field. This has the effect of ‘grouping’ all documents for a user under their user name - however, it also means the same documents will also be grouped under other user names with access to the same documents. Performance for some of the views is not great. Please can someone suggest if having this categorised column is helping performance or hindering it, i.e. if we were to remove this categorised column would things improve/get worse for a user who may only have access to 50 out of 10000 documents. Instead of having their documents grouped under their user name (from the TextList) they would see them listed based on the Readers field content.
Subject: Are you sure that there is no @now /@today in the view selection formulas
Subject: .
No there is no @now or @today in the selection formula
Subject: Reader fields do effect view performance
When you open a view in Notes, the client needs to get the first “x” documents to build the screen view that the user sees. If there are no reader fields involved, this is a quick process, as it just needs to examine the first “x” documents in the view’s index.
However, when you have Reader fields that limit access to a small subset of the documents, Notes may have to examine thousands of documents to get enough data to build that initial view for the user.
Private views could help here, as each user will have their own view index with just those documents that they can see.
Subject: Re: View Performance Problems
Hi Gary,
your problem is, that when using reader fields domino “ignores” indexing because it checks every document for read access when opening a view.
Your Idea with the categorized first column is 50% of the solution. To gain a performance benefit you need to embed the view in a form showing only a single category which value is the username of the current user.
Hope this helps
Stephan