Skip to main content

Data Sources

Create and maintain catalogs that power list fields in your forms.

Video coming soon

Data Sources

id: academy-data-sources · ~2–4 min

Record this lesson video, then set src on <LessonVideo id="academy-data-sources" />.
Data Sources administration
Maintain catalogs here, then bind them to List fields in forms.

Audience: Admin

Data Sources are CRUD catalogs on the web. Each source holds rows of structured data—products, customers, failure codes, price lists—that you connect to List fields in Form Builder. When the catalog changes, connected forms pick up the update on the next sync.

Create and manage a catalog

  1. Open Data Sources on the web (admin menu).
  2. Create a new source and define its columns.
  3. Add, edit, or delete rows directly in the grid, or bulk-load data (see Excel import below).
  4. Save. The source is now available when you configure List fields.

Each column in the catalog maps to a field type that controls validation and how values appear on mobile:

TypeUse for
TextNames, codes, short labels
NumberQuantities, prices, scores
DateEffective dates, expiry
BooleanYes/no flags, active/inactive
ImageThumbnails, product photos
FilePDFs, spec sheets attached to a row
URILinks to external pages or deep links
ProtectedSensitive values shown only to authorized roles

Choose types deliberately. A number column rejects text on import; an image column expects a valid image reference.

Import from Excel

For large catalogs, prepare a spreadsheet whose header row matches column names in the Data Source, then:

  1. Open the source → Import (or equivalent upload action).
  2. Select your .xlsx or .csv file.
  3. Review the preview, fix mapping errors, and confirm.

Imported rows replace or merge depending on the option you choose—check the dialog before confirming on a live catalog. Re-import after price or SKU updates instead of editing hundreds of rows by hand.

Sync into form Lists

List fields do not store their own options. They read from a Data Source at runtime:

  1. In Form Builder, add a List field (single or multi-select).
  2. Under field settings, pick the Data Source and the columns to display (label vs. stored value).
  3. Publish the form.

On mobile, the user sees the current catalog. Office edits to the source propagate after sync—no need to republish the form for option changes.

For step-by-step wiring in the builder, see Lists from Data Sources.

Tips

  • One source per domain (e.g. "Products", "Visit reasons")—avoid mega-catalogs with unused columns.
  • Use Protected for fields that should not appear to every mobile role.
  • Keep a stable key column (SKU, code) for imports and API use.
  • After a big import, spot-check one List field on a test device.