After migration R5=>R6 Author cannot save his own documets

HCL Domino Domino Forum
1

Hello,

After migration R5->R6, the group of Authors cannot save their documents, if i set to Designer ( with create personnal views/folders and shared views/folders) it does work,

Setting Author with both attributes described above doest not work.

The problem is that the users cant be Designer, they must be Author.

I have Author type field in form, with @username as computed formula, only the creator can modify/save the document.

The strange thing is the fact that Authors type field does work in R6, it shouldnt stop working.

The code in save button is:

@PostedCommand([FileSave])

The code in “Create DOC” ( which is used in some workflow engine):

@If(@IsDocBeingEdited;“”;@Command([EditDocument]));

@Prompt([Ok];“aaaa”;“1”);

@Command([FileSave]);

@Prompt([Ok];“aaaa”;“2”);

@If(salva = “1”; “”;@Return(“”));

@Prompt([Ok];“aaaa”;“3”);

@PostedCommand([Compose];“frmProdEtapas”);

@Prompt([Ok];“aaaa”;“4”)

im able to get printed “2” , but appears the “you´re not authorized…” error before it .

Why is that? any tips?

2

Subject: After migration R5=>R6 Author cannot save his own documets

Make sure the field is truely an author field by checking the field value in the doument properties. The flags section should show:

Field Flags: SUMMARY READ/WRITE-ACCESS NAMES

It does not matter if the field on the form is set to an Authors field. It is still possible to have these flags cleared even though the form is set to Author. An editor or above refreshing / saving the document would resolve the isssue if this is the case.

Also make sure their username has not changed in some way since the upgrade.

3

Subject: RE: After migration R5=>R6 Author cannot save his own documets

so you´re saying that maybe changing Author to Editor can solve the problem? if yes, i will try tomorrow… server is down for an unknown reason =/

thanks anyway !

4

Subject: RE: After migration R5=>R6 Author cannot save his own documets

No I was saying the authors field on the document might not have the properties it needs ot make it truely an authors field.

5

Subject: RE: After migration R5=>R6 Author cannot save his own documets

It should solve the problem but will compromise the security of your database as editor access will allow people to edit documents that they have not created.

If it is a problem with the authors field no longer being recognised as name then run an agent using @Command( [ToolsRefreshAllDocs] ) which will solve the issue.

Otherwise as authors fields did not change the way they work in release 6 it is likely to be a username issue as Bruce suggested.