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…

0

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

Azure Logic App X12 replacing separator characters in payload

Using the B2B X12 connector for Azure Logic App, sometimes the input xml values in the payload has reserved characters which conflict with the X12 encoding that you are attempting. X12 agreement with your external partner defines a segment separator character which then cannot be present as well in the value of the segment. By…

0

Logic App and B2B Integration Account monitoring solution right from the Azure portal

New in the Azure Marketplace you can now create a Logic App or Integration Account OMS monitoring solution right from the Azure portal, simply searching by the keywords “Logic App”: The Logic Apps Management solution was released to public preview earlier this month (see this blog post).  

0

Logic App, B2B diagnostics logging, monitoring and alerting documentation newly expanded

The documentation writer and our engineering team has recently scrubbed for quality and expanded for holistic coverage our documentation of both Logic App and B2B integration diagnostics logging, monitoring and alerting. The improved documentation was released just last Friday at: Monitor Logic App status Monitor B2B messages Track B2B messages in OMS Query OMS for B2B…

0

Whitelisting and Logic Apps

As B2B services move from on-premises servers to Azure Logic App, a recurring question is how to do both inbound and outbound (by the partner) whitelisting with such PaaS approach. On-premises this was easy because each enterprise obtained its own static IP, IPs or IP range. In Azure or any public cloud, the IPs are now…

5

EDIFACT Disaster Recovery PowerShell cmdlets

With the upcoming Disaster Recovery trigger and action for the EDIFACT connector, the existing PowerShell cmdlets in Logic App have been updated to handle EDIFACT control numbers as well. This is the relevant excerpt from the change log: […] * LogicApp * New parameters for Interchange Control Number disaster recovery cmdlets: – Optional -AgreementType parameter (“X12”,…

0

AS2 connector disaster recovery

Logic App enterprise integration AS2 connector disaster recovery is rolling out today in production with MIC replication. See the updated documentation at https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-enterprise-integration-b2b-business-continuity#as2 West Central US region is available immediately with all remaining regions for Logic App enterprise integration following in the next few days.

0

Azure Logic App template for X12 connector control numbers replication for disaster recovery published on quick start

I’ve just now published a Logic App template for X12 connector control numbers replication for disaster recovery on Azure quick start template on GitHub. This enables a very easy tryout with the “Deploy to Azure” button: As well as powerful automation using either Azure CLI or Azure PowerShell to deploy the same with customized input parameters. See…

0