Merging Save Conflicts - isnt' there a way?

I guess I didnt realize this before… but the form property to merge conflicts… etc are only for Replication conflicts… So… isn’t there a way to merge Save conflicts?

Our scenario is… we have a field in our DB [field 1] and it needs to display the status of a form in a different database. We added code to the Save button in that other database so that if the status is changed, when the user clicks Save, it updates the field in our database for that corresponding document. (they have a common field to ‘link’ on )

However… IF a user is in OUR document - in Edit mode… when they Save the document in OUR database, they get the Conflict message and a conflict document is created.

HOW can we merge this…updated field with the document a user might be in ???

Subject: Merging Save Conflicts - isnt’ there a way?

Maybe you can prevent this with document locking?

JYR

Subject: RE: Merging Save Conflicts - isnt’ there a way?

i do not believe that doc locking can do any help …

2 ideas:

1st - you mentioned the merging property of the form with rep conflicts: Maybe it’s possible to let your “status” agent of your other db changes the field in a different replica (on a different server) of this db?

2nd - you can try to proof in the querysafe event (LS) if sth in the backend doc has changed. But it’s NOT easy to get that changed backend doc: not just possible with notesuidocument.document property, this just gives you the backend doc of the current user’s uidoc. (as far as I know)

HTH

Uwe