The learner must update the gallery's `OnSelect` to chain `Set(selectedTicket, ThisItem); Navigate(DetailScreen)`, then add a Label on `DetailScreen` with `Text = selectedTicket.Title`. The app must be saved. The screenshot MUST show ALL of the following: 1. **Gallery `OnSelect` chained formula**, formula bar (with gallery selected, `OnSelect` chosen) shows `Set(selectedTicket, ThisItem); Navigate(DetailScreen)` or equivalent. 2. **Label on `DetailScreen` bound to selectedTicket.Title**, when the Label is selected with `Text` in the property dropdown, formula bar shows `selectedTicket.Title` (or `selectedTicket.`). 3. **Back button on `DetailScreen`**, a Button or Icon control whose `OnSelect` is `Back()` (visible in Tree View or formula bar). 4. **App is saved**. 1. Multiple Labels on the Detail screen showing other selectedTicket columns (Status, Priority, AssignedTo). 2. The Back button is an arrow icon rather than a text Button. COPILOT TOLERANCE: If a Copilot sidebar panel is visible, evaluate only the visible portion of the canvas and the formula bar. Do NOT penalize for partial canvas occlusion by the Copilot panel. FORMULA BAR TOLERANCE: Power Apps renders formula text in a muted gray when the formula bar is not focused. If the property dropdown clearly shows the expected property name and the formula bar contains ANY text (even faint), treat the formula as present. Only fail if the formula bar is clearly blank or shows an obviously wrong value. ✅ PASS if the gallery sets `selectedTicket = ThisItem` AND the Detail screen has at least one Label bound to a `selectedTicket.` reference AND a Back control with `OnSelect = Back()`. ❌ FAIL if: - The gallery `OnSelect` doesn't include `Set(selectedTicket, ...)`, Set may use a different variable name, e.g. `Set(selRow, ThisItem)`, which is acceptable as long as the Label binding uses the same name - No Label on `DetailScreen` references the carried variable - The Label's `Text` is hardcoded text instead of a formula reference - No Back button/icon with `Back()` is visible on DetailScreen - The app is unsaved FEEDBACK GUIDELINES: - For PASS: Reinforce that `Set()` + `Navigate()` + `Back()` is the canonical navigation pattern: carry data forward, let the user return. - For FAIL with hardcoded Label: Show them that `selectedTicket.Title` is a formula reference, not a string, no quotes. - For FAIL without Back: Remind them that `Back()` gives a reliable return path without hardcoding a screen name.

Order the form lifecycle

Introduction to Power Apps

exercicio interativo prático