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

Why the new SAP connector for Logic Apps

When you search for the keyword SAP in the Azure Logic Apps designer action card, you will see three connectors, four actions (and one trigger, not shown here): Why did we introduce earlier this year this new SAP connector in addition to the earlier SAP Application Server and SAP Message Server connectors? The new connector…

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

Where’s my node? Logic Apps Flat File Decode beware suppress empty nodes unintended effect

The flat file schema property ‘suppress_empty_nodes’ is described as “Indicates whether or not to remove empty XML nodes after the parser generates XML instance data.” in the documentation https://msdn.microsoft.com/en-us/library/aa559329.aspx Sandro Pereira blogs about how this can be helpful in his post Teach me something new about Flat Files. However you will not want to suppress…

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

Anti-patterns in iPaaS

Here are a couple of anti-patterns which have surfaces recently in my interactions supporting customers of Azure Logic Apps:  IP white-listing With on-premises integration solution, it used to be that the elements of the integration system were residing on specific static servers, such as their IP(s) as client of other services were static and well-known….

0

Non-Unicode SAP systems support and improved parallel performance for Logic Apps SAP connector

With the release of the October version of the On-Premises Data Gateway (here), the SAP connector for Logic Apps now supports sending and receiving messages from SAP system configured to use non-Unicode encoding of characters such as page-code based encoding. Also with this release, significant concurrency issues have been lifted, such that as many requests…

0

Escape characters illegal in XML with hex character reference through an Azure Function V2

Just now published sample code Visual Studio 2017 project on GitHub at https://github.com/daviburg/CSharpUtilities/tree/master/Sources/Daviburg.Utilities/Daviburg.FixToXmlCharacters demonstrating a C# Azure Function V2 that escapes characters illegal in XML to an hex character reference, i.e. &#xFFFF; value. We have seen users migrating from non-Microsoft platform to Azure iPaaS having difficulties with XML messages which did not comply to W3C’s specification…

0

Strongly typed date and time fields for SAP connector, and NUMC fields

These types have been a source of headache for users of BizTalk Server SAP Adapter as demonstrated by the amount of blog posting, forum questions and the existence of the SAP adapter binding connection parameter “EnableSafeTyping” and the further complication of a fine grain 12-toggles DataTypeBehavior binding connection parameter. Refer to posts from last decade:…

0