While you may have noticed this or not, but it’s real. Now Dynamics 365 CE existing table types have a new companion called Elastic, it is yet to be announced.
However let’s take a quick look of the table types showing up when you were trying to create a new one in Dataverse.
While everyone is aware about Standard, Activity, Virtual types in Model Driven Apps. Elastic tables are new tables which came in to Dataverse and probably it will be announced in the upcoming Microsoft Build 2023.
From my view, Elastic tables were
1. Built similar to the concept of Elastic Queries in Azure which is usually meant for the purposes of Data archiving needs.
2. You can scale out queries to large data tiers and visualize the results in business intelligence (BI) reports.
3. Elastic Query provides a complete T-SQL Database Querying capability on Azure SQL, possibly Dataverse.
Hope we get all the capabilities released with Elastic Queries of Azure SQL be released in Dataverse as well.
This blog post talks all about integration of your Logic apps to your Dynamics CE instance and it’s advantages. Lets get started…
By the way, I can’t redefine the definition provided by Microsoft, so here it goes.
Azure Logic Apps is fully managed integration PaaS service that helps you schedule, automate, orchestrate tasks, business processes, and workflows when you need to integrate apps, data, systems, and services across enterprises or organizations and simplify how you design and build scalable solutions for app integration, data integration, system integration, enterprise application integration (EAI), and business-to-business (B2B) communication, whether in the cloud, on premises, or both. It’s simple to say that you can integrate any system and it is built on a containerized runtime.
Now let’s understand how does the logic apps work:
Every logic app workflow starts with a trigger, which fires when a specific event happens, or when new available data meets specific criteria. Each time that the trigger fires, the Logic Apps engine creates a logic app instance that runs the actions in the workflow. These actions can also include data conversions and flow controls, such as conditional statements, switch statements, loops, and branching. As soon as the Logic App stops running, these resources are discarded.
The interesting part here is that Logic Apps is more developer friendly and can used directly create integrations using logic apps either from Visual studio, Visual Studio Code or browser.
We were given flexibility to choose the type of Logic Apps, Single-tenant and multi-tenant. While creating logic apps, we can use Standard or Consumption based resource type. Logic Apps can create complex orchestrations and it is serverless. This means there is no upfront knowledge required for developer about the infrastructure. You have to bear in mind that it is both a stateful and stateless service unlike Azure Function which is stateless. It allows you to use webhooks as triggers. Coming to the pricing part, the price of Microsoft Azure Logic Apps is inexpensive. Look at it’s architecture below
You can simply edit your Azure logic App in Visual studio code / Visual studio and push your changes to your Devops repository…wow such a easy approach…don’t forget to try it out…
Do let me know if you have any queries or if you can add any more points, do let me know in comments….
That’s it for today…will come back next week with another article in #PowerfulAloneBetterTogether Series.
ECELLORS CRM Blog 