See Configure the Rows of the input file generator for information on generating the rowConfigs object.

Within rowConfigs is the object type source, which defines the source entities/containers/plates for a set of rows.

The Source determines the number of rows that will be configured in its corresponding rowConfig. For example, if you had a run field with a 96 well plate storage link:

  • If you wanted one row per well in the input file, the source should lookup the wells of the 96 well plates
  • If you wanted one row per plate in the input file, the source should lookup the 96 well plates directly
  • If you wanted the left half of the plates to go to a different destination than the right half of the plates, you could have two rowConfigs (and therefore two sources) - one source that looks up the left half of the 96 well plates, and another source that looks up the right half of the 96 well plates


The main benefit of leveraging a source is minimizing the number of lookupSteps in the columnsMap. Once configured, a source can be a lookupStep for each columnsMap object.

Important Notes:

  • The maximum number of lookupSteps available per object is 5.
  • isMulti should always be true for the source.
  • See “Configure lookup steps” for more information on configuring the lookup steps of the Source

Example JSON


Did this answer your question?