Learn how Liquid and XSLT maps are referenced from Logic Apps workflows
Study batching, Foreach concurrency, and partial-success patterns for integrations
Adapt the JSON-to-XML order-batch map for a real ERP integration
Trace a Logic Apps execution end to end using a correlation ID
Needs an Azure subscription with Logic Apps Standard plus the local Logic Apps tooling to run the workflows.
This repository is a personal learning project by the author, Pratish10, built to explore Azure Logic Apps and the different ways it can move data between JSON and XML formats. Azure Logic Apps is a service from Microsoft that lets you build automated workflows in the cloud by connecting triggers, actions, and data transformations without writing a full application. The author treats this repo as a hands-on playground for enterprise integration patterns rather than a finished product. The project includes four end-to-end transformation examples. The first uses a Liquid template to reshape JSON order data, look up product information, calculate per-line totals, and assign discount tiers. The second turns JSON into XML order batches using XSLT 3.0, including headers, line items, totals, and audit metadata. The third uses XSLT to do the reverse, converting XML purchase orders into JSON with high-value-order flags and summaries. The fourth uses XSLT 1.0 to convert an XML purchase order into an XML delivery note, with line totals and a grand total. Around those maps, the workflows also cover the operational side of an integration: HTTP-triggered entry points so an external system can call the workflow over the web, batch input that arrives in chunks, parallel processing through a Foreach loop with concurrency, and structured response shapes for success, partial success, and error cases. Each workflow also passes a correlation ID through the steps so a single execution can be traced from start to finish in the logs. The repository is organized into an Artifacts/Maps folder that holds the four Liquid and XSLT map files, plus one folder per workflow with its workflow.json definition, and the standard Logic Apps configuration files (connections.json, host.json, local.settings.json) at the root. The README's closing notes describe what the author took away from the exercise: how maps are referenced from workflows, which transformation engine fits which scenario, and how to structure a workflow for batching, validation, tracing, and error handling. It is presented as a study repo, not a library you would install.
Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.