IMPORT RESPONSES

Imports a JSON responses file and bulk-loads its response records into either a physical-test or simulation result-set parent entity. Use this worker to ingest pre-exported response payloads into the d3VIEW platform and track how many records were successfully added versus failed.

When to use

Tagged: bulk_load, import, ingest, json, physicaltest, responses, simulation.

Inputs

Label ID Type Default Required Description
Parent Type parent_type select physicaltest   Type of parent entity to attach the responses to; choose ‘physicaltest’ (default) for physical-test records or ‘srs’ for simulation result-sets.
Name parent_name scalar   Name of the parent physical-test or simulation record to create or identify; repeatable scalar — leave null to let the platform auto-assign a name.
Responses File responses_file file Required JSON file containing a top-level ‘responses’ array; each element must be a valid response object conforming to the d3VIEW Response schema.

Outputs

Label ID Type Description
Simulation Id simulation_id simulation Platform ID of the simulation result-set parent record created or updated; populated only when parent_type is ‘srs’, otherwise empty.
Physicaltest Id physicaltest_id physicaltest Platform ID of the physical-test parent record created or updated; populated only when parent_type is ‘physicaltest’, otherwise empty.
Num Responses Added num_responses_added number Integer count of response records from the input file that were successfully saved to the database.
Num Responses Missed num_responses_missed number Integer count of response records from the input file that failed to save, indicating parse errors or constraint violations.

Disciplines

  • data.dataset.ingest

Auto-generated from platform schema. Worker id: responses_importer. Schema hash: 9500d32a3e46. Hand-curated docs in workerexamples/ override this page when present.