Create an Automated Flow with Dataverse as a Data Source | PL-400 Exam Answer

Connectors for Automated Flow with Dataverse as a Data Source

Question

You need to create an automated flow using the Dataverse as a data source.

You select "When a record is created" as a trigger and "Predict using AI Builder models" as one of the actions.

Please select the connectors that you use in your flow.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Correct Answers: B and D

Dataverse provides three connectors that Power Automate can use: Common Data Service, Common Data Service (current environment), and Dynamics 365 connector.

Each of the connectors has a list of triggers and actions.

There are similar triggers and actions between all connectors.

The Common Data Service provides “When a record is created,” “When a record is updated,” “When a record is deleted,” and “When a record is selected” triggers (Number 1)

Instead of separate triggers for a record update, create and delete conditions, Common Data Service (current environment) has one "universal" trigger: "When a row is added, modified or deleted" (Number 2)

It uses the word "row" instead of "record."

Triggers Actions

When a row is added, modified or deleted | PREMIUM

Common Data Service (current environment)

When a flow step is run from a business process flow

PREMIUM

Common Data Service (current environment)

When a record is deleted | PREMIUM
Common Data Service

When a record is updated | PREMIUM
Common Data Service

When a row is selected | PREMIUM
Common Data Service

When a record is created | PREMIUM
Common Data Service

The "universal" trigger reflects the difference between the two connectors.

If you use any Common Data Service trigger, it will ask you to provide Environment, Entity Name, and a Scope (Number 2)

If you input a "(Current)" value for an environment, the connector will behave as Common Data Service (current environment)

With the Common Data Service (current environment) connector, you do not need to provide environment information and focus on the trigger condition (Number 1).

When a record is created

El When a row is created, updated or deleted & oe *

* Trigger condition Choose an option or add your own. iy? * Environment (Current)
*The table name eee * Entity Name Accounts
Create or Delete
*
*Scope Create or Update Scope Scope.
Create or Update or Delete Lo Bussiness unit
Show advanced options aaa
Delete Organization
Update , Parent: Child business unit
Update or Delete User
Enter custom value Enter custom value

ne (SS es CE

The Common Data Service (current environment) connector has the same actions as the other two but also half a dozen more, like “Relate rows,” “Predict using AI Builder models,” “Perform a bound action,” “Get file or image content,” and others.

Ss When a record is created @ ::

J

S| Common Data Service (current environment) @ xX

<< Search connectors and actions
Triggers Actions See more

Download a file or an image | PREMIUM
Common Data Service (current environment) ©
Get a row by ID | PREMIUM
Common Data Service (current environment) ©
List rows | PREMIUM
Common Data Service (current environment) ©
Perform a bound action | PREMIUM
Common Data Service (current environment) @
Perform an unbound action | PREMIUM ®
Common Data Service (current environment)

Predict using AI Builder models | PREMIUM
Common Data Service (current environment)

Relate rows | PREMIUM

Common Data Service (current environment) ©
Unrelate rows | PREMIUM oO
Common Data Service (current environment)

Update a row | PREMIUM

Common Data Service (current environment) ©

The Dynamics 365 connector has the same triggers and actions as the Common Data Service connector, but Dynamics 365 connector is deprecated.

Microsoft recommends using Common Data Service (current environment) for all your Dataverse and Dynamics 365 data connection needs in the new flows.

The Common Data Service connector can benefit you when you need to synchronize data between two environments.

All other options are incorrect.

For more information about the Dataverse connector's triggers and actions, please visit the below URLs:

To create an automated flow using Dataverse as a data source, we need to use connectors that allow us to connect to and manipulate data within Dataverse. In this scenario, we are using the "When a record is created" trigger and the "Predict using AI Builder models" action.

The correct connectors that we can use in our flow are:

B. Common Data Service (current environment): This connector allows us to connect to the current environment's Common Data Service, which is a service that lets us store and manage data within Dataverse. We need to use this connector to create a trigger that listens for a new record being created in Dataverse.

C. AI Builder: This connector allows us to use AI Builder models within our flow. We need to use this connector to create an action that predicts using an AI Builder model.

Therefore, the correct answers are B and C.

A. Dynamics 365: This connector is used to connect to the Dynamics 365 platform, which is a set of enterprise resource planning (ERP) and customer relationship management (CRM) applications. Although Dynamics 365 can connect to Dataverse, it is not required in this scenario.

D. Common Data Service: This connector is similar to the Common Data Service (current environment) connector, but it allows us to connect to a specific instance of Dataverse. We do not need to use this connector in this scenario since we are using the Common Data Service (current environment) connector.

E. Microsoft Teams: This connector is used to connect to Microsoft Teams, which is a chat-based collaboration platform. It is not required in this scenario as we are not using any Teams-related actions or triggers in our flow.