Common Data Service (current environment) Connector Triggers for Power Automate Flows | PL-200 Exam Preparation

Common Data Service (current environment) Connector Triggers

Prev Question Next Question

Question

You create an automated flow using Dataverse.

Please select all triggers that Common Data Service (current environment) connector provides for Power Automate flows.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Correct Answers: B and C

Dataverse provides the 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, like “When a record is created,” “Create a new row,” or “Create a new record.”

The Common Data Service (current environment) (Number 1) and Common Data Service connector (Number 2) have the following triggers:

Environment Cle ' (default) < App checker @ x Nadas © Recheck all Formulas (5) Runtime Rules Accessibility (16) Performance (3)

Instead of separate triggers for a record update, create and delete conditions, Common Data Service (current environment) has one "universal" trigger: "When row is created, updated or deleted." It uses the word "row" instead of "record."

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

Power Apps File Home Insert View Action C] Newscreen~ A8 Theme v = Bordery | @ Reorder’ |& Align v rs) Av @ Fil DisplayMode viE= fey If(!IsBlank(BrowseGalleryl.Selected) && DataSourceInfo( [@SiteInspector], DataSourceInfo.DeletePermission), DisplayMode.Edit, Disp ayMode. Disabled)| _ . If(!IsBlank(BrowseGallery1 Selected) && DataSourcelnfo([@Sitel.. = edit Data type: text = Tree view ii} Screens Components | PB Search EP App v © BrowseScreent > IBY CompositeColumnChart1 CA Rectangle11 83 searchlcon1 =D TextSearchBoxt $3 IconNewltem1 $3 IconSortUpDown1 8% IconRefresht LblAppNamet A) RectQuickActionBart > BG BrowseGallery1 ~ © Detailscreent > EB) DetailForm1 [A LblAppName2 92 IconDeletet 23 IconEditt 28 IconBackarrow1 AL RectQuickActionBar2 © betailscreent 22 IconDeletet <_ Sitelnspector Address 11155 NE 8th City Bellevue Description Big 86934 sq ft lot with 4-story 48568sq ft reinforced concrete building. Building has elevators, sprinklers, and parking for 100+ vehicles. ID 1 IsGPSCoordinates True Latitude 47.617187 Longitude -122.191686 Notes Buidling built in 1980 with significant renovations in 1990 Location $2 IconDeletet DisplayMode How to fix (4) Use variables, collections, and navigation context to share state across screens instead Why fix Controls that reference controls on other screens can slow down app loading and navigation. Doing this may force the app to load the other screens immediately, rather than waiting until the user navigates to that screen. Learn more about optimizing your canvas app's performance View activity in your app to understand performance and identify bugs. EN Open monitor

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.

Options A, D, and E are incorrect because these triggers are Common Data Service connector triggers, but not Common Data Service (current environment).

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

Sure, I'd be happy to explain!

The Common Data Service (current environment) connector provides several triggers for Power Automate flows. These triggers allow you to initiate a flow when a certain event occurs in Dataverse (formerly known as Common Data Service).

Here are the triggers provided by the connector and their explanations:

A. When a record is selected: This trigger is not provided by the Common Data Service (current environment) connector.

B. When a row is created, updated or deleted: This trigger initiates the flow when a new row is added, updated, or deleted in a specific table in Dataverse. You can choose which table and which operation (create, update, or delete) you want to trigger the flow.

C. When a flow step is executed: This trigger is not provided by the Common Data Service (current environment) connector.

D. When a record is deleted: This trigger initiates the flow when a specific record is deleted from a table in Dataverse. You can choose which table and which record to monitor for deletion.

E. When a record is created: This trigger initiates the flow when a new record is created in a specific table in Dataverse. You can choose which table you want to monitor for new records.

So, the correct answers to the question are B, D, and E.

Prev Question Next Question