Power Platform’s October and November 2026 updates add new Power Apps controls, Dataverse capabilities, AI features, desktop-flow options, and administration tools. These changes matter to Power Platform makers, automation developers, and tenant administrators deciding what to test or adopt. Ronan Vico Technologies demonstrates several of the updates in a YouTube video.
Power Apps is adding controls intended to simplify common app layouts. The modern Attachment control supports drag-and-drop and accepted file types, and it provides events for adding, removing, and undoing removal of files. Other highlighted controls include Avatar Group, Persona, Metric, and Card Gallery. Persona combines a user’s name, email, and picture in one control; Card Gallery offers a ready-made way to display clickable menu-style items.
The Data Grid adds numbered pagination. Makers can set the Pagination property to Number, allowing app users to see page numbers and browse records in blocks. Sorting can be delegated to Dataverse when the connected data source supports it. Delegation means the data operation is handled by the source rather than requiring the app to process all of the records locally.
Other changes span apps and automation. The Dataverse.Unmask function returns the unmasked value of a secured Dataverse column for a record. Model-driven apps can use a configurable prompt to generate a row summary. Generative pages can call Dataverse custom APIs and custom connectors, while Application Insights can be used to track generative-page performance and errors.
Power Automate Desktop updates include reusable flow templates and direct scheduling through a desktop-flow trigger. The scheduling feature is in preview. Power Platform administrators also get alert routing to connector destinations and scheduled exports of management data, which can support custom reporting.
These updates address several roles rather than a single audience. Canvas app makers can evaluate the new controls, pagination, and Dataverse function. Model-driven app makers can consider row summaries, while teams building generative pages can explore custom API and connector calls. Desktop automation developers may find templates useful for repeating a standard flow structure.
Administrators and platform managers should look at the alert-routing and data-export options. The video identifies the modern Attachment control, direct desktop-flow scheduling, and alert routing as preview features. Preview features should be tested before production use; the presenter specifically cautions against using the Attachment control and scheduled desktop-flow trigger in production. No licence requirements are given here, so teams should check the requirements shown for each feature in their own environment before planning deployment.
The updates also point to controls still on the way, including navigation, breadcrumb, facet, and accordion components. Treat those as forthcoming components, not as controls ready to use in an app today.
For the modern Attachment control, makers can set accepted file types and use file events to respond to user actions. The control’s drag-and-drop behavior can support a more direct upload experience. The Data Grid pagination option is configured on the control itself, and its delegated sorting depends on support from the connected source.
Generative pages can call Dataverse custom APIs for server-side business logic and can connect to custom connectors. Application Insights provides a way to inspect page views, performance, and errors. On the administration side, alert routing can send notifications to a connector destination, while scheduled management-data exports provide data for reporting.
Preview status is the clearest reason to proceed carefully: preview behavior can change, and the presenter advises against production use for the Attachment control and scheduled desktop-flow triggers. Validate a feature in a non-production environment before building a critical process around it. The presenter also describes alert routing as preview.
Delegated sorting depends on the data source, so makers should verify that the intended operation is supported rather than assuming every connected table will sort the same way. Similarly, Dataverse.Unmask concerns secured values; apps should only expose those values where the user and business process are meant to have access.
Some changes are improvements to existing experiences rather than entirely new workflows. SharePoint list forms customized with Power Apps remain the starting point for the form scenario discussed; the update is described as a layout improvement. The presenter could not test that form change in the environment used for the demonstration. Power Automate Desktop’s flowchart mode is another option, but the presenter preferred the standard studio after trying it. These are practical reasons to assess each feature against your app or automation before changing established designs.
It is identified as a public preview. The presenter advises against using it in production while it is in preview.
Set the Data Grid’s Pagination property to Number. The control then displays page numbers for browsing records in blocks.
A scheduled trigger can be created directly for a desktop flow. The feature is in preview, so test it before relying on it in production.
It takes a record and a column and returns the unmasked value of a secured Dataverse column for that record.