This blog has moved

The date has finally come for the move of this dev blog off the MSDN platform. After considering several options, I am moving to LinkedIn articles for sharing future updates about Azure, Logic Apps, BizTalk, B2B integration, iPaaS, XML, SAP, Flat File, .NET, APIM, Azure Functions, etc… Please go in the future to https://www.linkedin.com/today/author/daviburg Some of…


Large request upcoming support for Azure Logic App SAP Connector

I’ve completed the development work for the support of large requests in Azure Logic App SAP Connector. With this upcoming new feature, users will be able to send requests to SAP and the On-Premises Data Gateway via an Azure Storage Blob SAS URI like this: Please note that the Blob itself and its SAS URI…

1

Responding back to SAP from Logic App

So you’ve registered SAP as a trigger in Azure Logic Apps, enabling SAP to call it as for any other RFC. But how do you parse the SAP request and respond back to it with actual content and not just a vanilla OK? If you enable the support for multiple RFCs by your Logic App…

2

New Logic App connector error responses to SAP

The next update to On-Premises Data Gateway SAP Adapter component for Azure Logic Apps SAP connector will include implementation of error condition translation to ABAP exception or BAPI return depending of what is available in the invoked RFC metadata. This will come in use when using the SAP trigger of the connector (when a message…

1

Logic App SAP connector IDoc support – going under the hood

While working on a customer inquiry, I recently investigated the details of our logic for IDoc support, including browsing which are available in the SAP system, forming the hierarchical view to pick an action URL from and generating the metadata / XML schema for the request-response payload. The following details are not a public contract,…

1

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…

1

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…

1

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…

1

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….

1

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.  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…

1