Hi,
I have some users who aren’t able to view their documents. They have editor access and are listed in the reader’s field in canonical format. Multi-values are enabled and each reader name in the field are enclosed in double quotes separately.
I’ve tried “Troubleshooting reader’s and writer’s fields” from one of the posts but to no avail. Is there something I’m missing?
My current workaround is to either refresh the document or input the user’s name in a newly created (editable) reader’s field. The latter always works but the former works only sometimes.
Hope someone can advise. Thanks in advance!
Regards,
Chee Siong
Subject: Some users cannot see doc
What does field flags say for the readers field? Does it show it as a READ-ACCESS NAMES?
I’m just curious if for the problem documents it doesn’t know it’s a readers field. Maybe something a result of an agent.
BTW, not that it’s really any of my business, why Readers and Editor access vs just using Readers and Authors with Author Access?
Subject: Some users cannot see doc
There really isn’t so much that can go wrong with reader fields. If you allow multiple values and list names in full canonical format, the only not so uncommon thing is, that some code (e.g. executed by a scheduled agent) changes the field type back to a normal text item.
Judging from your post, you most probably did that already, but when checking that the readers fields are OK, make sure to NOT open the document, but just have a look at the properties dialog, fields tab, from the view level. If a newly added readers field, containing exactly the same name(s) solves the problem, this would normally indicate, that there are multiple readers fields and at least one of them has been reverted to a text field.
Sorry, not much more to suggest.
Subject: RE: Some users cannot see doc
Yes it shows READ-ACCESS NAMES. I should probably reduce the access level to author access. (not too sure why it was created as such by the previous developer)
You might be right about agents changing the readers field to a text field. It seems to occur when the documents have been processed by an agent run by another user. Let me check the readers field again when the next problem comes in. I can’t seem to replicate the problem. Anyway, how does the agent revert the field to one of text type?
Yes I remember that on one of the problem docs, the properties dialog from the view does not show full canonical format, but it does when I open the document. Will take note of this…
By the way, the original readers field resides on a subform. I’ve put the newly created one on the form itself. Also, the $KeepPrivate field keeps getting set even when the default access has replicate or copy privileges checked. Not sure if these will cause any problems.
Thanks,
Chee Siong
Subject: RE: Some users cannot see doc
Something as simple as
FIELD FieldName := “CN=New User/O=Company”
or
doc.FieldName = “CN=New User/O=Company”
could result in a normal text item to be stored, replacing the readers field. When updating reader fields, the safe way is to always get a NotesItem object and set it’s Readers property to true after replacing its value.
Never trust anything you only see, when you open a document. Domino really only cares about what is stored in items, not what might be displayed through fields, that might be on a form.
Form or subform shouldn’t make a difference.
There are a couple of reasons, why a $KeepPrivate item might be generated. Users (or agent signers) not having the right to copy documents is just one of them. There is e.g. a form property to prohibit printing, forwarding and copying. Of that was set and a document is saved through that form (either in the front-end or using the computeWithForm method), this would result in $KeepPrivate = “1” as well.