nerdexam
Microsoft

PL-500 · Question #171

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…

The correct answer is A. Yes. Configuring a UI element with multiple selectors or wildcard attributes allows the automation to locate the Submit button regardless of its dynamic ID or position across pages.

Question

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 Selector with recapture feature. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(38 responses)
  • A
    74% (28)
  • B
    26% (10)

Why each option

Configuring a UI element with multiple selectors or wildcard attributes allows the automation to locate the Submit button regardless of its dynamic ID or position across pages.

AYesCorrect

The proposed solution of configuring a UI element with flexible or wildcard-based selectors is valid because Power Automate Desktop allows UI elements to have multiple selectors that are tried in sequence, enabling the automation to match the button whether it appears as a Submit on page 2 or a Next button with a different ID on page 1. This approach handles dynamic element IDs without requiring separate conditional branches for each page state.

BNo

No explanation applicable - this is a Yes/No question and the solution as described is valid.

Concept tested: Dynamic UI element selector configuration for RPA

Source: https://learn.microsoft.com/en-us/power-automate/desktop-flows/ui-elements

Community Discussion

No community discussion yet for this question.

Full PL-500 Practice