If a document is created in backend (db.CreateDocument) and then opened in UIWorkspace without saving it, it causes a save conflict 2nd time saving it, when R6 feature Locking is enabled.Is there anything i forgot, or any way to solve this problem ???
I can’t switch all functions to ws.compose and i want to get rid of our self programmed locking stuff.
Any help would be great!
Thanks
Subject: What sort of conflict?
Maybe, it appears because the document can’t be locked before it is saved.
I tried to learn to use R6 Lock feature last week, but found “our self programmed locking stuff” is yet more reliable. If you have replicas of your database on different servers, stick to old method (The locked document from Master Lock server replicates to secondary server and remains locked until next replication, if servers are offline).