When I import my solution in Servoy 501 , the problem tab shows 38 warning with valuelist.
Editable combobox bascal1 has attached a valuelist that contains real values. This is not supported.
In Servoy 500 all works OK.
Thanks Armin
This warning means that you have a combobox that it’s editable and the valuelist that is attached to it has both real and display values. In editable combo you can type anything you want so real value should be the same as display value.
lvostinar:
This warning means that you have a combobox that it’s editable and the valuelist that is attached to it has both real and display values. In editable combo you can type anything you want so real value should be the same as display value.
Laurian - can you expand on this please as I for one don’t get it!! (not unusual of course).
I have a combobox that has a valuelist, the combo is editable so the user can enter anything he wants - but he’s assisted by the valuelist in using a predetermined list. He has the choice to use the valuelist data or enter his own.
Why is this flagged as a warning in 501?
I ran into this error too when I upgraded to 5.0.1 After some experimentation I came up with the following conclusion:
My value lists are all based on database tables. Unselecting the edit checkbox on the properties sheet for the combo box eliminates the error and still allows the user to select values from the list. These are still returned properly by the data provider to the field in the form. My thinking on the error is that selecting the editable property on a combo box implies that the combo box can modify the database table it is associated with (which it can not). This error is not thrown with a custom valuelist where the selections are populated in the editor. A combo box is editable by default. You need to change it to a textfield if you don’t want the user to modify the current value. I’m not sure why the logic changed with this release but it kind of makes sense.
Hope this helps clarify.
Chuck.Amata:
I ran into this error too when I upgraded to 5.0.1 After some experimentation I came up with the following conclusion:My value lists are all based on database tables. Unselecting the edit checkbox on the properties sheet for the combo box eliminates the error and still allows the user to select values from the list. These are still returned properly by the data provider to the field in the form. My thinking on the error is that selecting the editable property on a combo box implies that the combo box can modify the database table it is associated with (which it can not). This error is not thrown with a custom valuelist where the selections are populated in the editor. A combo box is editable by default. You need to change it to a textfield if you don’t want the user to modify the current value. I’m not sure why the logic changed with this release but it kind of makes sense.
Hope this helps clarify.
Thanks for that feedback Chuck - and I understand your point. But, in other environments this is called ‘limit to list’ and is developer selectable.
In the circumstances where a user uses the list to make a selection of previously entered data easy (valuelist is based on that column of the database or a library list), but where the data he chooses to enter is is not in the list - he needs to have that ability - does he not???
Imagine the library list has entries 1 thru 20, and that’s what the valulist is populated against - however the entry he needs to make is 21 - should he not be able to do so??? Surely that’s what the editable flag is for. If you as the developer choose not to allow extra data entry then so be it. But if I want my user to have the ability to select easily from a combo list - but also to add his own entry then surely that MUST be available???
Ian,
This all works fine with Servoy, except when the valulelist has different display and real values.
If you have a value list { a=1, b=2, c=3 } the user types a or b or c and the dataprovider is populated with 1 or 2 or 3.
When the user types something else there is no value to store in the dataprovider.
That is what the new problem marker is warning for.
Rob
rgansevles:
Ian,This all works fine with Servoy, except when the valulelist has different display and real values.
If you have a value list { a=1, b=2, c=3 } the user types a or b or c and the dataprovider is populated with 1 or 2 or 3.
When the user types something else there is no value to store in the dataprovider.That is what the new problem marker is warning for.
Rob
Ah Rob - so its only on a Custom valulist - that makes sense - it’s not on a valuelist that draws from a database column.
Then those error really are valuable!
Thanks for the clarity.
Ian,
No, it is for value lists that have real and display values, regardless of the value list type.
If you have a value list that shows a product name and returns a product id from the products table, you cannot use it for an editable combo box.
Rob
rgansevles:
Ian,No, it is for value lists that have real and display values, regardless of the value list type.
If you have a value list that shows a product name and returns a product id from the products table, you cannot use it for an editable combo box.Rob
OK Rob - I get it. Thanks for the clarification.