PL-500 practice question 13 of 25

You are building an RPA for a web application. The automation populates and submits a form. You observe that the Submit button required for form…

Full set: 173 questions

Domain Develop solutions

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 on the review screen. You are building an RPA for a web application. The automation populates and submits a form. You observe that the Submit button required for form submission is sometimes located on the second page. When the Submit button is on the first page, it functions as a Next button with a different ID, depending on the selections made in the form. You need to configure a UI element for the Submit button that works in both scenarios. Solution: Use the Create a copy feature. Does the solution meet the goal?
Answer options
A: Yes
B: No Correct answer
Correct Answer:
B. No
Explanation

The "Create a copy" feature in Power Automate for desktop duplicates an existing UI element and its selectors. This results in two separate, identical UI elements. This approach does not solve the core problem, which requires a single UI element that can dynamically locate a button that has different properties (like its ID and location) in different scenarios. The correct method is to edit a single UI element and add multiple selectors to it. The automation will then try each selector in order until it finds a match, effectively handling the button's variable nature.

Why Incorrect

A. Yes: This is incorrect. Creating a copy does not merge the logic for finding the button in its different states; it merely creates a second, independent UI element definition.

References

1. Microsoft Learn. (2023). Manage UI elements. In the Power Automate documentation, under the section "UI element properties," it is explained that a UI element can have multiple selectors to handle dynamic content. The documentation states, "You can also create multiple selectors for a UI element. When this feature is used, the automation checks each selector in the defined order to locate the UI element." This confirms that adding multiple selectors to one element is the correct approach, not copying the element.

2. Microsoft Learn. (2023). Build a custom selector. This document details how to edit selectors for a UI element. The process involves modifying the selector builder for a single UI element to make it more robust or dynamic, which is the required technique for this scenario, rather than creating a copy. The "Create a copy" function is a management feature for duplication, not for creating dynamic selectors.

Scroll to Top