RAP CDS annotation based custom action triggering automatic navigation to object page S/4HANA 2023

[Shivaraj_Gowda]

Hi Experts,
When I Click on CDS annotation based custom action  "clean" defined in table header triggering automatic navigation to object page. Action implemented using  bopf .

@ui.lineItem:[{ type: #FOR_ACTION, position: 1, dataAction: 'BOPF:CLEAN', label: 'Clean'}]

I have checked CDS annotation, there is no semanicaction and semanicobject annotation defined on this action  and checked bopf class and manifest as well did not find any root cause of this automatic navigation issue.
This is custom app
SAP S/4HANA 2023

[gregorw]

Can you describe more what you exactly want to achieve?

[Shivaraj_Gowda]

Hi @gregorw,
Actually, there will be a automatic navigation to object page when we click on custom action present in list page table. We don't want this behavior. I am not sure why custom action triggering this behavior.
Ideally when we click on custom action there should not be a navigation unless we defined the navigation. Page should be stay in list page itself.

So here I am facing some issue. I am not sure any annotation or bopf class causing this issue.  

[sandeep_rs]

Hi,

Navigation is automatically triggered if the action is triggered against a single instance and the action returns a different instance (of the same entity) - see section "Navigation After Executing an Action" in page. This navigation can be disabled though using a manifest setting in Fiori elements OData V4 - see the V4 specific section in the same page that shows the usage of "navigateToInstance" manifest property.

Best Regards,

   Sandeep

[Shivaraj_Gowda]

Hi @sandeep_rs,

Thanks.
Is it possible to disable the navigation in OData V2? 
Is "navigateToInstance" in manifest configuration available for OData V2? if not what is the way to disable this navigation ?

[rohith_deraje]

Hi Shivaraj,  

Navigation is triggered only if a single instance is returned by the action and if the returned instance is not the same as the instance used when the action was triggered. The navigation is only triggered if the action was executed successfully and if the manifest has navigation defined for the context that is returned.

You can avoid sending back different unique context to avoid navigation to OP . Does it works for your use case?

Currently there is no manifest setting in Fiori elements OData V2 to stop navigation.