How To Fix ESH_SEARCH123 - Template &1, node &2: More than one attribute exists for MIME type

ESH_SEARCH123 - Overview

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 123

• Message text: Template &1, node &2: More than one attribute exists for MIME type

What causes this issue?

If you want to use binary content in DPS it is only possible to use URLs
to reference this content. In this case there are further restrictions
as there should be only one attribute referencing an URL per node.
Moreover a pair of attributes is needed: one referencing the URL and
another giving the correct mime type of the content. The attribute for
the URL needs to have the "ContentURLIndicator" set to true and must be
of datatype string. The latter is also true for the mime type attribute
which is designated to be a mime type by using the semantics code
"MimeType".

System Response

Only one attribute per node is allowed to be marked for being the
MimeType attribute as described above.

How to fix this error?

Change the model so that only one attribute is marked for being the
MimeType.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_SEARCH123 - Template &1, node &2: More than one attribute exists for MIME type ?

  The SAP error message ESH_SEARCH123 typically indicates that there is a conflict in the configuration of the Enterprise Search (ESH) system regarding the attributes associated with a specific MIME type. This error occurs when more than one attribute is defined for a given MIME type, which can lead to ambiguity in how the system processes search queries.
  
  Cause:
  
  
  Multiple Attributes for a MIME Type: The primary cause of this error is that the system has been configured with more than one attribute that corresponds to the same MIME type. This can happen during the configuration of the search model or when defining the attributes in the data source.
  
  
  Incorrect Configuration: There may be an incorrect or incomplete configuration in the search model or the data source that leads to this conflict.
  
  
  Data Source Issues: If the data source is not properly set up or if there are changes in the data structure that have