Clarification When Matching a Drop-Down Field to Database Column

asked on October 2, 2014 • Show version history

In the Forms 9.2 help files there is the following note:

Note: If you are matching a drop-down field to a database column, it will match the values assigned to each choice in the list instead of the choices themselves. If no value is assigned to a choice, the choice will be used instead.

In Forms 9.1 when you matched a drop-down field to a database column it just used the values from the lookup as the values and choices for the drop-down. Is this stating there is now a way to assign the values from the lookup as the drop-down field values and specify different choices?

Can someone give some clarification or possibly an example as to what this means exactly?

1 0

SELECTED ANSWER

replied on October 2, 2014

See the screenshot below

This is a sample drop down list where users can select either an "Accord" or a "Civic". If I have a lookup configured where it matches this drop down list to a database table, it will use the values "Honda1" or "Honda2" to match against the database column instead of "Accord" or "Civic". If the choices didn't have a value associated, then the lookup would try and match "Accord" or "Civic".

0 0

replied on October 2, 2014

So this is for doing a lookup from a drop-down selection, not actually populating a drop-down list, correct?

1 0

replied on October 2, 2014

Yes.

0 0

replied on October 3, 2014

Is there a way to get that auto-suggestion back? So that we can use it either way?

0 0

Question

Question

Clarification When Matching a Drop-Down Field to Database Column

Answer

Replies

Sign in to reply to this post.