Willy's Reflections - Visual Studio ALM Rangers

| Willy-Peter Schaub | Visual Studio ALM Rangers | In search of IT simplicity, quality and tranquility |

TFS Integration Platform … Should I use field name of reference name when defining field maps? Q&A-36

TFS Integration Platform … Should I use field name of reference name when defining field maps? Q&A-36

  • Comments 2

I noticed an email thread on which Grant Holliday was addressing a TFS Integration Platform migration session  that did not go as expected. Looking at the eye of the problem the question users of the platform could have is whether to use work item field names or reference names.

What’s the difference?

If we open a process template using the Process Editor Power tool, we notice that each field has a name and a reference name:

The field name is a friendly name, whereas the field is referenced by its reference name, for example when defining rules and conditions.

So what should we use when creating a field map?

When defining a field map you must use the “Reference Name”, not the “Field Name”.

INCORRECT use of field names:

<MappedField LeftName="MSIT.Description" RightName="Description" MapFromSide="Left" />
<MappedField LeftName="MSIT.AutomationStatus" RightName="AutomationStatus" MapFromSide="Left" />

CORRECT use of reference names:

<MappedField LeftName="MSIT.Description" RightName="System.Description" MapFromSide="Left" />
<MappedField LeftName="MSIT.AutomationStatus" RightName="Microsoft.VSTS.TCM.AutomationStatus" MapFromSide="Left" />

Other related references

  • Explaining the "why" of having to always do something is always appreciated, otherwise you're just like some grade-school religion classes I had.

  • @Dan, good point. In future we will ellaborate more on the "why".

    As mentioned in the post, the incorrect use of field maps results in unexpected behaviour, for example data not migrating as expected or migrations failing,

Page 1 of 1 (2 items)
Leave a Comment
  • Please add 5 and 8 and type the answer here:
  • Post