How To Fix ESH_ENG_CDSVAL_ES038 - 'order.by' and 'order.byReference' are mutually exclusive (&1)

ESH_ENG_CDSVAL_ES038 - Overview

• Message type: E = Error

• Message class: ESH_ENG_CDSVAL_ES - ES-CDS/ABAP: Validation of domain @EnterpriseSearch

• Message number: 038

• Message text: 'order.by' and 'order.byReference' are mutually exclusive (&1)

What causes this issue?

The element is annotated by @EnterpriseSearch.filteringFacet.order.by
and by @EnterpriseSearch.filteringFacet.order.byReference at the same
time. These annotations are mutually exclusive.

System Response

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

How to fix this error?

Decide for one or the other annotation.
@EnterpriseSearch.filteringFacet.order.by is the easier formulation and
should provide for almost all scenarios.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_ENG_CDSVAL_ES038 - 'order.by' and 'order.byReference' are mutually exclusive (&1) ?

  The SAP error message ESH_ENG_CDSVAL_ES038 indicates that there is a conflict in the use of the order.by and order.byReference parameters in a CDS (Core Data Services) view or query. This error typically arises when both parameters are specified in a way that is not allowed, as they are mutually exclusive.
  
  Cause:
  
  The error occurs when a query attempts to use both order.by and order.byReference at the same time. These two parameters are designed to control the ordering of the results returned by the query, but they cannot be used together because they serve similar purposes in different contexts.
  order.by is used to specify the ordering of the results based on specific fields, while order.byReference is used to order results based on a reference field.
  
  
  Solution:
  To resolve this error, you need to ensure that only one of the two parameters is used in your query. Here are the steps to fix the issue:
  
  
  Review the Query: