Why do I get "publishing errors" in the following scenario:
- open a set of workitems in MS Excel
- clear the contents of a field that has a frozen rule (for all rows)
- publish the changes
- select a new valid value for the field that was cleared (for all rows)
- publish the changes
--> conflicting field errors occurs
You have to select either the "Local version" value or the "Server version" value.
What's the difference with the first change (from old value to empty value) ?

Refreshing the list does not change this behavior.

Hello,

I was not able to reproduce the issue you had.

When you are publishing validation will happen in similar way both for many rows or single row.

Can you please provide you Frozen rule and the state of the work item when you cleared the field and published it.

Thanks,

This is the code
<FIELD name="Project" refname="Company.Common.Module" type="String" reportable="dimension">
<ALLOWEXISTINGVALUE />
<FROZEN />
<WHEN field="Company.Common.Unit" value="Unit-1">
<ALLOWEDVALUES>
<LISTITEM value="Module-1" />
<LISTITEM value="Module-2" />
<LISTITEM value="Module-3" />
</ALLOWEDVALUES>
<COPY from="value" value="Module-1" />
</WHEN>
<WHEN field="Company.Common.Unit" value="Unit-2">
<ALLOWEDVALUES>
<LISTITEM value="Module-1" />
<LISTITEM value="Module-2" />
<LISTITEM value="Module-3" />
</ALLOWEDVALUES>
<COPY from="value" value="Module-2" />
</WHEN>
</FIELD>

Create a few workitems and make sure the module field is set through the copy rule.
Select these work items from the result view (e.g.:All Workitems query) and right-click "Open selection in MS Excel".
In MS Excel clear the module field for all workitems and publish the changes to TFS.
In MS Excel set the module field for all workitems to "Module-3" and publish the changes to TFS.
This results in the 'conflict'-dialog.

If you refresh the workitems in MS Excel and only change one of them to the new value then this conflict does not occur.

Hello,

Thanks for sharing the rule. This is definitely a bug in our end. Sorry for coming across this issue.

I will report this bug in our database.

Thanks,

We use this functionality a lot and our project managers are complaining about this behavior.

Any idea if this is fixed in SP1 or if a possible workaround exists ?