Overview
A Data Collector is the Mobile Flow that gathers the data set for a label. It defines which source table the label is linked to, which fields are collected, any values the user must input before printing, and any related or unrelated tables that extend the data set. The collected data set is then converted to JSON or delimited text and handed to the printing method.
Data collectors are normally created with the Label Flow Wizard, a step-by-step guide that builds the flow without any technical setup. The wizard itself is powered by an internal system flow (the Data Collector Wizard (Flow) in Labels Mobile Setup) that is generated automatically the first time it is needed.
The Label Flow Wizard
Open a Labels Mobile Document and choose Create Data Collector to start the wizard. It walks through the following steps:
- Welcome. Introduces the wizard. Choose Next to begin.
- Select the source table. Choose the table the label is linked to (for example Item, Bin Content, or Warehouse Shipment) and select the fields to include in the data set.
- Input fields. Optionally specify fields the user must fill in before the label is printed, such as the number of labels.
- Related table. Optionally expand the data set with fields from a table related to a table already in the data set. The wizard tries to create the table relations automatically; if it fails, they must be set up manually.
- Non-related table. Optionally add fields from a table not related to any table in the data set. This is typically a setup table or similar that contains a single record.
- Complete. Specify the code and description for the label flow, or accept the suggested ones, and choose Finish to create the data collector.
After each data step, a Next Action option lets you choose whether to add input fields, a related table, a non-related table, or move on to completion.
The Data Set
Each field the collector gathers is stored as a data set line with:
- The Table ID and Field ID it reads from.
- Whether the field is Included in Data Set (only included fields appear on the label).
- A Data Source Field Name, the name the field is exposed under in the JSON or delimited payload. The wizard cleans field captions into valid source names automatically (for example the Item No. field is exposed as
ItemNo). - An optional Filter so the collector only returns matching records.
Because the data source field names are what the label layout and external label software reference, keep them stable once a label is in use.
Valid Flows
Only normal Mobile Flows registered in the Label area group can be selected as a data collector. Internal activation flows, which the app generates to publish certified labels, are rejected when you try to assign them, so you cannot accidentally point a label at its own activation flow.
Maintaining a Data Collector Later
The wizard is the fastest way to build a collector, but the data set can also be adjusted afterwards through Mobile Flow Setup on the label document, where you can add or remove fields, change filters, and manage the related-table relations directly.