-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting error "not in the supported list of values" #5
Comments
trying to add this control to one of our work items. please suggest what is wrong in following can u upload a sample work item definition file |
Thank you. That seemed to work. On Nov 22, 2016 12:30 PM, "Palasin" notifications@github.com wrote:
|
can u upload a sample workitemdefiniton file which uses this control |
We are using Visual Studio Team Services so I do not have a workitemdefinition that I can post. |
How is translated the check: "Allow users to enter their own values" into the XML? I have tried the ALLOWEXISTINGVALUE and had the same error. |
Sebastian have you tried SuggestedValues? That lets you create an initial list but a user can add something else if they want (at least that's how I remember it working when I was using TFS). |
Thanks! Solved using the SuggestedValues! |
After setting up the Multivalue control I tested it and when I choose more than one I get an error saying "The field 'Products' contains the value ' (9 names of my products) that is not in the list of supported values." The custom field is originally set up as a string picklist. I get that error when I try using just the picklist. I tried setting up it up using the individual fields like in the example but get the same error. I tried just the semicolon no spaces and semicolon with a space in between each name. I get the error both ways. I tried in both Chrom and IE 11 but got the same error. I then tried it in a different VSTS instance and it worked there. The first is my production environment that was set up in June this year. The 2nd instance is a personal instance set up several years ago. I've attached a screenshot with the error.
The text was updated successfully, but these errors were encountered: