For the complete documentation index, see llms.txt. This page is also available as Markdown.

Mapping footer

Category: App Studio

Version: 1.0

Last updated: May 21, 2026

Author: Any2Info


Description

The Mapping Footer is a visual component used within the Dashboard Designer and Forms Designer that allows users to create mappings between dataclip values and controls or fields.

The availability and behavior of the Mapping Footer depends on the selected control or field and the links configured between controls, fields, or forms.

For form fields, the Mapping Footer is generally only available when the field is linked to another field, typically through filtering or dependency relationships.

For dashboard controls, the availability of mappings depends on:

  • The selected control type

  • Existing links between controls

  • Supported mapping modes for the control

Because mapping capabilities differ between controls and fields, detailed mapping behavior is documented in the corresponding control or field documentation.


When enabled, the Mapping Footer consists of three primary sections:

Section
Description

Mappable Properties

Displays the available properties that can be mapped for the selected control or field.

Dataclip Selection

Displays the available dataclips that can be used as the source for mappings.

Mapping Interface

Shows the visual interface used to configure mappings. The appearance depends on the mapping type supported by the selected control or field.


Mapping Types

The Mapping Footer supports multiple mapping types depending on the selected control or field.

The most commonly used mapping types are:

  • Single Header Mapping

  • Multi Header Mapping

  • Single Dataclip Mapping


Single Header Mapping

Single Header Mapping allows the user to select a single header from a dataclip.

Behavior

  • A structural preview of the selected dataclip is shown.

  • Users can select a single header by clicking one of the displayed table headers.

  • The preview contains a limited dataset to provide context for the available data structure.

Typical Use Cases

  • Mapping a single value to a field

  • Filtering controls based on one column

  • Selecting a single identifier or label field


Multi Header Mapping

Multi Header Mapping allows users to select multiple headers from a dataclip.

Behavior

  • A structural preview of the selected dataclip is displayed.

  • Multiple headers can be selected simultaneously.

  • A limited data preview is shown for context.

Table View Mode

Multi Header Mapping also supports an optional Table View Mode.

In this mode:

  • Mappings are displayed in a grid structure.

  • Extended mappings can be configured.

  • Mappings may be sortable depending on the selected control or field.

Notes

Extended mapping behavior differs per control or field and is documented individually where applicable.

Sorting behavior may affect:

  • Display order

  • Data grouping

  • Visualization logic

These behaviors are also documented in the corresponding control or field documentation.

Typical Use Cases

  • Chart series mappings

  • Multi-column visualizations

  • Complex filtering configurations

  • Grouped dashboard data


Single Dataclip Mapping

Single Dataclip Mapping allows an entire dataclip to be linked directly.

Behavior

  • The user selects a dataclip.

  • Once selected, the mapping becomes active immediately.

  • In some cases, additional extended mappings may become available.

Typical Use Cases

  • Controls requiring complete datasets

  • Data source assignment

  • Dynamic dataset binding


Broken Mappings

In some situations, previously configured mappings may become invalid and result in Broken Mappings.

A Broken Mapping indicates that an existing mapping can no longer be resolved or applied correctly by the system.

Common Causes

Broken mappings can occur due to:

  • Removal of a dataclip

  • Removal or renaming of dataclip headers

  • Removal of links between controls

  • Removal of links between forms or fields

  • Changes in control configuration

  • Unsupported mapping type changes

Behavior

When a mapping becomes broken:

  • The mapping may no longer function correctly

  • Dependent controls or fields may stop receiving data

  • Validation warnings or visual indicators may appear

  • The Mapping Footer may show incomplete or invalid mapping information

Troubleshooting

To resolve broken mappings:

  1. Verify that the referenced dataclip still exists

  2. Confirm that all mapped headers are still available

  3. Check whether links between controls or fields still exist

  4. Reconfigure the mapping if the original structure has changed

  5. Review the related control or field documentation for supported mappings

Best Practices

  • Avoid renaming or removing dataclip headers after mappings have been configured

  • Review dependent mappings before removing controls or form links

  • Test dashboards and forms after structural changes

  • Keep dataclip structures stable whenever possible


Availability Rules

The Mapping Footer is only available when supported by the selected control or field.

Forms Designer

For fields, the Mapping Footer is typically enabled when:

  • The field is linked to another field

  • Filtering relationships exist

  • Dependent field behavior is configured

Dashboard Designer

For controls, availability depends on:

  • Control type

  • Existing control links

  • Supported mapping capabilities

Not all controls support all mapping types.


Usage

Use the Mapping Footer when:

  • Linking controls to dataclips

  • Configuring dependent fields

  • Creating dynamic filtering behavior

  • Mapping chart or dashboard data

  • Connecting datasets to visual components


Tips & Best Practices

  • Always verify that the selected control or field supports mappings.

  • Use descriptive dataclip headers to simplify mapping configuration.

  • Prefer Single Header Mapping for simple field relationships.

  • Use Multi Header Mapping only when multiple data columns are required.

  • Review individual control or field documentation for advanced mapping behavior.

  • Keep mappings organized to improve dashboard maintainability.


Notes

The Mapping Footer behavior is highly dependent on:

  • Control implementation

  • Field configuration

  • Existing links and relationships

  • Supported mapping extensions

For advanced or control-specific mapping behavior, always refer to the dedicated documentation of the relevant control or field.


Changelog

Version
Date
Change

1.0

May 21, 2026

Initial documentation version added.

Last updated

Was this helpful?