Upgrade to TFS 2013 Broke Multi Value Control

Topics: User Forum
Jun 17, 2014 at 4:49 AM
Hi,

Our server just got upgraded to TFS 2013 from TFS 2012. We were using version 1.1.1.0 for TFS 2012 Web Client, and it was working fine, but after the upgrade, we experienced very strange UI issues when using the web client:
  • The toolbar in the web view of the work item (with Save, Refresh, Undo, New Linked Work Item, etc.) disappeared.
  • Other controls stopped working or displayed weirdly
  • The field with the Multi Value control did not show any values within the dropdown menu.
I thought it might be because of a compatibility issue. But we upgraded to the 1.2.1.0 version for TFS 2013, and it's still the same behavior. Our only workarounds are to use the VS client or to change the Multi Value controls back to Field controls.

Any ideas of what's wrong or how to diagnose?

Thank you.
Jun 17, 2014 at 3:24 PM
Hi,

We are seeing this as well. I also get a red error box on the web when I try to create a new record with a multivalue control.

Cannot read property 'clear' of undefined
TypeError: Cannot read property 'clear' of undefined
at MultiValueControl.inherit.bind (https://XX/tfs/_static/tfs/12/_scripts/TFS/min /tfs/_plugins/1954/CodePlex.WitCustomControls.MultiValueControl.js:131:31)
at MultiValueControl.bind (        https://XX/tfs/_static/tfs/12/_scripts/TFS/min /corejs?v=_MSFW4OfdCDNeZq3uu091cS-RQBlKwXqd57IiCDpwKQ1:435:6134)
at MultiValueControl.<anonymous> ( https://XX/tfs/_static/tfs/12/_scripts/TFS/min /WorkItemTracking/Scripts/TFS.WorkItemTracking.Controls.js:4:17319)
at Function.v.extend.each (        https://XX/tfs/_static/tfs/12/_scripts/TFS/min /basejs?v=dGN7LpVYzz1ht2C3dYFc8lW3inYzn_TfeSHjG3xTgic1:24:17564)
at a.b.bind (                      https://XX/tfs/_static/tfs/12/_scripts/TFS/min /WorkItemTracking/Scripts/TFS.WorkItemTracking.Controls.js:4:17284)
at a.bind (                        https://XX/tfs/_static/tfs/12/_scripts/TFS/min /WorkItemTracking/Scripts/TFS.WorkItemTracking.Controls.js:4:18957)
The stack trace goes on, but from what I can see there seems to be missing files. I can't find the basejs or any of the WitCustomControls files.

I installed the extension using the extension manager. Did I miss something in the installation that the files didn't get placed properly?

Any thoughts or suggestions would be appreciated.

Thanks,
Jim
Jun 18, 2014 at 5:30 PM
Hi I just submitted a patch (Id 16490) with a new zip that will fix this issue.

So far, the fix has only been tested on TFS2013.2.

Since it did not go throught all the checks yet, please be shure to keep a copy of your prior version if you decide to go with the update.
Jun 18, 2014 at 6:26 PM
Thank for the update. From the initial testing I have done it has fixed the main problems we found.

Jim
Jun 25, 2014 at 2:42 PM
Is it possible that the web version is not saving the resulting string correctly as compared to the IDE version? On the web version the items are [Item1][Item2] on the VS version they are [Item1];[Item2] -- note the ';' inbetween the individual items.

The side effect is that whenever anybody touches a work item in VS that was modified in the web the work item changes.

Should the two implementations be the same?

Jim
Developer
Jul 20, 2014 at 7:02 AM
Can you post your work item type definition so that we can look at how you've defined the control?