-
Notifications
You must be signed in to change notification settings - Fork 46
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
Total Character Limit for Multiple Items #295
Comments
It doesn't have any effect on the field even though adding the limit in the field configuration. |
Thanks for reporting, we'll dig into this |
Just checking to see if there's been any luck with this |
@AminTi - any update on this issue resolution as I am also running into a similar issue report by @shaun-borlinghaus. I havent found a workable solution and was curious if there was a timeline for a fix for anyone else experiencing this issue. Thanks! |
@AminTi Because we need every value to appear we need to cut the name off at 15 for consistency to ensure we are able to put the values into our system. I think my issue is related, but if it's not feel free to create a new issue. |
@AminTi -- Just following up to see if there is any progress for this. |
@AminTi -- following up again to see if there is any progress with this? We are being limited in our workflow. |
We have a picklist field that allows multiple items to be checked for inclusion. The total list has over 200 items or so with varying lengths of items. I can select items up until it reaches a total character limit of 240 characters across all selections. Is there a configuration option that will allow for a total character selection of larger than 240 characters? Once it reaches 240 total it shows "The value for field 'field name' is too long." and "Set the field Filed Name to use suggested values rather than allowed values". I've altered the "set maximum display length for each option's label" to a random number above 240, but it looks like that is only a limit per each individual picklist option.
The text was updated successfully, but these errors were encountered: