Skip to Content

Fiori Elements BOPF Actions and CDS Where Clauses

I need help working out why my Fiori Elements app is behaving the way it does.

Let me first explain what I'm trying to do.

I have a Fiori Elements List Report App (transactional app with a BOPF) ... I have disabled the standard Delete action on the BOPF as I don't want the user to be able to delete entries from the database, instead I want the user to flag the entries as deleted and then filter the out of the list. In this way the entry remains in the database but is flagged as deleted.

I have created a BOPF action which sets the deletion flag on the record in my underlying table, and I have implemented this action in my oData enabled CDS view so it renders the action on the screen. Then I have put a where clause in my CDS which checks if this deletion flag is blank.

All this stuff works as I want it...

Except for this strange behaviour ... When I execute the action on the list item, the app then navigates to the object page showing an empty object, the user then has to click back to get back to the list.

Any idea why this happens?


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 07 at 02:51 PM

    Hi Neil

    This behavior may be because your BOPF action returns a single node instance? If yes, then try to change the exporting type to "None"


    Add comment
    10|10000 characters needed characters exceeded

    • Indeed, when returning a single entity using an action, navigation is triggered to this entity, as after navigating to this "deleted" entity the deletion flag is set, as yyour CDS view excludes deleted entities the entity could not be found and a empty screen is being displayed.