Page 1 of 1

Invalid value in select box

Posted: Sat Jan 09, 2021 4:14 am
by rads
I have a question regarding select boxes.

We use lots of select boxes and the other day I had a problem we were not aware of.

We have select boxes for transport methods that are used in several screens.

Now somebody deleted a transport method that was used in a sales order - don't tell me we should use relational constrains, nobody uses relational constrains for every foreign key :)

Since the record in the list of transport methods has been deleted the select box appears to be empty although the key is populated with the value in the sales order. However, since there is no matching record in the table with the transport methods the user cannot see the key nor will he notice that the transport method has become invalid.

Any idea, anybody?

Perhaps (future release) select boxes should show a text like '?????' or "invalid", ... in such a case.

Best wishes

Rainer aus dem Spring

Re: Invalid value in select box

Posted: Thu Jan 14, 2021 3:39 am
by rads
Perhaps Profound might (for a future release) consider to define a new select box property for a default choice that is displayed when the value does not match any entry in the list.

Best wishes,

Rainer

Re: Invalid value in select box

Posted: Fri Jan 15, 2021 12:47 pm
by Scott Klement
For Profound to consider something like that, you'd need to put in a change request. You can do that by e-mailing support@profoundlogic.com

That said, the select box is simply an HTML <select> tag, and for us to change the way it behaves doesn't seem like a good idea? It is a standard agreed upon by all of the web browsers, and so forth. Is it really a good idea to make it work differently in your application?

Re: Invalid value in select box

Posted: Sat Jan 16, 2021 3:20 am
by rads
Scott Klement wrote:For Profound to consider something like that, you'd need to put in a change request. You can do that by e-mailing support@profoundlogic.com

That said, the select box is simply an HTML <select> tag, and for us to change the way it behaves doesn't seem like a good idea? It is a standard agreed upon by all of the web browsers, and so forth. Is it really a good idea to make it work differently in your application?
Do you have any other idea how to solve the problem ?

Rainer