Binding to data not defined by the default data connection

You can override the default data binding by enabling settings to allow binding to data that is not defined in the default data connection. The Allow Binding To Data Not Defined By The Default Data Connection setting saves data in fields when they are bound by name or by explicit binding reference.

Saving or exporting undefined data in a separate namespace

To save or export the data in a separate namespace, you can select the namespace setting. The namespace lets you bind fields or subforms to data that is outside the default data connection. When set, the data description is automatically updated when nodes are added. Optionally, you can specify a prefix for the namespace. If you do not specify a namespace, the namespace information in the added nodes is inherited from the parents of the added nodes.

You can also specify that the added nodes are bound relative to a filtered node in the Data View palette.

Identifying nodes not bound by the default data connection

In the Data View palette, nodes that are not bound by the default data connection are dimmed. Keep in mind the following points when working with nodes that are not bound by the default data connection:

  • You cannot drag the nodes to the form layout to create new nodes, and you cannot bind them to existing nodes.

  • The node is not displayed in the Object palette> Binding tab.

To allow binding to data that is not defined by the default data connection

  1. Select File > Form Properties.

  2. Click the Data Binding tab and select Allow Binding To Data Not Defined By The Default Data Connection.

  3. (optional) Do any of the following actions:

    • To add a namespace, select XML Namespace and type the namespace.

    • To add a prefix to the namespace, select XML Namespace Prefix and type the prefix.

    • To add data nodes in the filtered hierarchy, select Add Nodes Inside The Filtered Data Hierarchy.

// Ethnio survey code removed