Loading

Data 360: Handling Retriever Errors in Einstein Studio

Data pubblicazione: Jan 23, 2026
Descrizione

Users may encounter the following error when attempting to save a Retriever configuration:
“Retriever failed to save. To avoid losing work, wait and try again.”

While the error may be generic, the network tab in your browser's developer tools may have additional error information.

 

  1. Before saving, open your browser's network tab
  2. Click Save
  3. Look through the POST method responses for something like below
"error": [
     {
         "httpStatusCode": "BAD_REQUEST",
         "errorCode": "INVALID_INPUT",
         "message": "The output field related DMO ssot__XXXXXXXX_dlm of category STANDARD must not be unstructured DMO"
     }
            ]
Risoluzione

The output field relationship from [Primary DMO] to [Related DMO] should be one to one, or many to one.

In Einstein Studio, while creating a Retriever, Step 3 (Configure Retriever Results) allows users to include fields not only from the Primary DMO (on which the Search Index is configured) but also from related DMOs.

This happens because the system cannot determine which specific related record to include in the Retriever output when the relationship type is One-to-Many.

For example:

  • A single Individual record can have multiple ContactPointEmail records (for personal, work, or alternate emails).
  • Since there can be more than one related record, the Retriever cannot decide which email to display, causing the save operation to fail.

To avoid or fix this error:

  • Select fields only from DMOs that have a One-to-One or Many-to-One relationship with the Primary DMO.
  • Do not select fields from DMOs that have a One-to-Many relationship, because multiple related records can exist, and the Retriever cannot choose which one to display.

Example:

  • ssot__Individual__dlm → ssot__ContactPointEmail__dlm is a One-to-Many relationship (one individual can have many emails).
  • In this case, fields from ssot__ContactPointEmail__dlm should not be added to the Retriever output.

 

The output field related DMO ssot__XXXXXXXX_dlm of category STANDARD must not be unstructured DMO

This error occurs when an unstructured DMO field or a file attachment associated to an Unstructured DMO is used in a retriever based on Structured DMO Search Index.

To use an Unstructured DMO field, the source DMO search index for the retriever must also be unstructured.

Numero articolo Knowledge

005228387

 
Caricamento
Salesforce Help | Article