Hi, all-
Does anyone know if there is a limit as to how many selections can be added to a field in list manager?
We have a field and are trying to select 16 options, however we are unable to save and close when we hit 16.
We are fine with 15.
I didn't see this in any documentation so was wondering if I either missed it somewhere, or if others are experiencing this as well.
Thank you!
Rachel
Odds are high that List Manager converts multi-selects like that into a comma separated varchar of length 255, so I expect the cutoff is based on the length of the select id values.
Quite possible. But if you can be sure that your list of 16 values is well below that character limit, I would submit a ticket.
We just recently encountered a new situation, Version 15, using the List Manager element "Package History Package" wherein we could not select 10 values from the dropdown. 0 - 9 and 11+ worked just fine, but 10 did not. No idea why, and as those are 3-4 digit package numbers that is certainly well below any varchar limit.
Thank you both for your responses.
John A. Moskal II, very interesting. I tested it to see if I could select 17 values and I can. So 15 or 17 values work, but not 16. Looks like this is going to require a ticket...
Thanks for your help!
For what it's worth, we're also having a problem with not being able to select the number of values we want in a particular field. In our case, it's an attribute and we can only select 13 values in list manager. Fourteen values gives us the lovely 'string or binary data would be truncated' message.
Hi, Kathleen-
We don't even receive a message. We just cannot select the confirm and close option. I tested it a bit more this morning and found it is happening with several fields, but not all. Very strange!
Interesting: I'm guessing you can't look at the query List Manager when you add the problem element. Have you tried building it manually in SSMS?
That really sounds like the limit on the character string is being reached. Is the ref_idcol a text value or integer?
Oh sure. I can build it manually just fine when I go to "Show Query". I am 99.9% certain that the problem is not SQL related but instead probably in the .NET side of things. And I have tried with many varieties of different elements. It is the distinct count of the element, oddly enough, that is posing the issue, and it is almost definitely NOT SQL related, or, if it is, certainly not related to a varchar length or typical SQL/List Manager issue of the past.
I DID just today get a response to my ticket saying that that this is probably related to a newly discovered defect that as of yet is still unpublished on the master defect list. So keep your eyes open, I guess.
Gawain Lavers, that would make sense, however it seems our problem is that of which John has encountered.
I went on to add several more values, which if that didn't work, would lead me to believe it was a character limitation. However, since I was able to do this, I am thinking it must be a defect of some sort. I am able to manually build, but we have many users who pull their own lists and aren't able to use that method. For now, we are using a work around of splitting the criteria in two and using the alternate criteria and adding the same field selecting the rest of the values.
I appreciate everyone's input!
Yeah, that seems certain (although I think Kathleen's issue may still be with the size of the list, given the error message). Mostly I recommended building manually in case the problem selections had some sort of rhyme or reason to them (problematic character in the description, for instance, or a duplicate id or something like that).
An update: what we were encountering was in fact a defect and will be fixed with the v15.0.7 service pack.
Appreciate everyone's insight.
Best,