Question Re: Fiori Elements Intent Based Navigation Custom Entity in Technology Q&A

Fiori Elements Intent Based Navigation Custom Entity

dommeyer — Fri, 04 Nov 2022 07:51:13 GMT

Hello Experts,

for our fiori elements app we included a custom entity as association in our root view entity. In our custom entity we want to do an intent based navigation from the material number to the Fiori App F1602 (Material Master). Therefore we created a target mapping with reference to the original application and used our custom semantic object. We copied exactly the same parameter values but our problem is that the value of the material number which is clicked is not included in the URL. The mapping in the launchpad designer looks like this (mapping smatn to Product):

The name smatn is the same according to the CDS Entity:

The problem is that when you now click on the material number you get to the overview page of the app and not into the object page because the value of the field smatn is not included into the URL.

How can we solve this issue?

Best regards,
Dominik

Re: Fiori Elements Intent Based Navigation Custom Entity

sandeep_rs — Fri, 04 Nov 2022 08:55:52 GMT

Hi dommeyer

Few questions:

Is the field where it is being clicked part of an extension (custom section) or is consumed in a standard fe app (If so, Fiori elements OData V2 or a Fiori elements OData V4 application?).
Can you also throw some more light on what annotation is configured against this field to show it up as a link (semantic link \ DataFieldWithIntentBasedNavigation \ ....)?
Is the field part of a form/header or is embedded in a table column..? Should not really matter but just so that we get the complete picture here.

Thanks and Best Regards,

Sandeep

Re: Fiori Elements Intent Based Navigation Custom Entity

dommeyer — Fri, 04 Nov 2022 12:12:59 GMT

Hi sandeep.rs,

thanks for your answer.

The field is consumed from a Custom Fiori Elements App. The target field in the target application is part of a standard Fiori Elements App (F1602 - Field: Product). The section in the custom app is configured via association in the root view:
We created our custom semantic object in table /UI2/V_SEMOBJC. Then we just added the annotiations in the CDS Custom Entity as follows
The field is part of a table column as you can see in the picture of the second point.

Thanks!

Br,
Dominik