Q: 1
Note: This question is part of a series of questions that present the same scenario. Each question in
the series contains a unique solution that might meet the stated goals. Some question sets might
have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.
You are creating a cloud flow that will use two Update Row actions to interact with Microsoft
Dataverse. Neither of these actions are dependent on each other.
You must minimize the amount of processing time require to complete the flow.
You need to implement the actions in the cloud flow.
Solution: Create a parallel branch for the two Update Row actions.
Does the solution meet the goal?
Options
Discussion
Option A here. Parallel branches let both Update Row actions run simultaneously, which is the best way to save time if they aren't linked. Some might pick B thinking about possible data locks, but with no dependencies mentioned A fits. Let me know if you disagree.
Its A. Since the two Update Row actions are independent, parallel branches will cut processing time instead of running sequentially.
A or B, had something like this in a mock and picked B thinking sequential updates might be faster for Dataverse.
Maybe B , because running them one after the other feels quicker in Dataverse for some reason.
B tbh, because I think running them in sequence is faster for Dataverse updates.
Be respectful. No spam.
