How To Fix /UI2/FDM_2_CDM3035 - InnerAppRoute defined twice (once using "&&/" and once as parameter)

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM_2_CDM3 -

• Message number: 035

• Message text: InnerAppRoute defined twice (once using "&&/" and once as parameter)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /UI2/FDM_2_CDM3035 - InnerAppRoute defined twice (once using "&&/" and once as parameter) ?

  The SAP error message /UI2/FDM_2_CDM3035 InnerAppRoute defined twice (once using "&&/" and once as parameter) typically occurs in the context of SAP Fiori applications when there is a conflict in the routing configuration of the application. This error indicates that the same inner application route is defined in two different ways, which leads to ambiguity in the routing logic.
  Cause:
  
  Duplicate Route Definitions: The error arises when an inner application route is defined both as a parameter in the routing configuration and also using the "&&/" syntax. This can happen if the developer inadvertently specifies the same route in multiple places or formats.
  Misconfiguration: The routing configuration in the manifest file or the component.js file may have conflicting entries that define the same route differently.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Routing Configuration:
  
  Open the manifest.json file of your Fiori application.
  Look for the sap.ui5 section and locate the routing configuration.
  Identify any inner application routes that are defined using both the "&&/" syntax and as parameters.
  
  
  
  Remove Duplicate Definitions:
  
  Ensure that each inner application route is defined only once. If you find a route defined in both ways, choose one method of definition and remove the other.
  For example, if you have a route defined as:
  "routes": [
    {
      "pattern": "myRoute&&/",
      "name": "myRoute",
      "target": "myTarget"
    },
    {
      "pattern": "myRoute",
      "name": "myRoute",
      "target": "myTarget"
    }
  ]
  You should keep only one of these definitions.
  
  
  
  
  Test the Application:
  
  After making the necessary changes, save the manifest.json file and refresh your application.
  Test the routing to ensure that the error is resolved and that the application behaves as expected.
  
  
  
  Related Information:
  
  SAP Fiori Documentation: Refer to the official SAP Fiori documentation for best practices on routing and navigation in Fiori applications.
  Debugging Tools: Use the browser's developer tools to inspect the console for any additional errors or warnings that may provide further context on routing issues.
  SAP Community: If the issue persists, consider reaching out to the SAP Community forums for additional support and insights from other developers who may have encountered similar issues.
  
  By following these steps, you should be able to resolve the /UI2/FDM_2_CDM3035 error and ensure that your Fiori application's routing is correctly configured.