Menu
Logic-apps allow you to do lots of EDI / file-processing operations, such as flat-file decoding:
The FromApexDemoEntry is a schema that is hosted in the integration account.
Is it possible to perform these operations without having an integration account?
For example, could we simply have an Azure Function that will accept a message along with with a schema and perform the flat file decoding step without having to go to an integration account?
276
Integration Account is a part of the Azure Logic Apps Enterprise Integration Pack (EIP) that is a secure, manageable, and scalable container for the integration artifacts that are created.
In the Azure portal, open an existing logic app, or create a new logic app. On your logic app's menu, under Settings, select Workflow settings. Under Integration account, open the Select an Integration account list, and select the integration account you want. To finish linking, select Save.
By building a logic app workflow, you can encode and decode flat files by using the built-in Flat File actions. Although no Flat File triggers are available, you can use a different trigger or action to get or feed the XML content from various sources into your workflow for encoding or decoding.
Logic Apps can scale depending on the connector(s) you use, for instance, the File System connector current limit of 100 calls per minute. Like Logic Apps, Azure Functions can run under a consumption plan – instances of the Azure Functions host are dynamically added and removed based on the number of incoming events.
How to remove dependency from the solution. If you want to remove unmanaged components you need to delete them one by one. As you know there is no straight uninstall in case of unmanaged. So delete all components individually. How to remove dependency from the solution.
The dependencies issue could be solved in two ways: with quick fixes or fundamental long-term solutions. The quick fix is to visualize and manage the dependencies. E.g. creating additional coordination roles or using specific techniques ("ropes on the boards"). Yes, it somehow helps to survive and continue the movement.
The bad news is that a strong culture of “managing dependencies” will hinder the implementation of the fundamental solutions. The more dependencies the less agile organization becomes. Dependencies thrive because of the unnecessarily complex architecture, lack of skills, and suboptimal organizational design (component teams).
Uninstalling an unmanaged solution isn't an option for removing this dependency, because unmanaged solutions are just a means to group components. Managed dependencies are the ones where the dependent component is associated to a managed solution. To resolve this kind of the dependency, you must act on the solution where the component was added.
For EDI specifically, you must have an Integration Account because that is where all of the EDI configuration exists. There is no practical way around this.
Keep in mind, EDI is different from 'flat files'. Native flat file processing also required an Integration Account because of the schemas.
While you theoretically could parse a flat file in a Function and Loop over the result in a Logic App...you really don't want to. It would be a lot of custom parsing code to duplicate something that's already built into Logic Apps.
You will almost certainly spend more money developing a custom solution than just paying for the Integration Account.
123
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
