# Mapping data to fields
### Footer function
Mapping data to fields is available in the supporting footer below the canvas. If a field has the ability to bind data, the mapping option becomes visible in the footer bar.
### General
In general the best way to approach data mapping is to refer to the dataclip as a table structure consisting of rows and columns.
To determine a single value from this structure a column (**header**) and row (**occurence**) is needed.
When multiple values from multiple rows are needed system will need to know which columns and rows are needed.
The software supports 1 type of mappings:
**Single header mapping:** This mapping requires a single header or column form a dataclip to be mapped to a property.
*Examples:*
* Select a value from a list and set values to linked labels or textboxes. These labels and/or texboxes shows a specific value under a header based on filtered or chosen line from a dataclip.
In general the best way to approach data mapping is to refer to the data as a table structure consisting of rows and columns.
To determine a single value form this structure a column and row is needed.
When multiple values from multiple rows are needed system will need to know which columns and rows are needed.
A general note here, by default all rows in a data set are targetted.
Filtering to these rows are commonly applied by configuring these as links or filters.
