Book Image

Enterprise Integration with Azure Logic Apps

By : Matthew Bennett
Book Image

Enterprise Integration with Azure Logic Apps

By: Matthew Bennett

Overview of this book

Logic Apps are a visual flowchart-like representation of common programming actions, and are a flexible way to create logic without writing a single line of code. Enterprise Integration with Azure Logic Apps is a comprehensive introduction for anyone new to Logic Apps which will boost your learning skills and allow you to create rich, complex, structured, and reusable logic with instant results. You'll begin by discovering how to navigate the Azure portal and understand how your objects can be zoned to a specific environment by using resource groups. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will teach you the benefits and foundations of Logic App logic design. As you advance, you'll find out how to manage your Azure environment in relation to Logic Apps and how to create elegant and reliable Logic Apps. With useful and practical explanations of how to get the most out of Logic App actions and triggers, you'll be able to ensure that your Logic Apps work efficiently and provide seamless integration for real-world scenarios without having to write code. By the end of this Logic Apps book, you'll be able to create complex and powerful Logic Apps within minutes, integrating large amounts of data on demand, enhancing your systems, and linking applications to improve user experience.
Table of Contents (17 chapters)
1
Section 1: Logic App Fundamentals
7
Section 2: Logic App Design
13
Section 3: Logic App Maintenance and Management

Run IDs

Every logic app run also has a unique GUID. Sadly, this is not the same GUID as the trigger GUID, but the same user experience is presented to us – we can search for a specific run by GUID or filter to a specific date and time. This allows us to then analyze the run, explore the data that's been gathered, and spot any errors that may have occurred. As a developer, I spent a lot of my time having to backtrack through a logic app run to obtain IDs or key data, as well as to troubleshoot where issues had occurred.

One extremely useful feature is the ability to resubmit a run. You should use this when you have made a minor correction and wish to update an existing record. However, you should resubmit with caution if you are resubmitting a run from a logic app that's been used for integration purposes – this may have unintended effects and cause duplicate records to be created:

Figure 9.14 – Trigger history on the Overview...