I have EDI files on a file server how do I decode them into xml/json/csv in azure?
I tried using logic apps X12 using the lookup artifact of the integration account.
After reproducing from my end, I could able to convert Edi files to XML from logic apps using Decode X12 message of X12 Connector.
Make sure you are adding the required schemas, Map, Partners and Agreement in your Integration account before executing.
NOTE: To create schemas or maps you require either of the following
Visual Studio 2019 and the Microsoft Azure Logic Apps Enterprise Integration Tools Extension.
Visual Studio 2015 and the Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0 extension.
You can refer more on Add schemas to use with workflows
Below is the flow of my Logic App.
Related
To create an enterprise integration solution using Azure Logic Apps I am trying to run the Enterprise Integration Pack in Visual Studio. I see that is supported only for VS2015.
installer
interesting blog EIP
But with many attempts my VS2015 installation for some reason never installs all tools with success (adding Azure SDK, EIP, App Logic Tools, sign to Azure Subscription with MFA..). And it is not supported anymore. Ultimately my target is to test complex XML mapping creating XSLT graphically (because for complex use case make it graphically is strongly easier). Essentially creating graphically what is called in Logic Apps "Maps". So how can I achieve that by passing all issues with VS2015?
Just to show one issue that I get when I try to loging to my Azure Subscription that is MFA:
It looks like Azure DevOps may have APIs similar to Office 365 but I'm not finding them in the documentation and when I called support they don't seem to know what I'm talking about. We are trying to build an integration like we have with o365 using Graph api's. Can anyone point me in the right direction- it seems like Azure DevOps is mostly an on-prem solution and not SaaS at this time.
Assuming you are talking about the former Visual Studio Online, and the current Azure Devops, then you have this article with the reference to its REST APIs. Also you have the option to use the Client SDKs with one of the programming languages available, to establish the integration.
You might looking for Visual Studio SDK documentation...
The Visual Studio SDK helps you extend Visual Studio features or
integrate new features into Visual Studio. You can distribute your
extensions to other users, as well as to the Visual Studio
Marketplace. The following are some of the ways in which you can
extend Visual Studio
Check this link: https://learn.microsoft.com/en-us/visualstudio/extensibility/visual-studio-sdk?view=vs-2019
I am an experienced BizTalk developer who is now moving on to Azure logic apps. I have installed Visual Studio 2017 and added the "Azure Logic Apps Tools for Visual Studio" through the Tools|Extensions and Updates menu. However, I don't see an option for creating/editing XML schemas(.xsd files), I don't see the BizTalk EDI X12 schemas and there is no option for creating a map. What am I missing? I have searched and searched with no luck. Thanks.
XSD & Maps are part of the Azure Integration Account service. You need the Microsoft Azure Logic Apps Enterprise Integration Tools in order to use those. You will see that the mapper is very similar to what you know from the BizTalk-world.
I'm not sure Microsoft Azure Logic Apps Enterprise Integration Tools is already supported in VS 2017. I know it's supported on VS 2015.
On a side note, xsd's and maps created using a BizTalk Server Project will also work fine in an Azure Integration Account and Logic Apps,but might lead to a more complex ALM-story.
Right now there is no tooling available for Visual Studio 2017, only for Visual Studio 2015.
The tools are based on the BizTalk components and those components are only available for Visual Studio 2015.
You can download EDI schemas from Open Source Github, but only EANCOM and EDIFACT, X12 messages have been removed due to licensing questions https://github.com/Microsoft/Integration/tree/master/BizTalk%20Server/Schema
In Visual Studio 2015 ,there's a project templates for some azure service(etc:blob、storage:queue).
Now, I'm using Visual Studio 2017 enterprise ,i can't find the project template after intalled Azure SDK.
How can i fix this?
The quickstarts aren't included in the box in 2017 - you can find the latest here:
https://github.com/Azure-Samples?utf8=%E2%9C%93&q=storage-dotnet&type=&language
Azure Cloud is the monicker for the entire suite of products. Are you looking for the Asp.Net Core template that will run in Azure? Click on .Net Core and choose Asp.Net Web and it will set up a quick start for you that already can be published to Azure. Or was there a specific kind of template are looking for that isn't Asp.Net Core?
Edit: It's possible VS 2017 Azure SDK didn't release console templates yet. Having said that, the templates you have show how to use the Azure Storage code in a .Net Core project. They are less boilerplate and more tutorial. You should create a test one, see how the code works, then create a normal, basic .Net Core Console project and re-implement the code how you want it. There is nothing special about a quick start template except some pre-included dependencies and sample code.
I just installed Visual Studio 2013 Update 3 and Azure SDK 2.4. I also installed "Microsoft Azure Tools for Microsoft Visual Studio 2013 -v2.4". I also tried repairing and reinstalling both the sdk and the Azure tools.
I can see 4 templates under Cloud (Azure Cloud Service,ASP.NET web application,Microsoft Azure WebJob and Azure Mobile Service) when creating a C# project.
There is no Cloud folder and no Azure templates at all when creating a F# project.
Is F# not supported or is it something wrong with my installation? I think it was supported earlier.
The F# template for Worker Roles is available as you are creating your Cloud Service project.
Create a Cloud Service project using C# or Visual Basic.
Next, as you are selecting the roles for your cloud service, you can select the F# Worker Role.
Full Disclosure: I've not actually used the F# template. I just recall seeing it when creating my C# projects.