This post has been republished via RSS; it originally appeared at: MSDN Blogs.
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:
