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

List records versus Get record

While they are very similar, the Get record and List records actions are significantly different in how they are configured. Starting with Get record, the primary key (the GUID of the entity) needs to be known in advance. If I, for example, wanted to look up my user account in Dynamics 365, I would reference the environment I am interested in, the Users table, and add the Contact GUID. This would report back with the full record for that one record.

Figure 11.4 – The Get row action uses the primary key of the entity. This can be hardcoded or accessible based on the contact in scope

You will notice that where you have a trigger such as Delete record starting your logic, only the GUID will be available. If you want to still be able to access any data from any fields on the deleted record, you will not be able to. One workaround is to instead use the Deactivate button in Dynamics (for example), which will change the state...