It turned out that we had a workflow post create function that set the response type to an invisible type request type. This overruled our project settings and resulted in an empty value. Removing the post function in the workflow resolved the issue.
Has this always been the case? If you are in a position to test, could you create a new request type and try to use it instead?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.