I have an EDI document which contains the UNH2.5 segment. I uploaded an individual schema (attached as XML file) and configured the agreement's send/receive settings as per documentation.
The action "Encode to EDIFACT message by agreement name (V2) (Preview)" worked without problems, and segment UNH2.5 was recognized.
Problem is that every time I use the action “Decode EDIFACT message” it returns error "70: The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement."
It seems there’s an error in the Agreement and Schema resolution logic for this decoding action of the managed EDIFACT connector. Also tried to decode an EDIFACT without segment UNH2.5 and the issue persists.
Please, see attached XSD schema, JSON agreement and minimal EDI sample (which was encoded via Azure Logic App using "Encode to EDIFACT message by agreement name (V2) (Preview)" with the attached schema and agreement).
Plan Type
Consumption
Steps to Reproduce the Bug or Issue
Create an integration account
Setup partners in integration account
Upload schema in integration account
Setup agreement in integration account
Create a Consumption Logic App
Setup trigger "When a HTTP request is received"
Add action "Decode EDIFACT message"
Set the body of HTTP trigger as the EDIFACT flat file message to decode
Check error "70: The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement." in the "Bad Messages" section of the response
Describe the Bug
Hi,
I have an EDI document which contains the UNH2.5 segment. I uploaded an individual schema (attached as XML file) and configured the agreement's send/receive settings as per documentation.
The action "Encode to EDIFACT message by agreement name (V2) (Preview)" worked without problems, and segment UNH2.5 was recognized.
Problem is that every time I use the action “Decode EDIFACT message” it returns error "70: The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement."
It seems there’s an error in the Agreement and Schema resolution logic for this decoding action of the managed EDIFACT connector. Also tried to decode an EDIFACT without segment UNH2.5 and the issue persists.
Please, see attached XSD schema, JSON agreement and minimal EDI sample (which was encoded via Azure Logic App using "Encode to EDIFACT message by agreement name (V2) (Preview)" with the attached schema and agreement).
Plan Type
Consumption
Steps to Reproduce the Bug or Issue
Workflow JSON
Screenshots or Videos
No response
Additional context
attachments.zip