locked
The data warehouse has detected data conflicts for the following work item fields RRS feed

  • Question

  • Hi

    I get the following error

    TF293000: The data warehouse has detected data conflicts for the following work item fields: Microsoft.VSTS.Common.ReviewedBy<->Microsoft.VSTS.Common.ReviewedBy (abc). The conflicts occur because there are differences in the attributes set for reportable fields that are defined across team project collections. Updates to the data warehouse will continue for project collection xyz. However, updates to the data for the conflicting fields are suspended until the conflicts are resolved.

    I checked all these attributes (Reporting Name, Reportable and Type) they are all same in both the collections

    The only difference found was in the xml is as below, i.e. syncnamechanges was set true for one collection

    <FieldDefinition name="Reviewed By" refname="Microsoft.VSTS.Common.ReviewedBy" type="String" syncnamechanges="true" reportable="dimension" />

    <FieldDefinition name="Reviewed By" refname="Microsoft.VSTS.Common.ReviewedBy" type="String" reportable="dimension" />

    Tried making syncnamechanges as true in test environment it worked fine (TFS 2017 Update 1) and in production too

    It doesn't allow to make it "false" why?

    TF401327: The operation is not supported. The feature is obselete.

    Regards,

    Krupali Desai


    Tuesday, September 12, 2017 10:14 AM

Answers

  • Hi Krupali Desai,

    Which version of tfs do you use? In TFS 2015, we deprecated the ability to change the syncnamechanges property on a field. Fields marked as "syncnamechanges=false" through identity rules cause issues for the client object model.

    For more detail information, please refer to  Team Foundation Server 2015 known issues .

    Best Regards


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Desai Krupali Wednesday, September 13, 2017 10:16 AM
    Wednesday, September 13, 2017 9:49 AM

All replies

  • Hi Krupali Desai,

    Which version of tfs do you use? In TFS 2015, we deprecated the ability to change the syncnamechanges property on a field. Fields marked as "syncnamechanges=false" through identity rules cause issues for the client object model.

    For more detail information, please refer to  Team Foundation Server 2015 known issues .

    Best Regards


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Desai Krupali Wednesday, September 13, 2017 10:16 AM
    Wednesday, September 13, 2017 9:49 AM
  • Hi, 

    Thanks for reply.

    We are using tfs 2017 update 2.

    Regards,

    Krupali Desai

    Wednesday, September 13, 2017 10:15 AM