.. _auto_database_simulation_response_importer:

*CREATES OR REPLACES A RECORD INTO THE DATABASE BASED ON SIMULATION RESPONSES*
==============================================================================

Ingests simulation response data into a target database by creating a new record or replacing an existing one. Use this worker to persist CAE simulation outputs and their parent–child relationships into the platform's data-record store as part of a post-processing or DOE workflow.

When to use
-----------

Tagged: ``create``, ``data_record``, ``database``, ``import``, ``post-processing``, ``replace``, ``response``, ``simulation``.

Inputs
------

.. list-table::
   :header-rows: 1
   :widths: 20 20 20 20 20 20

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Choose Database
     - database_id
     - remote_lookup
     - —
     - ✓
     - Target database (data-record store) into which the simulation response will be written; select from the user's available databases via the platform lookup.
   * - Choose Simulation
     - simulation_id
     - remote_lookup
     - —
     - ✓
     - The simulation whose response data will be imported into the database; select from the user's available simulations.
   * - Choose Parent Simulation
     - parent_simulation_id
     - remote_lookup
     - —
     - ✓
     - The parent simulation linked to this response record, used to preserve hierarchical run relationships (e.g., DOE parent); select from the user's available simulations.
   * - Simulation Input Id
     - simulation_input_id
     - scalar
     - simulation_id
     - 
     - Column/field name in the database that stores the simulation identifier; defaults to 'simulation_id' — change only if the target database schema uses a different key name.
   * - Parent Simulation Input Id
     - parent_simulation_input_id
     - scalar
     - parent_simulation_id
     - 
     - Column/field name in the database that stores the parent simulation identifier; defaults to 'parent_simulation_id' — change only if the target database schema uses a different key name.
   * - Create Or Replace
     - create_replace
     - select
     - create
     - 
     - Write mode: 'create' inserts a new record (default), 'replace' overwrites an existing record with the same simulation identifier; leave as 'create' for first-time ingestion.

Outputs
-------

.. list-table::
   :header-rows: 1
   :widths: 20 20 20 20

   * - Label
     - ID
     - Type
     - Description
   * - Database Id
     - database_id
     - scalar
     - Identifier of the database record store that was written to, passed downstream for chaining further database operations.
   * - Simulation Id
     - simulation_id
     - scalar
     - Identifier of the simulation whose response was successfully imported, available for downstream referencing or validation steps.

Disciplines
-----------

- cae.postprocessing.response
- data.dataset.ingest
- platform.workflow

.. raw:: html

   <hr style="margin-top:2em">
   <p style="font-size:11px;color:#888">
   Auto-generated from <code>platform</code> schema. Worker id: <code>database_simulation_response_importer</code>. Schema hash: <code>e97b939d57ce</code>. Hand-curated docs in <code>workerexamples/</code> override this page when present.
   </p>