TFS 2015报告仓库冲突 [英] TFS 2015 Reporting warehouse conflict

查看:55
本文介绍了TFS 2015报告仓库冲突的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们正在将12个团队项目迁移到新的集合和单个团队项目中。 作为此清理的一部分,我们将更新WIT定义中的自定义字段以匹配我们的新公司名称。 我们希望无限期保留旧系列
(只读),并希望能够使用仓库继续历史报告。 

We are migrating our 12 team projects into a new collection and a single team project.  As part of this cleanup we are updating the custom fields on our WIT definitions to match our new company name.  We want to keep the old collection on-line (read only) indefinitely, and want to be able to use the warehouse to continue historical reporting. 

旧的在名为CompanyA的项目集合中,我们在User Story WIT上有一个名为"Classification"的自定义字段。使用Refname为"CompanyA.Classification",将仓库报告为维度。 在新项目集合中,
CompanyB,我们有相同的字段"分类"。引用名称为"CompanyB.Classification"设置为维度报告。

In the old project collection called CompanyA, we have a custom field on User Story WIT called "Classification" with a Refname of "CompanyA.Classification", reporting to the warehouse as a dimension.  In the new project collection, CompanyB, we have the same field "Classification" with a refname of "CompanyB.Classification" that is set to report as a dimension.

仓库建立时,我收到以下错误:

When the warehouse builds, I get the following error:

< ResultMessage> [工作项跟踪仓库同步]:---> TF293000:数据仓库检测到以下工作项字段的数据冲突:


CompanyB.Classification< - > CompanyA.Classification(CompanyA);

发生冲突是因为为团队项目集合定义的可报告字段的属性集存在差异。数据仓库的更新将继续进行项目收集Amadeus。但是,在解决冲突之前,将暂停对
冲突字段的数据进行更新。您可以通过在所有项目集合中使字段的定义相同,或者通过在项目集合Amadeus中将字段标记为不可报告来解决这些冲突。有关更多
的信息,请访问以下Microsoft网站:
http:/ /go.microsoft.com/fwlink/?LinkId=160807.</ResultMessage
>

<ResultMessage>[Work Item Tracking Warehouse Sync]: ---> TF293000: The data warehouse has detected data conflicts for the following work item fields:
CompanyB.Classification<->CompanyA.Classification (CompanyA);
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 Amadeus. However, updates to the data for the conflicting fields are suspended until the conflicts are resolved. You can resolve these conflicts by making the definitions of the field the same in all project collections, or by marking the field as non-reportable in project collection Amadeus. For more information, see the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=160807.</ResultMessage>

如何在不更改字段中的名称的情况下解决此错误收集 (我们需要在两个地方进行"分类"以用于报告目的)并且不必保留旧的"CompanyA"。 refname,因为我们公司
现在是CompanyB,管理层希望它说"CompanyB",我希望能够看到"分类"。仓库中两个集合中的所有工作项目用于报告目的。

How do I get past this error without changing the name on the field in either collection (we need to be "Classification" in both places for reporting purposes) and not having to retain the old "CompanyA" refname since our company is now CompanyB, and management wants it to say "CompanyB", and I want to be able to see "Classification" on all work items in both collections in the warehouse for reporting purposes.

帮助! 我该怎么办?

Help!  how do I do this?

谢谢,

John

推荐答案

我尝试通过Witadmin更改报告引用名称,如下所示:

I attempted to change just the reporting refname through Witadmin as follows:

witadmin changefield / collection:http:// vqas052 :8080 / tfs / CompanyA /n:CompanyA.Classification /reportingrefname:CompanyB.Classification

witadmin changefield /collection:http://vqas052:8080/tfs/CompanyA /n:CompanyA.Classification /reportingrefname:CompanyB.Classification

我重建了仓库,它解决了我收到的错误信息。 不幸的是,我不再在CompanyA集合的任何工作项上看到"分类"字段。 我希望来自CompanyA和CompanyB
的工作项都有CompanyB.Classifcation,但他们不会:(

I rebuilt the warehouse and it resolved the error message I was receiving.  Unfortunately, I no longer see the Classification field on any of the work items from CompanyA collection.  I was hoping that work items from both CompanyA and CompanyB would have CompanyB.Classifcation, but they don't :(

我如何解决这个问题?  ;帮助!

How do I get around this problem???  HELP!


这篇关于TFS 2015报告仓库冲突的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆