I thought the issue in my previous post was resolved, but alas. 

 

I managed to get the issue isolated.

I have an XPage related linked to a DominoDocument datasource.  On the Xpage I have only a submit button (either Save Document or Save Datasources). When I access an existing document using the ?editDocument url and click submit a Save conflict is generated.

 

The same behaviour occurs on the server as well as local. 

 

Here is the page source 

<?xml version="1.0" encoding="UTF-8"?>

<xp:view xmlns:xp="http://www.ibm.com/xsp/core"

xmlns:xc="http://www.ibm.com/xsp/custom" pageTitle="test">

<xp:this.data>

<xp:dominoDocument var="document1" formName="ePortfolio"></xp:dominoDocument>

</xp:this.data>

<xp:button value="Label" id="button1">

<xp:eventHandler event="onclick" submit="true"

refreshMode="complete">

<xp:this.action>

<xp:saveDocument></xp:saveDocument>

</xp:this.action>

</xp:eventHandler>

</xp:button>

</xp:view> 

in other words, if there was no Subject or Tags field on this Forums topicThread XPage it would result in a conflict for every update. 

 

In my case I use a repeat control to display a custom control for a set of documents. Depending on the state some are disabled, some enabled. Saving the datasources results in a save conflict for all the disabled custom controls.

 

The only workaround I found was setting the concurrencyMode to "force".