Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Enterprise Integration with Azure Logic Apps

You're reading from   Enterprise Integration with Azure Logic Apps Integrate legacy systems with innovative solutions

Arrow left icon
Product type Paperback
Published in Dec 2021
Publisher Packt
ISBN-13 9781801074728
Length 294 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Matthew Bennett Matthew Bennett
Author Profile Icon Matthew Bennett
Matthew Bennett
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Section 1: Logic App Fundamentals
2. Chapter 1: Getting Started with Azure Logic Apps FREE CHAPTER 3. Chapter 2: Environments and Resource Groups 4. Chapter 3: Referencing Data within Actions 5. Chapter 4: Reading Complex Data 6. Chapter 5: Manipulating Data 7. Section 2: Logic App Design
8. Chapter 6: Working with the Common Data Service 9. Chapter 7: Working with Azure Functions 10. Chapter 8: Scoping with Try/Catch Error Handling 11. Chapter 9: Sharing Data with Other Logic Apps and APIs 12. Chapter 10: Monitoring Logic Apps for Management Reporting 13. Section 3: Logic App Maintenance and Management
14. Chapter 11: Fine-Tuning Logic App Runs with Run After 15. Chapter 12: Solving Connection Issues and Bad Gateways by Rerunning Logic Apps 16. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Enterprise Integration with Azure Logic Apps
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime
Modal Close icon
Modal Close icon