A custom command calling a custom projection action fails with "Client Warnings are not supported for the action" and a 405 Method Not Allowed, even though the underlying PL/SQL code doesn't raise any warnings or touch request headers, and an equivalent action on the same projection works fine.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This has been resolved in at least one case by adding the same action under a different name and wiring it up through a plain "ExecuteAction" command-group item instead of however the original command was configured — with that change, the request no longer carried the X-IFS-Accept-Warnings header that was triggering the error, even though the underlying action code and parameters were otherwise identical. If you hit this exact error on a custom command, recreating the command through a command-group ExecuteAction item is worth trying before spending more time debugging the projection action itself.

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

← Browse Developer Studio, deployment, and upgrades questions