I am having issues with reader fields in this release 6.5.1, I have never had a problem before. I have a reader field with 25 names in it. The names are derived from a Profile Doc in the database that looks up a list of Managers that should have read access to the docs. Each doc then computes the reader field to result in the list of managers. The problem is; the reader field doesn’t provide read access unless it is a computed when composed field, an editable field with the default value @getProfileField(XX) or a computed field with the same formula will not work but a computed when composed field will? any help or suggestions will be appreciated as I have searched the release notes and web and found nothing to help.
Subject: RE: Reader Fields editable, computed, computed when composed
First, I have to say that your application will have better performance, use much less disk space, and be more maintainable if you use a role or group of managers rather than duplicating this information in every document.
There is absolutely no reason the field shouldn’t work just as well as a computed or editable field instead of computed when composed (though, if you don’t need to change the value, CWC is the best choice anyway). There is some other issue preventing it from working in the other cases, e.g. the field has not been set to be multivalued, so it’s getting converted to a delimited string instead of a list.
Please see these links:
tool to analyze whether current user can read/edit a document
Compleat Reader and Author Field Troubleshooter
Subject: RE: Reader Fields editable, computed, computed when composed
I changed my approach to the formula in the readres field, it is now looking at the role “[Managers]” as the authorized readers for the document.The readers field still will not work unless the field is CWC, which is contrary to as advertised. I did go to your postings, thank you, and confirmed I was using and writing the formula correct, and I am so the only conclusion left is R6.5.1 designer or client is broke! Andre I appreciate you taking the time.
Subject: RE: Reader Fields editable, computed, computed when composed
If you have a Readers (or Authors) item stored in a document, the Notes client and server do not even look at the form design to decide whether you have access. They only care about whether the item has a Readers flag set and what its value is. If your Readers field is not working, it’s because the Readers flag did not get set or because the item doesn’t have the value you think it does. Using the tools and techniques in the links I posted, it should be possible to determine which of these is the case.
If you are still having a problem, please post complete information.
What are all the formulas of the field?
What are the options of the field? Don’t forget the multivalue and delimiter options.
Is there any code that is handling this field, other than the formulas? If so, please show your code.
What do you find out from examining the document properties from a view? What is the value, what are the flags?