Ignoring partner qualifiers in Azure Logic Apps EDIFACT decoding

One of our customers was having invalid UNB segment, specifically the optional partner qualifiers within it, in EDIFACT message payload to decode. The decoding of UNB segment is required for EDIFACT and if partner qualifiers are present, they must be valid. Attempting to decode the invalid message as-is would result in error “The protocol of the message could not be recognized.”

The workaround was to trim the partner qualifiers from the incoming message, and use the Json view of the partner agreement in the Azure management portal to blank out (set empty string to) the partner qualifiers.