Error TF20015 - The field {0} contains a value that is not in the list of supported values.

Question

 

I have a new field to replace the System.Reason field because once you save a Work Item that field becomes Read only and can only be changed on a transition.

So I created a new field with 2 conditional rules based on System.State. But when I try to save the Work Item I get an error that says the value in DashReason is not in the list of supported values.

When I create a new WorkItem the State is Active and the DashReason is New (based on the default in the WHEN tag). New is in the list of ALLOWEDVALUES. The Field definition is included below.

This is driving me nuts. What am I doing wrong?

 <FIELD name="DashReason" refname="Nowcom.Dash.Reason" type="String">
          <ALLOWEDVALUES>
            <LISTITEM value="New" />
            <LISTITEM value="Reviewing" />
            <LISTITEM value="Accepted" />
            <LISTITEM value="Duplicate" />
            <LISTITEM value="As Designed" />
            <LISTITEM value="Contact Software Support" />
            <LISTITEM value="Fixed" />
          </ALLOWEDVALUES>
        <ALLOWEXISTINGVALUE />
        <WHEN field="System.State" value="Active">
          <DEFAULT from="value" value="New" />
          <ALLOWEDVALUES>
            <LISTITEM value="New" />
            <LISTITEM value="Reviewing" />
            <LISTITEM value="Accepted" />
          </ALLOWEDVALUES>
        </WHEN>
        <WHEN field="System.State" value="Resolved">
          <DEFAULT from="value" value="Fixed" />
          <ALLOWEDVALUES>
            <LISTITEM value="Duplicate" />
            <LISTITEM value="As Designed" />
            <LISTITEM value="Contact Software Support" />
            <LISTITEM value="Fixed" />
          </ALLOWEDVALUES>
        </WHEN>
      </FIELD>

 

Thanks,

-- Robert

Answer 1

Could you make that field visible and tell what is the actual value of that field?

Thanks,

Alex

Answer 2

Field is visible and when State = Active the value in my field is "New" (minus quotes of course).

 

 

Answer 3

This looks like a bug. However, try replacing DEFAULT rules with COPY - this may help.

Alex

Answer 4

Aliaksei Baturytski - MSFT wrote:

This looks like a bug. However, try replacing DEFAULT rules with COPY - this may help. Alex

This didn't help at all. Any other ideas? I really need a work around to this.

As far as I can tell this is simple operation. This field definition is not that complicated. It should work.

 

Answer 5

Alex I got it working.

Looks like it was all my fault. In a comedy of errors sort of way.

 

1. In the UI I had changed the field to point to System.Reason instead of Nowcom.Dash.Reason so even though the drop down looked like it was showing the right values it was actually a different set of values.

2. But thats not all. The kicker was in another conditional rule I was defaulting Nowcom.Dash.Reason to a value "Ready to Test". This is what it was complaining about. I guess this one was happening after the conditional rules I showed you so it would error out because this isn't in the list. This was a left over from something I had tried the day before.

Everything works now.

If I can make a humble suggestion: if error TF20015 was written like this: The field {0} contains a value [{1}] that is not in the list of supported values. I would have been able to solve this in less than 30 secs rather than spend a day.

For anyone else paying attention to this thread: The moral of the story is to check all Defaults for your field throughout the whole WIT file.