Skip to main content
Solved

Workflow cannot call OData Function AqEventBusTab_Default() (requires GET) — “Null value returned for key attribute 'Objkey' of entity type 'AqEventBusTab'”

  • October 28, 2025
  • 1 reply
  • 19 views
N
Do Gooder (Customer)
Forum|alt.badge.img+4
  • NINO
  • Do Gooder (Customer)
  • 11 replies

Hello,

My Workflow cannot call OData Function AqEventBusTab_Default() (requires GET) — “Null value returned for key attribute 'Objkey' of entity type 'AqEventBusTab'”

 

  • Base: https:///main/ifsapplications/projection/v1/CustomProjectionAqEventBusTab.svc
  • Function: AqEventBusTabSet/IfsApp.CustomProjectionAqEventBusTab.AqEventBusTab_Default()

 

 

A workflow service task using “IFS API” cannot successfully invoke the Default() function on AqEventBusTab.

The same call works via direct OData GET (Postman/Python).

 

In workflow, using “Action = Call” (POST) leads to an error: “Null value returned for key attribute 'Objkey' of entity type 'AqEventBusTab'.” It seems the workflow task cannot issue a GET to a bound OData Function, and calling it as POST causes the failure ?

 

 

Best answer by NINO

After investigation,
the Default() functions are not meant to be executed inside workflows.

Workaround used:
I created a custom attribute in the event that calls a PL/SQL function to generate the next ID. This allows the record to be created successfully.

 

 

And in my workflow :

Regards,

Nino

1 reply

N
Do Gooder (Customer)
Forum|alt.badge.img+4
  • NINO
  • Author
  • Do Gooder (Customer)
  • 11 replies
  • Answer
  • October 29, 2025

After investigation,
the Default() functions are not meant to be executed inside workflows.

Workaround used:
I created a custom attribute in the event that calls a PL/SQL function to generate the next ID. This allows the record to be created successfully.

 

 

And in my workflow :

Regards,

Nino


Terms & ConditionsCookie settingsAccessibility statement