Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 949803 - Last Review: February 27, 2008 - Revision: 1.3
Microsoft Team Foundation Server Integration in Microsoft Project is broken after editing the Microsoft Project Mapping File
Source: Microsoft Support
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Using the Microsoft Team Foundation Server TFSFieldMapping.exe utility, you download a Microsoft Project mapping file. You edit the field mappings, setting the "ProjectField" of the "System.Reason" to the same value used by the SyncField mapping. For example:
<?xml version="1.0" encoding="utf-8"?>
<MSProject>
 <Mappings>
  …
   <Mapping WorkItemTrackingFieldReferenceName="System.Reason" ProjectField="
pjTaskText25" />
  …
   <SyncField ProjectField="
pjTaskText25" />
 </Mappings>
</MSProject>
(NOTE: This is just a specific example of two items sharing the same ProjectField mapping)
You upload the modified Project mapping file. You launch Microsoft Project and connect to the team project on your Team Foundation Server whose field mappings were modified in the previous steps.
The Microsoft Team Foundation Server integration inside Microsoft Project will not be completely functional. Here are some of the symptoms the user may experience:
Using Integration with Microsoft Project and Microsoft Team Foundation Server 2005 Client
- Retrieving work items from the server is not functional. Work items inserted into the task sheet using the "Get Work Items" dialog will be missing the values of several fields, including the Work Item ID and the Title.
- Publishing is not functional. Publishing new work items will be reported as successful but the work items are not actually published. The Work Item ID field will remain empty.
- In addition to the usual "Yes", "Refresh only" and "No" values in the "Publish and Refresh" column drop-down, the list will also include values defined for the TFS field that is sharing the same ProjectField as the SyncField. For example, if System.Reason is sharing the ProjectField then the values in the drop-down box will be:
- Accepted
- As Designed
- Avoided
- New
- No
- Refresh Only
- Yes
- The default value set by the Team Add-in for the "Publish and Refresh" column won't be "Yes" as usual. Instead it will be the default value defined for the TFS field sharing the ProjectField with the SyncField. For example, if System.Reason is sharing the ProjectField then the default value will be "New"
         Â
Using Integration with Microsoft Project and Microsoft Team Foundation Server 2008 Client- Publishing is not functional. Publishing new work items will report an error. Publishing changes to existing work items will report as successful but the work items won't be actually published.
- In addition to the usual "Yes", "Refresh only" and "No" values in the "Publish and Refresh" column drop-down, the list will also include values defined for the TFS field that is sharing the same ProjectField with the SyncField. For example, if System.Reason is sharing the ProjectField then the values in the drop-down box will be:
- Accepted
- As Designed
- Avoided
- New
- No
- Refresh Oly
- Yes
- The default value set by the Team Add-in in the "Publish and Refresh" column won’t be "Yes" as usual. Instead it will be the default value defined for the TFS field sharing the ProjectField with the SyncField. For example, if System.Reason is sharing the ProjectField then the default value will be "New"
Â
When editing the Microsoft Project mapping file from your Microsoft Team Foundation Server, do not reuse the ProjectField mapping on the SyncField entry. In fact,
ALL ProjectField mappings in the Microsoft Project field mapping file should be unique.
For more information on the TFSFieldMapping.exe utility, refer to this MSDN entry:
http://msdn2.microsoft.com/en-us/library/ms252493.aspx
(http://msdn2.microsoft.com/en-us/library/ms252493.aspx)
For more information on the Microsoft Team Foundation Server Project mapping file, refer to this MSDN entry:
http://msdn2.microsoft.com/en-us/library/ms181686.aspx
(http://msdn2.microsoft.com/en-us/library/ms181686.aspx)
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALSâ€) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
APPLIES TO
- Microsoft Visual Studio 2005 Team Foundation Server
- Microsoft Visual Studio Team System 2008 Team Foundation Server
- Microsoft Office Project Standard 2003
- Microsoft Office Project Professional 2003
- Microsoft Office Project Professional 2003, Service Pack 1 (SP1)
- Microsoft Office Project Standard 2003, Service Pack 1 (SP1)
- Microsoft Office Project 2003 Service Pack 2
- Microsoft Office Project 2003 Service Pack 3
- Microsoft Office Project Standard 2007
- Microsoft Office Project Professional 2007
- Microsoft Office Project 2007 Service Pack 1
| kbnomt kbrapidpub KB949803 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate