.. _auto_text_save_to_blob:

*SAVE TEXT A BLOB IN DATABASE*
==============================

Serializes a plain-text string as a named blob record in the d3VIEW database. Use this worker whenever downstream workers or reports need to retrieve a stored text artifact by a stable blob name.

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

Classification: **process**.

Tagged: ``blob``, ``database``, ``persist``, ``scalar``, ``storage``, ``text``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Blob Name
     - blob_name
     - scalar
     - —
     - ✓
     - Unique name (key) under which the text will be stored in the database blob store; must be a non-empty string and should be stable across runs if downstream workers reference it by name.
   * - Text to be written
     - texttobewritten
     - text
     - —
     - ✓
     - Plain-text content to persist as a blob; accepts any UTF-8 string — e.g. a JSON payload, an LS-DYNA keyword snippet, or a report summary.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - text_save_to_blob_output_1
     - text_save_to_blob_output_1
     - scalar
     - Scalar confirmation value returned after the write completes — typically the blob ID or name assigned by the database, which can be passed to downstream retrieval workers.

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

- data.io.file

.. raw:: html

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