PL 400: configure steps to use Dataverse connector actions and triggers(Configure Power Automate)

Data is one of the most valuable assets a business can have and potentially has a tremendous impact on long-term success. It helps us in finding new customers, making better decisions in customer retention, customer services and more. Microsoft Dataverse is the data backbone that enables people to dynamically store their data in a scalable and secure environment. It enables data to be viewed as a service that is tailored on-demand to meet ever-changing business needs. On the background, it powers many Microsoft Dynamics 365 solutions such as Field Service, Marketing, Customer Service and Sales. It's also available as part of Power Apps and Power Automate, with native connectivity built-in. Power Automate allows us to do more with fewer manual tasks, saving time and money. Microsoft Power Automate allows us to connect to hundreds of different programs and services across the web and helps automate entire processes.


Microsoft Power Platform provides connectors for communication between other products. It is a proxy or wrapper around an API that allows the underlying service to communicate with Microsoft Power Automate, Microsoft Power Apps and Azure Logic Apps. There are over 300 connectors available to use natively and the Dataverse Connector provides seamless integration with other products from Cloud Flow. It provides multiple triggers to start the flow and many actions that we can use to create or update data in the Dataverse while the flows run.

A series of triggers and actions help create automated workflows with Power Automate. A trigger is the event that initiates a cloud flow to whom and when to send a specified evaluation based on specific circumstances.

The triggers in Dataverse are:

  • When a flow step is run from a business process flow - This trigger allows a flow to be started when the Run Flow button is clicked in a business process flow step.
  • When a row is added, modified, or deleted - This trigger allows a flow to be started when a row is added, modified, or deleted in a Microsoft Dataverse table, such that it matches the selected options.
  • When an action is performed (preview) - Triggers when the Microsoft Dataverse action is complete.

The actions in Dataverse are:

Microsoft Dataverse Connector provides the following actions to help us manage data in Microsoft Cloud Flows.

  • Create a new row
  • Update a row
  • Search rows with relevance search
  • Get a row
  • list rows
  • Delete a row
  • Relate rows
  • Unrelate rows
  • Execute a changeset request
  • Get file or image context
  • Perform a bound action
  • Perform a unbound action


Configure steps to user Dataverse connector actions and triggers:

  • Open Power Automate (https://powerautomate.microsoft.com/)
  • Select Create and then Automated cloud flow.


  • Name flow and then search for and select the Dataverse Triggers. 
  • Select Create.


  • Configure selected trigger with the Change type, Table name, and Scope parameters.


Comments

Post a Comment

Popular posts from this blog

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power ...
Read more

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more