Conditional Databind is the ability to dynamically bind data from an external database source such as a table, view or stored procedure to a field upon a change of value from another field.
describe each field attribute of the Conditional Databind screen and how to incorporate to your form template. A typical Conditional Databind screen is shown below.
To better understand the functionality of each of these properties, we will use an example form containing of just 2 field elements named FieldOne and FieldTwo. In the scenario, when there is a change in value in FieldOne we want to populate a list of data to FieldTwo based on the value from FieldOne.
In our example because we are using FieldOne as the reference field, we need to populate the Conditional Databind properties for FieldOne element.
Conditional Binding Tab
Property Name |
Description |
ServerEvent |
Property list all the possible events available that can be used as a trigger to perform the databind functionality. Currently there is only one event which is the OnChange event. This event indicates if there is change in the value of the current field triggers the databind functionality for the field specified (FieldTwo) |
ApplyToField |
Property list all Form Fields created and available from the form template. This is also the field that will have data bound to if it satisfies the specified condition. In our example, we select FieldTwo from the list. Note that the field element needs to have been created prior assigning Conditional Databind attributes. |
FieldCompareOperator |
Indicates which comparison operator to use when comparing value of the currently affected field (FieldOne). Currently there are 8 possible comparison operators available. • Any Value: Always return TRUE for any value provided in the Conditional Field • Equals: Returns TRUE if the provided Conditional Field value match exactly to the value specified in the evaluation expression. This matching operator is case sensitive. • Not Equals: Returns TRUE if the provided Conditional Field value do not match exactly to the value specified in the evaluation expression. This matching operator is case sensitive • Less Than: Returns TRUE if the provided Conditional Field value is less than the value specified in the evaluation expression. This comparison operator applies to Date and Numeric value types • Less Than or Equals: Returns TRUE if the provided Conditional Field value is less than or equals to the value specified in the evaluation expression. This comparison operator applies to Date and Numeric value types • Greater Than: Returns TRUE if the provided Conditional Field value is greater than the value specified in the evaluation expression. This comparison operator applies to Date and Numeric value types • Greater Than or Equals: Returns TRUE if the provided Conditional Field value is greater than or equals to the value specified in the evaluation expression. This comparison operator applies to Date and Numeric value types • Contains: Returns TRUE if the provided Conditional Field value contains the value specified in the evaluation expression. This comparison operator is NOT case sensitive • Empty or Equals: Returns TRUE if the provided Conditional Field value is empty or blank or the provided Conditional Field value matches exactly the value specified in the evaluation expression. This comparison operator is case sensitive • Empty or Not Equals: Returns TRUE if the provided Conditional Field value is empty or blank or the provided Conditional Field value do not match exactly the value specified in the evaluation expression. This comparison operator is case sensitive |
FieldCompareValue |
This is the value to be compared against the current field's value (FieldOne). The FieldCompareOperator and FieldCompareValue forms a criteria in which the current field's value must meet in order for the databind to execute. In our example, if the FieldCompareOperator is selected as "Equal" and FieldCompareValue is "Joe Bloe", for databinding to execute on FieldTwo the current value of FieldOne must be "Joe Bloe". If it is any other value dynamic databind on FieldTwo will not execute. |
BindToSourceType |
Indicates the type of external data source to be used for extracting data when the current field value satisfies the specified condition. Similar to the Databinding tab, there are 4 possible options to select from.
• Table (DNN) : This option indicates that the source table is a DNN type table. DNN typed table is a table that uses the ObjectQualifier attribute in DNN • Table (Non-DNN): This option indicates that the source table is a normal table without using the DNN object qualifier attribute. • Stored Procedure (DNN): This option indicates that source data comes from a stored procedure that uses the ObjectQualier attribute in DNN • Stored Procedure (Non-DNN): This option indicate the source data comes from a stored procedure that does not use the ObjectQualifier attribute in DNN |
BindToSourceName |
Property to specify the name of the data table or stored procedure to use. If stored procedure is used, additional parameters can be specified as listed at top of the screen. In addition, field tokens can be used to specify the value of a particular field within the form. A standard token format can be of two forms: {FORM:fieldID} or {FORM:fieldName} where "fieldID" id replaced by the 34 characters ID of the field normally generated by Enterprise Forms and "fieldName" is the name of the field element. |
BindToValueColumn |
Property to indicate the column name of the record set return from the data source to bind the Value component of the field. |
BindToTextColumn |
Property to indicate the column name of the record set return from the data source to bind the Text component of the field. |
BindingPostback |
Property to indicate that a server event should be triggered immediately when there is a change in the value of the current field |