CREATES OR REPLACES A RECORD INTO THE DATABASE BASED ON PHYSICALTEST RESPONSES¶
Ingests physical-test response values into a target database by creating or replacing records, mapping response names to database column names. Use this worker when you need to promote scalar KPI responses from one or more physical tests into a structured database table, with optional column-name remapping and single-row or multi-row insertion modes.
When to use¶
Tagged: create, database, files, import, ingest, mapping, physicaltest, replace.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Choose Database | database_id | remote_lookup | — | ✓ | Target database (data-records store) into which the physical-test responses will be written; select from the available databases via the remote lookup. |
| Choose Physicaltest | physicaltest_id | remote_lookup | — | ✓ | Primary physical test whose response values will be read and inserted into the database; select from the user’s available physical tests. |
| Choose Parent Physicaltest | parent_physicaltest_id | remote_lookup | — | ✓ | Parent physical test used to scope or group the insertion; required when the database schema links records to a parent test hierarchy. |
| Physicaltest Input Id | physicaltest_input_id | scalar | physicaltest_id | Name of the database column that will store the physical-test identifier; defaults to ‘physicaltest_id’ — change only if your schema uses a different column name. | |
| Parent Physicaltest Input Id In Database | parent_physicaltest_input_id | scalar | parent_physicaltest_id | Name of the database column that will store the parent physical-test identifier; defaults to ‘parent_physicaltest_id’ — change only if your schema uses a different column name. | |
| Create Or Replace | create_replace | select | create | Controls write behaviour: ‘create’ inserts a new record, ‘replace’ overwrites an existing record that matches the key; defaults to ‘create’. | |
| Response Names To Database Columns Map Information | map_data | dataset | — | Optional dataset providing explicit column-name-to-response-name mappings in the format ‘DB_column => TestId.response_name’; leave empty when database column names already match the physical-test response names exactly. | |
| Type Of Insertion | type_of_insertion | select | create | Determines row granularity: ‘single’ collapses data from all selected tests into one database row; ‘multiple’ writes one row per test — choose based on how your database schema is structured. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Database Id | database_id | scalar | Identifier of the target database into which the records were written, passed downstream for chaining further database operations. |
| Physicaltest Id | physicaltest_id | scalar | Identifier of the physical test whose responses were imported, passed downstream for traceability or subsequent processing steps. |
Disciplines¶
- data.dataset.ingest
- data.io.sql
Auto-generated from platform schema. Worker id: database_physicaltest_response_importer. Schema hash: 15ea0aedb141. Hand-curated docs in workerexamples/ override this page when present.