HelloI’m using notesDocument.lock function at webService. Sometimes i’m getting an error “You cannot update or delete the document(s) since you are not listed as an allowable Author for this document”. Efficient user has an manager access to DB. What’s the problem?
Subject: check reader/author field type from document property.
Hi
Just check if the user is part of reader/author field. If he/she is there in the reader/author field, then just check if the document security fields(reader/author) fields are created as reader/author fields.
Sometime, you might have reader/author fields created in the document but it might be created as text list field. It could be one of the reasons for ur err.
Regards,
Karthik KS
Subject: But the user has MANAGER access to DB. Doesn’t it enough to lock document?
Subject: It sounds to me like the user actually does NOT have Manager access.
If the access was changed very recently, it may be that the old access was cached. Use the access icon on the status bar to determine what the system thinks the user’s access is currently.
Subject: Sounds like code is getting this error…
- Check for a $Writers field on the document when this happens. Even Manager cannot take a lock if it exists; but Manager can remove any lock, then apply their own. My experience with code doing locking is that it randomly fails to actually remove the $Writers field from the document. This is so frequent that I wrote a LockManager class that, after unlocking, ensures $Writers is in fact deleted, among other weirdness hacks.
Hope this helps…