Repeated Data Mapping II

  • If you repeat any component which has fields to map, in most cases you must map them to the corresponding fields of the Item subtree.

  • Keeping them unmapped produces unwanted results.

  • If there is no field to map your repeated field to (e.g., an event), access the Advanced Data Mapping dialog and rename it.

  • The new field's name must contain the item and the new name, e.g., MonthsItem.MonthNewName.

  • This will set each repeated field to be independent.

Repeat the Text Input 1 component by the Months array.Default repeated child's mapping produces unwanted result:The repeated child's variables need to be mapped to the Item's variables:

  • The mapping of repeated data can only be done inside the repeated component's (in this case Text Input 1) Data Mapping tab. If you access the mapping tab of any other components (e.g., its parent component), you will not see the item subtree and its variables.

  • If you decide to manually type the item subtree's and the new variable's name, remember that the field values are case-sensitive, meaning MonthsItem is different than Monthsitem.

  • If you do not map the repeated child's fields, all of them will be mapped to the same field (in this screenshot, the Value field). Such a repeated component will have dependent data mapping (changing the third repeated child's occurrence changes the values of all the other occurrences).

  • The middle part of the screenshot shows the Value variable, which is not mapped to anything.

  • If you map the variable to one of the MonthsItem variables, you will have a correct result.