Generative pages in Power Apps: building model-driven pages from a prompt

Generative pages in Power Apps

You describe a page, and the agent writes React code for both the UI and the logic behind it. Think of it as a custom page where you don't need Power Fx.

Two ways to build

• Browser — make.powerapps.com, conversational, no setup
• Code tools like GitHub Copilot CLI — Microsoft's recommended route: newer models, works worldwide, and one request can build multiple pages plus the Dataverse tables they need

Before you start

• Environment must be in the US, Great Britain, Australia or Singapore — otherwise the option won't appear and you'll need the code-tools route
• Browser prompts are US English only
• No extra AI or message credits needed

Build it

1. App designer → Add page → Generative page → Describe a page
2. Prompt with functional requirements first, then UX — name the columns
3. Add data → Add table — max six Dataverse tables
4. Optionally attach a sketch or wireframe
5. Generate page

The agent shows its plan first — requirements and assumptions — then writes, transpiles and renders. Check the assumptions before iterating. Fixing a bad plan later costs more.

Iterate

• Chat with the agent, or Edit on the Code tab — your edit saves as a new iteration
• Compare diffs iterations, but only from the second iteration in the current session
• The accessibility assistant scans each iteration; Auto fix hands violations back to the agent

Patterns worth knowing

• Inputs: pages accept recordId, entityName and data — say so in the prompt and the agent writes the init code
• Form embedding: form designer → Components → Display → Generative page. The record ID is passed in automatically, no config needed. This is the one I'd use most
• Navigation: open a page with Xrm.Navigation.navigateTo, passing parameters
• Data: everything goes through the dataApi object — read what it's calling
• Connectors (preview): create a connection, then a connection reference in the Default Solution, and it appears under Add data → Connectors. Not for production yet

ALM

• Solution-aware — add the app and sitemap; pages come across as UX Agent Project rows via the sitemap dependency
• Missing from the dependency check? Make a small sitemap change, republish, export again
• Only the first prompt and published code move to the target — the conversation stays behind. Write your intent down somewhere else

Limits

• 50,000-character prompt maximum
• One maker per page at a time
• Model-driven apps only
• Fixed list of supported column types — check before designing around anything unusual

My take

Microsoft is explicit: validating the generated code is your job. Check the dataApi calls, and make sure no rule that must hold has ended up in browser code. That belongs in a plugin.

Use it for dashboards, card galleries, Kanban boards and record panels on forms. Keep PCF for reusable field-bound controls and anything performance-sensitive.

Thanks for reading this article. Hope this Article will help you. Cheers!!!

Related Article: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/generative-pages

 #Dynamics365 #PowerPlatform #MicrosoftCopilot #DynamicsCRM #CopilotStudio #Dataverse #AIDeveloper #DynamicsAIEngineer #HireAIEngineer #AIEngineer #D365Consultant #CRMDeveloper #AIAgents #MSDyn365