Logic Apps B2B encode minor update

We are rolling out a small fix to Logic Apps B2B connectors (EDIFACT and X12) for their Encode API. We were not catching properly exception from invalid XML document user input where the document contained XML complex type Choice or All elements which actual occurrences count exceeded the maximum specified in the XML schema. For…

0

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…

0

Special characters in Logic Apps B2B partners identifier

The text field for qualifier value in Azure portal under Integration Account > Partners > Set (AS2|X12|Edifact) Identity allows you to enter alphanumerical characters and a set of special characters limited to ‘-‘ (dash), ‘(‘, ‘)’ (parenthesis) and ‘.’ (dot). However the RFC 4130 defining the allowed characters in an AS2 partner identifier specifies a…

0

AS2, EDIFACT connectors updates for Azure Logic Apps

We are currently deploying the following minor updates to all regions for AS2 and EDIFACT connectors. AS2 German and Spanish localization fix for Resolve Agreement actions (removing end period from operation description and summary for Logic Apps Designer support) EDIFACT enable support of & > < ! ” ; % * in EANCOM message EDIFACT…

0

Fix for Logic Apps Log Analytics B2B solution “Oops… Looks like we couldn’t get the data”

We are rolling out a fix for the following error in Logic Apps Log Analytics B2B solution. The error was visible in the summary tile, partners and X12/EDIFACT  tiles of the solution.   The error manifested when the EDIFACT acknowledgements lack the TSN (Transaction Set Number). From our on-call engineer: “The issue here is the field…

0

Azure Logic Apps connected to SAP, and now what?

So we’ve released to public preview the SAP connector for Azure Logic Apps which lets you call or be called as RFCs, BAPIs, as well as send and receive IDOCs. But beyond the technical aspect, what does that mean in terms of business process, patterns you can enable with these? What does it really mean…

0

Logic Apps X12 connector control of Group Header field GS08 aka Version Release Identifier

When you edit the X12 agreement in the Azure Portal blade for Integration Account, you see under the receive and send settings a picker for the ISA12 field aka Control Version Number. But what about the Group Header field GS08 aka Version Release Identifier? You can control this with the agreement property groupHeaderVersion in the envelope…

0

Support non-UTF payloads in Logic App with a conversion Azure Function

Much of cloud services assume that a text payload will be some form of UTF (unicode) encoding. Some even do assume it is UTF-8. Such that when your text payload is in a different encoding, such as a page code based encoding, the non-basic latin characters gets mangled. This is particularly common with Flat Files…

1

Calling Logic App from Cleo VLTrader

Here are anonymized notes from a live troubleshooting session for customers who were trying to send AS2 messages from Cleo VLTrader client to Logic App with HTTP request trigger and AS2 connector. The client is using 3rd party software VLTrader from Cleo. https://www.cleo.com/cleo-vltrader/ Initially VLTrader client was receiving a 400 Bad Request response and Logic…

0

Troubleshooting Logic Apps X12, EDIFACT schema not found issues

As you attempt to encode an outgoing B2B message with Logic Apps, you sometimes get a 400 Bad Request response with the error message: Message cannot be serialized since the schema http://Contoso.X12810.MSLI.Schemas.AP.X1200401810#X12_00401_810 could not be located. Either the schema is not deployed or multiple copies are deployed. Which we are improving for cases that there…

0