Logic Apps EDIFACT connector update to support padding interchange qualifier

We are rolling out a small update to the Azure Logic Apps EDIFACT connector. With this update comes a new envelope setting 'BusinessIdentityQualifierPaddingType', an enumeration defining if and what padding needs to be performed on the interchange qualifier. This is defined as follows:

     /// <summary>
    /// The enum is defined to indicate number of zeroes to be used for padding business identity qualifier in EDIFACT interchange. 
    /// </summary>
    public enum BusinessIdentityQualifierPaddingType 
    { 
        /// <summary> 
        /// The BusinessIdentityQualifierPadding type is no padding. 
        /// </summary>
        None = 0,
 
        /// <summary> 
        /// The BusinessIdentityQualifierPadding type is one zero padding. 
        /// </summary> 
        One = 1,
 
        /// <summary> 
        /// The BusinessIdentityQualifierPadding type is two zeroes padding. 
        /// </summary> 
        Two = 2,
 
        /// <summary> 
        /// The BusinessIdentityQualifierPadding type is three zeroes padding. 
        /// </summary> 
        Three = 3, 
    }

We have rolled out earlier the support for decoding EDIFACT interchange with padded qualifiers. Please note that the qualifiers are trimmed when promoted to named properties while they remain as-is in both segment properties and generated acknowledgement (so your partner get the same as it sent). Here is a sample decode output extract for this:

  "goodMessages": [

    {

      "UNA_Segment": "UNA:+,?*'",

      "UNB": {

        "UNB_Segment": "UNB+UNOB:4+4859110:001+5521009:001+120528:1345+14+################+++0++0'",

        "UNB2.1": "4859110",

        "UNB2.2": "001",

        "UNB3.1": "5521009",

        "UNB3.2": "001",

        "UNB11": "0"

      },

      "UNH": {

        "UNH1": "8",

        "UNH2.1": "TAXCON",

        "UNH2.2": "D",

        "UNH2.3": "09A",

        "UNH2.4": "UN"

      },

      "decimalPointIndicator": 44,

      "repetitionSeparator": 42,

      "escapeCharacter": 63,

      "technicalAckExpected": true,

      "functionalAckExpected": true,

      "componentSeparator": 58,

      "dataElementSeparator": 43,

      "interchangeControlNumber": "14",

      "messageType": "https://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006#EFACT_D09A_TAXCON",

      "payload": "<...removed...>",

      "replacementCharacter": 63,

      "segmentTerminator": 39,

      "segmentTerminatorSuffix": "None",

      "transactionSetControlNumber": "8",

      "agreementName": "Agreement",

      "guestPartnerName": "Fabrikam",

      "hostPartnerName": "Contoso",

      "ReceiverIdentifier": "4859110",

      "receiverQualifier": "1",

      "SenderIdentifier": "5521009",

      "senderQualifier": "1"

    }

  ],

  "badMessages": [],

  "generatedAcks": [

    {

      "acknowledgement": {

        "unH1": "99",

        "UNH2.1": "CONTRL",

        "UNH2.2": "4",

        "UNH2.3": "1",

        "UNH2.4": "UN",

        "uci": {

          "ucI1": "14",

          "UCI2.1": "4859110",

          "UCI2.2": "001",

          "UCI3.1": "5521009",

          "UCI3.2": "001",

          "ucI4": "8"

        },

        "unT1": "3",

        "unT2": "99"

      },

      "ackPayload": "<...removed...>",

      "isFunctionalAck": false,

      "isTechnicalAck": true,

      "technicalAckExpected": false,

      "functionalAckExpected": false,

      "messageType": "https://schemas.microsoft.com/Edi/Edifact#Efact_Contrl_Root"

    },

Comments

• Anonymous
  June 20, 2019
  This blog has been moved off the MSDN platform. Find further content and update at https://www.linkedin.com/today/author/daviburgComments are locked as part of the blog migration, so please reach out to your customer support contact for assistance with Microsoft products and services.