readers field doesn't works properly ?

[Toma Bogdan]

I have an readers fields in a document. I have moved the database from a server to another. I have changed the values/names from the readers field with a Lotus Script agent.

Now the users that are in the modified readers field doesn't see the documents ! Why ? Should I need to make another updating operations ?

PS. The Enforce a consistent... checkbox is checked and I have updated the Administration server from ACL database settings.

[Semeaphoros]

Why did you change the names? that does not have anything to do with the change of the hosting server, except, that this server has to be in one of the reader-fields to be able to see the documents for replication or so.

from what to what have you changed the names?

Did you use the fully qualified name? (see here: Notes Namesystem

And look also at this document:

Overview ACL

BTW: Best Practices on this board is a very useful resource for this type of problems

[Toma Bogdan]

Why did you change the names? that does not have anything to do with the change of the hosting server, except, that this server has to be in one of the reader-fields to be able to see the documents for replication or so.

from what to what have you changed the names?

Did you use the fully qualified name? (see here: Notes Namesystem

And look also at this document:

Overview ACL

BTW: Best Practices on this board is a very useful resource for this type of problems

unfortunatelly, I don't understand German just English ...  

On the first server (server 1) I had user1/123/DOMAIN_OF_SERVER1. On the second server I need to change the username (the OU) so now I have user1/456/DOMAIN_OF_SERVER2

So I was forced to update the readers field so users to access their documents. But even updating the readers field with the LS agent, they can't access them  

[Semeaphoros]

Hey, the user-name does not depend on the server, the database is residing on, but solely from what is defined inside the ID-file, that resides on the client-workstation, so if you change their names, they have to change ID-file or they have to be renamed by the appropriate administrative process, so what you did does not make sense in my eyes.

And, you are referring to the names in its abbreviated form. Do you have the names in canonical form in the readers-field? That is

CN=user/OU=123/O=Organisation ?

They have to be in canonical form to work inside readers and authors fields

[Toma Bogdan]

Hey, the user-name does not depend on the server, the database is residing on, but solely from what is defined inside the ID-file, that resides on the client-workstation, so if you change their names, they have to change ID-file or they have to be renamed by the appropriate administrative process, so what you did does not make sense in my eyes.

they are the same people but they have another IDs (new IDs) according with new server !

And, you are referring to the names in its abbreviated form. Do you have the names in canonical form in the readers-field? That is

CN=user/OU=123/O=Organisation ?

They have to be in canonical form to work inside readers and authors fields

In the readers field I have user/123/Organisation not CN=user/OU=123/O=Organisation but before it works (when I have used user/123/Organisation)

[Semeaphoros]

It may or may not work with abreviated names, usually it does not.

Are you sure, that it has been abbreviated before and was not only displayed in the abbreviated form? This is very usual practice with readernames and author-fields

[Toma Bogdan]

Are you sure, that it has been abbreviated before and was not only displayed in the abbreviated form? This is very usual practice with readernames and author-fields

I am sure. I use the sytax name/OrgUnit/Organization and it works !

[Hernan Cortez]

Are you sure, that it has been abbreviated before and was not only displayed in the abbreviated form? This is very usual practice with readernames and author-fields

I am sure. I use the sytax name/OrgUnit/Organization and it works !

As far as I remember the abbreviated form gets converted automatically when you type them in an editable field or use abbreviated form in formulas for computed fields.
You might check the properties box for the document, to see if you find something strange there.

Axel

[Semeaphoros]

Yes, usually it does, if you don't overwrite that behaviour, and hence it is saved as canonical and not abbreviated. But it does not, if you fill the fields directly in the backend-document by LotusScript

[Toma Bogdan]

Yes, usually it does, if you don't overwrite that behaviour, and hence it is saved as canonical and not abbreviated. But it does not, if you fill the fields directly in the backend-document by LotusScript

so the best thing I should do is to modify the readers field with LS to get the canonical values, isn't it ?

[Semeaphoros]

No, with LS you have to supply the canonical form of the name yourself, this translation is done in the UI.

You can do the following within LS:


dim namTemp As NotesName

set namTemp = New NotesName ( "username/Department/Organisation" )

print namTemp.canonical

to convert from abbreviated to canonical with LS

[Toma Bogdan]

No, with LS you have to supply the canonical form of the name yourself, this translation is done in the UI.

You can do the following within LS:


dim namTemp As NotesName

set namTemp = New NotesName ( "username/Department/Organisation" )

print namTemp.canonical

to convert from abbreviated to canonical with LS

it is exactly that I said before your last reply: to modify the actual values from abbreviated to canonical with a LS agent.

[Hernan Cortez]

it should be a good idea to work with item class. Item class has properties like isReaders and some such.

[Toma Bogdan]

it should be a good idea to work with item class. Item class has properties like isReaders and some such.

is it necessary to set

Code

note.IsReaders=True

after I have modified the readers field with the LS agent (even the field is READERS by default) ?

[Toma Bogdan]

Yes, usually it does, if you don't overwrite that behaviour, and hence it is saved as canonical and not abbreviated. But it does not, if you fill the fields directly in the backend-document by LotusScript

I have used the canonical values but the behaviour is the same. The users that are in that readers field can't see the doc.
here is the code for updating the readers field:

Code

   While Not(note Is Nothing)
      Limits=Ubound (note.Reviewers)
      Redim Preserve New_values(Limits) As String
      For i=0 To Limits
         New_values(i)=note.Reviewers(i)
         Set curent_CN = New NotesName(New_values(i))
         name=curent_CN.abbreviated
         ' I perform a search into the employee db to get the full name based on abbreviated name
         Set employee_doc = view.GetDocumentByKey (name)
         If Not (employee_doc Is Nothing) Then
            If employee_doc.form(0) = "Job" Then
               Set full_name=New NotesName(employee_doc.name_CN(0))
            Else
               Messagebox("Can't be found" & name)
            End If
            
            New_values(i)=full_name.canonical
         End If      
         
      Next
      note.Reviewers=New_values
      Dim item As NotesItem
      Set item = note.GetFirstItem( "Reviewers" )
      item.IsReaders=True
      Call note.Save(True,False)
      Set note = collection.GetNextDocument(note)
   Wend

[Toma Bogdan]

it seems that if I enter manually into the doc and I save it the readers fields works fine !

how can I do this with LS (because I have over 1000 docs) ?

As you can see

Code

note.Reviewers=New_values
      Dim item As NotesItem
      Set item = note.GetFirstItem( "Reviewers" )
      item.IsReaders=True
      Call note.Save(True,False)

I try to set True to IsReaders property of the Readers fields but the users can't see the doc !

[Semeaphoros]

As Alex (El Indio Mapuche) already said, try to verify with the documents properties-box, if the field and the field values are set correctly. I don't see, where the problem now is. Maybe that you should work with the NotesItemClass from the beginning and using that class throughout the whole code instead of only "rearanging things" at the end of the procedure.

[Toma Bogdan]

these are the steps:

1) Reviewers field should be of type Readers and MULTIVALUE
2) Check the document properties for the defination of this field ie,
Data Type should be "Text List". Field Flags should be "SUMMARY READ-ACCESS NAMES"
3) Names format should be CANONICALIZE

10x

[Semeaphoros]

Sorry, but I don't have any further idea at this point ...
This looks correct

[Toma Bogdan]

now it works... I need to update all docs  

Code

@Command([ToolsRefreshAllDocs]);
 @All