How To Fix ESH_SEARCH122 - Template &1, node &2: More than one attribute exists for ContentURL

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 122

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

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
ContentURL attribute as described above.

How to fix this error?

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

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_SEARCH122 - Template &1, node &2: More than one attribute exists for ContentURL ?

  The SAP error message ESH_SEARCH122 indicates that there is a configuration issue in the Enterprise Search (ES) setup, specifically related to the template and node configuration. The error message states that there are multiple attributes defined for ContentURL, which is causing a conflict.
  Cause:
  The error typically arises when:
  
  Duplicate Attributes: More than one attribute is defined in the search configuration for the ContentURL field. This can happen if multiple data sources or models are configured to provide a ContentURL but are not properly distinguished.
  Incorrect Template Configuration: The template used for the search might not be correctly set up to handle the attributes, leading to ambiguity in which ContentURL to use.
  
  Solution:
  To resolve the issue, you can follow these steps:
  
  
  Check the Configuration:
  
  Go to the SAP system and navigate to the configuration settings for the Enterprise Search.
  Review the templates and nodes associated with the search configuration.
  
  
  
  Identify Duplicate Attributes:
  
  Look for the attributes defined for the ContentURL in the relevant data sources or models.
  Ensure that there is only one attribute defined for ContentURL in the context of the specific template and node.
  
  
  
  Modify the Configuration:
  
  If you find multiple attributes, you will need to either remove the duplicates or consolidate them into a single attribute that can be used for ContentURL.
  If necessary, adjust the template to ensure it correctly references the intended ContentURL.
  
  
  
  Test the Changes:
  
  After making the necessary adjustments, test the search functionality to ensure that the error no longer occurs and that the search results are as expected.
  
  
  
  Consult Documentation:
  
  If you are unsure about the configuration, refer to the SAP documentation for Enterprise Search or consult with your SAP Basis or technical team for assistance.
  
  
  
  Related Information:
  
  Enterprise Search Configuration: Understanding how to configure templates and nodes in SAP Enterprise Search is crucial. Familiarize yourself with the relevant transaction codes and configuration paths.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that could resolve the issue.
  Community Forums: Consider reaching out to SAP community forums or support channels for advice from other users who may have encountered similar issues.
  
  By following these steps, you should be able to resolve the ESH_SEARCH122 error and ensure that your Enterprise Search configuration is functioning correctly.