Last updated:
Links
Form Links connect fields or controls so that the value supplied by one control influences the data or value of another. Form linking follows the same underlying behavior as Dashboard linking, but Forms support four link types: Filter, GS1Filter, StartDateTime, and EndDateTime.
A link is created on the Base Control (the field or control being affected) and references a Target Control (the field or control supplying the value).
Target Control (Customer dropdown, supplies selected customer) │ value changes; link is evaluated ▼Base Control (Address field or GridList, loads customer-specific data)For example, a Customer dropdown can influence separate Address, City, and Postal Code fields. Each receiving field is a Base Control linked to the Customer dropdown; the fields’ data configuration or mappings determine what each field displays.
Links are evaluated when a Target Control changes its value. A separate Refresh Control action can refresh a specific control using its current configuration and linked values, without changing the links.
Configuration
Section titled “Configuration”Creating a link
Section titled “Creating a link”- Select the Base Control in the form editor.
- Open the Linking tab, visible when a control is selected.
- Add a link and select a Target Control in the dialog.
- Select a compatible Link Type and configure its parameters.
- Save the form.
- Open the Mapping Footer manually for each field that needs mapping, configure its data, save, and test in the Viewer.
The Target Control dialog excludes unusable controls. Once a target is selected, only compatible link types are offered; types whose limits have been reached are excluded.
Available link types
Section titled “Available link types”| Link type | Target Control | Purpose |
|---|---|---|
| Filter | Compatible selection or textual input field | Filters a Dataclip header using a supplied textual value and configured condition |
| GS1Filter | Barcode Filter field only | Extracts a selected GS1 code’s value from a scanned barcode and filters a Dataclip header |
| StartDateTime | DatePicker or TimeRange | Filters data from a start date/time; supports a configurable Header ID |
| EndDateTime | DatePicker or TimeRange | Filters data through an end date/time; supports a configurable Header ID |
Shared link parameters
Section titled “Shared link parameters”| Setting | Applies to | Description |
|---|---|---|
| Target Control | All | The linked field supplying the value; cannot be changed after creation |
| Link Type | All | Determines how the value is applied; cannot be changed after creation |
| Required | All four Form link types | If the Target Control supplies no usable value, the Base Control resets to its initialized state |
| Header | Filter, GS1Filter | Selects the Dataclip header being filtered |
| Condition | Filter | Configurable textual comparison operator |
| GS1 Code | GS1Filter | Selects the GS1 component to extract; this selection determines the applied condition |
| Header ID | StartDateTime, EndDateTime | Selects the specific Dataclip date header to filter |
| Ignore time | StartDateTime, EndDateTime | Applies local start/end-of-day boundaries instead of the selected time |
Required and reset behavior: When any required link has no usable value, the Base Control resets to its initialized state. For example, a grid shows no data, while a label or filter displays its value configured outside mapping. For textual Filter values, null and "" are unusable; date values are unusable when null. A valid value that happens to return no records is not inherently unusable. A missing selected GS1 code likewise yields an empty/unusable value.
Filter
Section titled “Filter”Filter links apply a textual value to a selected Dataclip header. When a selection field is used, its mapping selects a single header and its options represent the distinct values under that header. Textual input fields such as Filter and Barcode Filter fields can supply user-entered or configured variable values.
| Condition | Behavior |
|---|---|
| Equals | Matches the exact value |
| Contains | Matches text containing the value |
| EndsWith | Matches text ending with the value |
| StartsWith | Matches text beginning with the value |
Version 5.2.0.7 change: The filter Header and Condition are configured directly on the link. Before this version, the header was configured through mapping and the condition on the linked control.
Multiple filters are evaluated by the system based on both the headers and the comparison conditions. For example:
(Customer = "Customer A" OR Customer = "Customer B")AND Status = "Open"Different headers commonly combine with AND, while multiple Equals conditions on one header can combine with OR. Do not assume a universal combination rule for all conditions; the system evaluates the combination.
GS1Filter
Section titled “GS1Filter”GS1Filter is only available for Barcode Filter fields. It selects a specific GS1 code, extracts only the value associated with that code from a scanned barcode, and applies the condition associated with the selected code to the selected Dataclip header.
| Setting | Description |
|---|---|
| GS1 Code | Identifies the barcode component to extract |
| Header | Dataclip header to filter |
| Condition | Determined by the selected GS1 code |
| Required | Resets the Base Control when the selected code produces no usable value |
For example, a scanned GS1 barcode might contain:
| GS1 code | Meaning | Illustrative extracted value |
|---|---|---|
01 |
GTIN | 08712345678906 |
10 |
Batch/lot | BATCH123 |
17 |
Expiration date | 271231 |
A GS1Filter configured for code 10 supplies BATCH123, not the entire barcode. Multiple GS1Filter links are allowed, including multiple links to the same Barcode Filter field using different GS1 codes. If the scanned barcode lacks the selected code, the value is empty/unusable; when Required is enabled, the Base Control resets.
StartDateTime and EndDateTime
Section titled “StartDateTime and EndDateTime”StartDateTime and EndDateTime use a DatePicker or TimeRange Target Control to filter a date/time period. Only one StartDateTime and one EndDateTime link may exist per Base Control.
Unlike dashboard date links, Form date links let the user select a specific Dataclip Header ID. Dashboard date links automatically use a Dataclip’s unique designated DateTime header.
The Ignore time parameter sets the start boundary to local 00:00:00 and the end boundary to local 23:59:59..., including the full selected days. The effect also depends on whether the DatePicker is configured for date-only or date-and-time input.
| Link type | Ignore time enabled | Example local boundary |
|---|---|---|
| StartDateTime | Start of selected day | October 20, 2026 at 00:00:00 |
| EndDateTime | End of selected day | October 20, 2026 at 23:59:59... |
The client’s timezone is used to establish local boundaries, and transmitted values are converted to UTC+00:00. For example, October 20, 2026 at 00:00 in the Netherlands (CEST) is October 19 at 22:00 UTC.
Example: Show customer information in a form
Section titled “Example: Show customer information in a form”- Add a Customer dropdown as the Target Control.
- Select an Address field as the Base Control and add a Filter link to the Customer dropdown.
- Configure the filter header and condition.
- Repeat for City and Postal Code fields as needed.
- Manually configure each field’s relevant mapping so it retrieves the intended value.
- Save the form and test in the Viewer by changing the selected customer.
Example: Filter a GridList using a scanned GS1 barcode
Section titled “Example: Filter a GridList using a scanned GS1 barcode”- Configure a GridList with its Dataclip selected in the control properties.
- Add a Barcode Filter field to supply the scanned barcode.
- Select the GridList as the Base Control and add a GS1Filter link to the Barcode Filter field.
- Select the GS1 code and the Dataclip header to filter; set Required if the GridList must reset when the code is absent.
- Add further GS1Filter links for other barcode components if needed.
- Save the form and test in the Viewer.
A GridList can obtain its data directly from the Dataclip selected in its properties, without additional mapping. Most other linked Form fields generally need mapping; the exact requirement depends on the field’s data configuration.
Initial loading and dependencies
Section titled “Initial loading and dependencies”Linked controls begin loading when the form opens. When a required value depends on another linked field, initial loading proceeds in layers, as upstream values become available.
Region selection → Customer selection (filtered by region) → Customer details (filtered by customer)If any required link lacks a usable value, its Base Control resets to its initialized state. Design clear one-way dependency chains and prevent circular dependencies during form design; automatic cycle detection is not assumed.
Editing and deleting links
Section titled “Editing and deleting links”The Linking tab lists the links on the selected Base Control and allows individual deletion. A link’s Target Control and Link Type cannot be changed after creation; delete and recreate it to change either. Applicable parameters such as Header, Required, and Condition can be edited. Deleting a linked control automatically cleans up links that reference it. Removed links are no longer used during evaluation.
Deleting links does not delete mappings. A mapping that depended on a removed link may appear broken when opened in the Mapping Footer. Save the form after changes.
Mapping
Section titled “Mapping”Linking is normally followed by mapping. Links define relationships and filter behavior, while mapping connects fields to Dataclip data where needed. The Mapping Footer must be opened manually for each relevant field; linking does not configure it automatically. Some fields, including GridLists, can use the Dataclip selected in their properties instead. Deleting a link does not delete mappings and may leave broken mapping references. See Mapping Footer.
- Select the receiving field as the Base Control and the value-providing field as the Target Control.
- Create links first, then manually open mapping for each field that requires it. Links do not create mappings automatically.
- Most Form links involve mapping, but some controls such as GridLists can read from the Dataclip selected in their properties.
- Set Required when a field should return to its initialized state if any mandatory linked value is absent.
- Use multiple GS1Filter links to extract different values from a single Barcode Filter field.
- For date links, select the correct Header ID and verify Ignore time behavior.
- Avoid circular link dependencies and review mapping references after deleting links.
- Save the form and test in the Viewer.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Possible cause | What to check |
|---|---|---|
| A field resets to its initialized value or a GridList shows no data | A Required link has no usable value | Check all Required links; one missing value is enough to reset |
| GS1Filter produces no value | Scanned barcode lacks the selected GS1 code | Verify the code selected in the link and the barcode contents |
| Filtered values are unexpected | Wrong header or condition | Review Header and Condition in the link, especially on versions 5.2.0.7 and later |
| Date filtering uses the wrong column | Incorrect Header ID | Select the intended Dataclip date header in the Form date link |
| Date boundary is shifted | Ignore time or client timezone conversion | Check local day boundaries and UTC conversion |
| Target Control or Link Type is unavailable | Incompatible control or link limit reached | Check control compatibility and existing links |
| Mapping appears broken | A referenced link was removed | Open Mapping Footer and repair the affected mapping |
| Linked field does not respond | Wrong target value, mapping, configuration, or unsaved changes | Review the link, save, and test in Viewer |
| Initial data is missing | Required value depends on another field that has not supplied a value | Check the dependency chain and Required settings |