Fiori Element - Intent-Based Navigation adds unwanted query parameters and navigates to input screen instead of target display screen

[pallavjadav]

Intent-Based Navigation appends unwanted parameters and navigates to input screen instead of target display screen

Description

Hello Team,

We are facing an issue with Intent-Based Navigation (IBN) for a custom semantic object/action used to open a standard display screen.

We are using an annotation structured as follows (generic form):

{
  "$Type": "UI.DataFieldWithIntentBasedNavigation",
  "SemanticObject": "SomeSemanticObject",
  "Action": "displayDocuments",
  "Value": "SomePrimaryProperty",
  "RequiresContext": true,
  "Inline": true,
  "Label": "{i18n>SomeLabel}",
  "Mapping": [
    { "LocalProperty": "PropertyA", "SemanticObjectProperty": "FieldA" },
    { "LocalProperty": "PropertyB", "SemanticObjectProperty": "FieldB" },
    { "LocalProperty": "PropertyC", "SemanticObjectProperty": "FieldC" },
    { "LocalProperty": "PropertyD", "SemanticObjectProperty": "FieldD" }
  ]
}

This configuration works correctly when only one mapping is provided. However, when multiple mappings are used, the IBN behavior changes unexpectedly.

---

Issue Observed

1. When the IBN link is triggered, the navigation does not directly open the target display screen. Instead, it opens the initial input screen, requiring manual entry.
2. The generated URL becomes excessively long because it includes many unrelated Object Page fields, not just the mapped ones.
3. This issue occurs only when multiple entries exist in the Mapping array.

Example of the actual URL generated (redacted and simplified):

https://<launchpad-url>#SomeSemanticObject-displayDocuments?FieldA=...&FieldB=...&FieldC=...&FieldD=...&[hundreds of automatically-added parameters]

---

Expected Behavior

The URL should include only the explicitly mapped properties, such as:

https://<launchpad-url>#SomeSemanticObject-displayDocuments?FieldA=...&FieldB=...&FieldC=...&FieldD=...

No additional Object Page fields should be appended.

---

Impact

• Navigation lands on the wrong screen (input instead of display).
• Extremely long URLs due to appended parameters.
• Behavior suggests a framework-level issue, not annotation misuse.

---

Request for Support

We kindly request confirmation on the following:

• Is this a known issue or limitation in the Fiori IBN framework when multiple mappings are used?
• Is there a workaround to ensure only mapped parameters are included in the URL?
• Can the framework behavior be corrected so that navigation proceeds directly to the target display screen?

Any guidance or assistance in resolving this issue would be greatly appreciated.

[gregorwolf]

Hi @pallavjadav ,

please check out the additions that I've contributed to this example. When you click on the link in the "Association (1..1)" column you see now a navigation to Deliveries:

The resulting link is:

http://localhost:4004/$launchpad#FeatureShowcaseDeliveries-manage?order.ID=b6451584-d37c-4bb4-b35a-d2327810a143&sap-xapp-state=TASMKQM4MR2HLYFX9NBO7U9U6VASC1PMFPDQ3AQ5Y&/?sap-iapp-state=TASKR03WIPO3GILUIAPF1VM3APC42996ICAEK53JY

and as you can see it contains only order.ID as a praprameter. The result is filtering the Deliveries by the order ID:

I've achived this with the mapping in:

https://github.com/SAP-samples/fiori-elements-feature-showcase/blob/main/app/listreport-objectpage/field-control.cds#L31

and the crossNavigation definition in:

https://github.com/SAP-samples/fiori-elements-feature-showcase/blob/main/app/deliveries/webapp/manifest.json#L27

hope that helps.

Best regards,
Gregor