Skip to content
Merulan

Import and target records

Import and target Records by checking Pipeline lineage, reading current values, and verifying membership in a suitable List.

Use this guide when an operator needs to import Records and group them in Records & Lists. Finish with a checked List and links to the import's Run.

Before you start

An import needs a declared Entity kind, a mapped Source, and access to the target Workspace. Data Pipelines owns that setup, its Runs, and promotion. Decide whether you need external rows imported or one Record created directly. For a direct create, entities.create owns the call contract. Creating a Record directly does not create Pipeline lineage.

Verify the import

An import must produce readable Records before those Records become a useful work target.

  1. Follow Run a data pipeline to start the mapped Pipeline. Keep the Run's readback so you can inspect its result and lineage.
  2. In Records, select the target Entity kind. Read the intended Records and check their values against the imported source data.
  3. Follow the Pipeline's lineage when a value or origin is unclear. Resolve the import outcome before including the Record in work that depends on that value.

Choose the target

Imported Records need a List whose target admits every intended member. Choose a single kind when the work is specific to that kind. Choose an Interface target when several kinds fill the same role.

  1. Use Create a list to create a Static List with the chosen target. Open the returned List to confirm its name and target.
  2. Add the intended Record references using lists.addMembers or the Console membership control. Check the result for refused members.
  3. Read the List's members. Compare their kind and id with the intended selection before launching work against the List.

Checkpoints

An import and a membership change have separate readbacks. The Pipeline Run explains which work produced the Records. The Record read confirms the current values. The List member read confirms which Records the work target contains. A successful List creation proves only that the collection exists. A filtered table or a member count does not establish that every intended Record is present.

Success

An import becomes a verified work target when the expected Record references appear in a suitable List and their values are readable. Keep the originating Pipeline and Run available for lineage checks. The List names the selected work. It does not replace the import evidence. If the next Action freezes its targets at launch, verify membership before starting that Run.

When it fails

INVALID_LIST_KIND_OPERATION

A membership edit targeted a List kind that does not accept it. Manual membership belongs to a Static List. Use a Static List for the selected imported Records, or revise the Dynamic List's query when the desired target should recompute.

VALIDATION_ERROR

A Record write or membership input does not satisfy its declared contract. Check the error's field or target against the current Entity kind and List target. Repair the input before sending it again. Changing a View cannot repair either contract.

Recovery

An import problem should be repaired at its owner. A wrong value or missing origin returns to Data Pipelines for mapping, Run, or promotion review. A wrong List target requires a List with the correct target. A missing member requires a valid Record reference and admission by that target. Read the repaired result before launching downstream work. API supplies HTTP setup when a script performs the linked Record or List calls.

Next steps