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

How and when to use logical and physical field naming

In summary, a data field can be referenced in one of three ways:

  • On the CRM itself, every data field has a label. The label contains label data and the label object on the form has a label object name. This, however, has no bearing on the data field it is associated with.
  • Labels sit next to data fields. These have a logical name and only the logical name is visible from the GUID. CDS will also reference the logical name. Searches in the dynamic catalog will uncover fields by their logical name.
  • OData queries and references to parameters or fields in Logic Apps code view refer to the physical name of the field. SQL queries likewise operate at this lower level when addressing the database. The physical name of the CDS field is the physical name within the database.

As a rule of thumb, we should use logical names where the Dynamics 365 field is correctly indexed. If it is a custom field, it might not exist in...