Doc with $Conflict won't allow Agent to set new field

HCL Domino Domino Forum
1

Hi all,

We have some documents that are Rep Save Conflicts.

The docs have both a $Conflict field and a $Ref field.

We want to copy/paste all these to a new Db and then delete them from the old DB, but as the $Ref will change when pasted, we want to first save the old $Ref to (say) OldParentUNID using the following Agent :

tmp := @Text($Ref);

FIELD OldfParentUNID := tmp

When this Agent runs on any doc that has a $Conflict field, the new field OldParentUNID is not created.

Is there some restriction about creating new fields on docs with a $Conflict field.

Ray.

2

Subject: Doc with $Conflict won’t allow Agent to set new field

Use @SetField Function. For updating the the field OldfParentUNID

tmp := @Text($Ref);

@setfield (“OldfParentUNID”; temp)

Hopes this work ?

3

Subject: RE: Doc with $Conflict won’t allow Agent to set new field

Thanks for your reply.

Unfortunately, I tried that as well - but it also doesn’t create the new field.

I think there is a restriction when a doc has a $Conflict field - although I can find no documented evidence of this.

I suppose it could be argued as logical, in that changing the conflict in the back end would make it different to the original and no longer a conflict - but also not a doc. Strange logic!!!

Ray.

4

Subject: RE: Doc with $Conflict won’t allow Agent to set new field

I’ve now tried LotusScript and it works.

Using normal backend script processing I can get a handle to the $Conflict doc, save the $Ref in a new field called OldParentUNID and save the doc.

Works as normal.

Why doesn’t a simple Formula work but LS does?

Ray.