Adding ?odata-debug=json to a projection call produces detailed trace information when called as an interactive end user, but returns nothing useful in the ifs-trace output when the exact same call is authenticated with client credentials (a service/integration account).

All FAQ questions / Integrations and APIs

Answer

Check two things for the service account specifically: that the SQL_TRACE system parameter is turned on, and that the DEBUGGER system privilege is granted to that service account — trace output for odata-debug=json depends on both, and a service/integration account commonly doesn't have DEBUGGER granted by default the way an administrator's interactive account might, which silently suppresses the detailed trace even though the call itself succeeds or fails normally.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions