Maybe error handling can help you out:
Good afternoon Tom, first thank you for your contribution. In my case I'm exposing an api and not consuming this solution so I believe I couldn't solve the problem. I would be able to apply something without
You can but you will loose a piece of Mendix magic.
Your service usually takes care of three steps: import mapping, calling the microflow, the export mapping.
Instead of having your service take care of the import mapping, make it pass the request-content as a string. Your microflow can do the import-mapping, the Client’s ‘find by key’ will result in an error, so in your microflow set error-handling on the import-mapping activity. On handling the error, change HttpResponse (that you need to have as import parameter of the microflow). Set HttpResponse/Message to whatever you like.
** Editted ** Well, actually, yes you can do this the way you like, if set the mapping instead of Error, to Ignore.
You will get to your microflow and in your microflow, if you have no associated client, set the HttpMessage like I described above.
Good afternoon Tim, thanks for the reply. Got it, so using Mendix's default import mapping I wouldn't be able to change the return message?