WHERE Clauses and Bind Variables for Validation Tables (User, System Administrator, and Flexfields Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

WHERE Clauses and Bind Variables for Validation Tables

You can use validation tables with WHERE clauses to set up value sets where one segment depends on a prior segment that itself depends on a prior segment ("cascading dependencies").

Using bind variables in WHERE/ORDER BY clauses

You may use special bind variables, such as :block.field, :$PROFILES$.Option_name, or :$FLEX$.Value_set_name, in your WHERE/ORDER BY clause. However, you may not use them in the Value Column or Hidden ID Column fields (where you would normally specify a column name), even if you do specify a SQL fragment instead of specifying a single column name. You may use bind variables in the Description Column and Additional Columns fields.

Attention: If you are using flexfields server-side validation, you cannot use form field references (:block.field). You must either remove your field references or turn off flexfields server-side validation using the profile option Flexfields:Validate on Server.

See:

Flexfields:Validate on Server

Attention: You may not use a DISTINCT clause in any of the column fields or in your WHERE/ORDER BY clause (you should use a view with a GROUP BY clause instead of your actual table).

If you are using a validation table with special arguments such as :$FLEX$.Value_Set_Name for your value set, you should specify No in the Enable Security field, since any security rules you have for your value set would ignore the values of these special arguments, and your rules could have effects other than what you intend.

See:

Overview of Implementing Table-Validated Value Sets

Values and Value Sets.

WHERE Clauses and Bind Variables for Validation Tables

Using bind variables in WHERE/ORDER BY clauses

See Also