powerapp-canvas-development

Add a new key under the Screens root section with Properties and a Children array of single-key control maps, then list the screen in EditorState.ScreensOrder. Children are ordered by z-index with the first item at the bottom and the last on top.

IfError requires all arguments to be type-compatible, so Patch returning a record and Notify returning a boolean conflict. Make every arm a Set call, stash FirstError.Message in a variable, and check it afterwards with a separate Notify.

SetFocus is categorically excluded for controls inside a Gallery, Edit form, Component, or Container, and the target must be on the same screen and not disabled. The restriction is documented and cannot be worked around in Power Fx; only a PCF code component can force focus.

No. The official schema declares Control as anything and Variant as any non-empty string, so invented control tokens validate perfectly but fail in Studio. A second token pass checks every control, variant, and Icon value against an allow-list from real Studio output.

A gallery's own OnSelect does not reliably fire when the click lands on a child control. Place a transparent full-template Classic/Button declared last in the row and put the action on its OnSelect instead.

Power Fx cannot name or call a behaviour block, so shared logic must live on a hidden control's OnSelect invoked with Select(), which works even when Visible is false. This avoids duplicating write logic that can silently diverge across copies.