powerapp-canvas-controls

Use only tokens grounded from real Studio code-view output, such as `ModernTextInput@1.1.1` or `Classic/Button@2.2.0`. Generic Microsoft docs list names like `Button` or `Dropdown` that Studio never emits, and an ungrounded token fails the entire paste.

Modern controls are Fluent-based with per-control version suffixes and properties like `AccessibleLabel`, while classic controls use the `Classic/` prefix when a modern namesake exists. Modern versions cannot be inferred between controls, so author the classic control when a modern version is unknown.

A single wrong `Control:` token, `Variant:` value, or version suffix rejects the whole paste and returns only "it didn't work". Common causes include guessed modern versions, `AccessibleLabel` on classic controls, and nonexistent `Icon` enum members like `Icon.Back`.

ModernCombobox is seeded with `DefaultSelectedItems`, which must be a table of records from the Items source, and read via `.Selected.Value`. ModernDropdown is the opposite: its `Default` takes a plain value, so the two controls have different contracts despite similar names.

No, canvas text inputs have no keypress or Enter event, and `FocusOut` only fires when the control loses focus. The working options are `TriggerOutput: =TriggerOutput.Delayed` for debounced commits or an explicit button beside the input.

Use a Form with TypedDataCard children for straightforward CRUD over one list where SubmitForm and per-field validation suffice. Use separate Patch calls when you need guarded per-column writes, such as optional Choice, Person, or Managed Metadata columns that must not take down the whole record.