Correlation Message IBM MQ Connector in Logic App

Question

We have a Queue Manager (IBM MQ) defined Onpremise and connected to Azure Logic App. We use the IBM MQ Connectors (connectors-create-api-mq) to get and put actions.

We defined two workflows, one to request (Azure get a message from MQ) and other to response (Azure put a message to MQ), an Application Onpremise do a correlation with the ID that is set in the Message ID (mq) request property and copy in the CorrelID (mq) property over the response.

In summary, an App puts a message, Azure gets that, Azure puts the response, and the App gets the response.

We observe a problem in the integrity of the MessageID base 64 string used by Azure.

For example:
When the App puts the message, it has the MessageID property set (base64): xdTYQNTYydLixMXiwUBAQGFM/g8l18to
When Azure gets the message, it shows the MessageID as: XDTYQNTYYDLIXMXIWUBAQGFM/G8L18TO
The second workflow builds the response by copying the MessageID to CorrelID for correlation of the Apps.
When IBM MQ (onpremise) receive the response, it shows the CorrelID a: XDTYQNTYYDLIXMXIWUBAQGFM/G8L18TO

Note Azure change to Uppercase the base64 string ID.

IBM MQ and Apps are case sensitive and can't correlate the message.

We tried to use a String variable, convert from 64 to string, an unique workflow with the get and put and reference the field directly, but we get the same problem. Do you have some time or idea how to resolve that?

Answer 1

@Juan Carlos Brenes Can you please confirm if you are using the Send message or Send message (v2) (Preview) in your workflow. It would be great if you can share the screenshot of the input/output of this action. I believe you might be using the HTTP trigger to trigger the workflow with the input data from your application. It would be great if you can share the screenshot of the input/output of the trigger as I want to confirm if the messageID is changed to upper case on the Send message action or some other place in your workflow.