{"posts":[{"id":"f7355748-ad2a-4fa8-8da8-ee1be63a243e","title":"Canvas Apps has a confirm dialog now!","slug":"canvas-apps-has-a-confirm-dialog-now","description":"A native confirmation dialog has been added to Canvas Apps. This is how to use it.","content":"Canvas Apps are still receiving new features, and this one is *potentially* a really good one. Prior to this, it was impossible to have a pop-up confirmation that was accessible, unless you used a [PCF component](https://learn.microsoft.com/en-us/power-apps/developer/component-framework/overview).\n\nWell, now we have this nice Fluent UI dialog:\n\n![Screenshot 2026-02-09 140851](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/content/1770646354935-9iwgma.png)\n\n## How to use\n\nA small amount of Power Fx is required to launch the dialog modal. At its most basic, this is all that's required.\n\n```c#\nConfirm(\"This is the brand new dialog\")\n```\n\nThat would usually be put in the OnSelect of a button. If you want to get more fancy with the details, there's an options record that you can provide to customise it a bit.\n\n```c#\nConfirm(\n \"This is the brand new dialog\",\n {\n Title: \"Are you sure you want to save?\",\n Subtitle: \"This will save your record\",\n ConfirmButton: \"Save\",\n CancelButton: \"Cancel\"\n }\n)\n```\n- **Title**: The biggest bit of text that's in bold\n- **Subtitle**: Slightly smaller and a bit grey, below the title. The body text goes below this and is even smaller and even more grey. A somewhat strange choice.\n- **ConfirmButton**: What the confirm (primary) button displays\n- **CancelButton**: What the cancel (secondary) button displays\n\nThe `Confirm()` function returns true if the user selects the confirm button, and false if they select the cancel button. So your formula is more likely to be something like this:\n\n```c#\nIf(\n // Call the dialog\n Confirm(\n \"This is the brand new dialog\",\n {\n Title: \"Are you sure you want to save?\",\n Subtitle: \"This will save your record\",\n ConfirmButton: \"Save\",\n CancelButton: \"Cancel\"\n }\n ),\n // True\n Notify(\"Your record was saved\"),\n // False\n Notify(\"Your record was NOT saved\")\n)\n\n```\n\n## Accessibility\n~~It's **not** accessible yet. It doesn't work properly with screen readers as it doesn't read out the dialog title. It only reads out the buttons, which is very confusing.~~\n\nUpdate: It appears to work properly with screen readers now! Nice!\n\nIn addition to that, the colours can't be changed for the buttons, so this is no use with destructive actions, like a deletion confirmation.\n\n## Final thoughts\n\nThis is potentially a great new feature for Canvas Apps, filling a gap that didn't have a low code solution, but it needs to be made accessible before it's adopted. That's one of the main reasons for having a native dialog like this in the first place.","contentHtml":"

Canvas Apps are still receiving new features, and this one is potentially a really good one. Prior to this, it was impossible to have a pop-up confirmation that was accessible, unless you used a PCF component.

Well, now we have this nice Fluent UI dialog:

$\"Screenshot$

How to use

A small amount of Power Fx is required to launch the dialog modal. At its most basic, this is all that's required.

Confirm(\"This is the brand new dialog\")

That would usually be put in the OnSelect of a button. If you want to get more fancy with the details, there's an options record that you can provide to customise it a bit.

Confirm(\n    \"This is the brand new dialog\",\n    {\n        Title: \"Are you sure you want to save?\",\n        Subtitle: \"This will save your record\",\n        ConfirmButton: \"Save\",\n        CancelButton: \"Cancel\"\n    }\n)

Title: The biggest bit of text that's in bold
Subtitle: Slightly smaller and a bit grey, below the title. The body text goes below this and is even smaller and even more grey. A somewhat strange choice.
ConfirmButton: What the confirm (primary) button displays
CancelButton: What the cancel (secondary) button displays

The Confirm() function returns true if the user selects the confirm button, and false if they select the cancel button. So your formula is more likely to be something like this:

If(\n    // Call the dialog\n    Confirm(\n        \"This is the brand new dialog\",\n        {\n            Title: \"Are you sure you want to save?\",\n            Subtitle: \"This will save your record\",\n            ConfirmButton: \"Save\",\n            CancelButton: \"Cancel\"\n        }\n    ),\n    // True\n    Notify(\"Your record was saved\"),\n    // False\n    Notify(\"Your record was NOT saved\")\n)\n

Accessibility

~~It's not accessible yet. It doesn't work properly with screen readers as it doesn't read out the dialog title. It only reads out the buttons, which is very confusing.~~

Update: It appears to work properly with screen readers now! Nice!

In addition to that, the colours can't be changed for the buttons, so this is no use with destructive actions, like a deletion confirmation.

Final thoughts

This is potentially a great new feature for Canvas Apps, filling a gap that didn't have a low code solution, but it needs to be made accessible before it's adopted. That's one of the main reasons for having a native dialog like this in the first place.

\n","image":"https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/featured/1770647214741-r2kg1.webp","ogimage":null,"datePublished":"2026-02-09T00:00:00+00:00","tags":["Power Apps","Power Fx"],"published":true,"readTimeMinutes":2,"authorId":"c2867773-6a1a-4b30-a003-cf813a4ac2a6","featured":false,"viewCount":0,"updatedAt":"2026-03-04T22:23:30.186446+00:00","deprecated":false,"showUpdated":true},{"id":"bd13dbdc-325f-4c03-935b-e94d7eddbd37","title":"Forget Canvas Apps: It's Time to Let Your Makers Write Code","slug":"forget-canvas-apps-it-s-time-to-let-your-makers-write-code","description":"AI has removed the skill barrier to writing code. It's time for organisations to let their Makers build Power Apps with Code Apps; not just developers.","content":"Microsoft just announced that Code Apps is now Generally Available, so I'm going to make an argument that might ruffle a few feathers in the Power Platform community: **your Makers should be using Code Apps, not just your developers.**\n\nI'm not talking about your developers picking up another tool. I'm talking about the same citizen developers who currently build Canvas Apps. The ones who aren't software engineers. The ones who've never written TypeScript in their lives.\n\nLet me explain why.\n\n## AI changed everything\n\nIf you'd asked me two years ago whether a non-developer could build a production-quality web app in React, I'd have said no. The learning curve was too steep. You needed to understand components, state management, build tooling, and a hundred other things that take years to internalise.\n\nThat's no longer true.\n\nWith modern AI assistants, anyone can build web applications using natural language. You describe what you want, AI writes the code. When you get stuck, you ask. When something breaks, you paste the error and ask for a fix. AI doesn't just write code - it explains, debugs, refactors, and teaches as you go.\n\nI've been vibe coding websites and web apps for a while now, and when Claude Opus 4.5 was released, I noticed a huge step change. Previously, working with AI felt like walking a dog on a lead; you had to guide it constantly or it would wander off. Now, it stays to heel. It builds excellent software without _needing_ technical instructions from me, although technical instructions can undoubtedly improve the output.\n\nThis isn't a small improvement. It's a fundamental shift in who can build software.\n\n## Canvas Apps are harder than they look\n\nHere's something the Power Platform community doesn't talk about enough: Canvas Apps are deceptively difficult.\n\nYes, they're easy to get started with. Drag a button onto a screen, connect to a data source, write a simple formula. You can build a basic app in an afternoon.\n\nBut try to build something more ambitious. Try to create a smooth, beautiful interface. Try to handle complex data operations. Try to refactor an app that's grown organically over six months. You'll quickly discover that the abstraction layer that made simple things easy makes difficult things incredibly difficult.\n\nCanvas Apps have a reputation for being slow and looking dated. That reputation exists for a reason.\n\nAnd here's the thing: if you push Canvas Apps far enough, you end up in pro-code territory anyway. You hit limitations that force you towards PCF components, Dataverse plug-ins, JavaScript web resources, etc. The ceiling is lower than it appears.\n\n## Code Apps massively raise the ceiling\n\nCode Apps let you build with React, Vue, or any other modern web framework while still benefiting from Power Platform's managed environment. You get:\n\n- Microsoft Entra authentication out of the box - no code required\n- Access to 1,500+ Power Platform connectors, callable directly from JavaScript\n- Hosting, deployment, and ALM handled for you\n- Your organisation's governance policies enforced automatically\n\nYou're writing real code, which means there's a really high ceiling. If you can describe what you want, AI can help you build it.\n\n## \"But what about the risks?\"\n\nI can already hear the objections. Let me address them.\n\n**\"Makers won't be able to maintain code they didn't write.\"**\n\nCanvas Apps are notoriously difficult to maintain. Refactoring is almost impossible. With Code Apps, maintenance becomes straightforward, because AI can read the code, understand it, and modify it. If a Maker built it with AI assistance, they can maintain it with AI assistance.\n\n**\"What about security?\"**\n\nAuthentication is included by default with Code Apps. No code needed. The apps are locked down with Content Security Policies, so Makers can't call external services unless explicitly permitted. Yes, they need to handle authorisation themselves, but that's true of Canvas Apps too.\n\n**\"Who's going to support these apps?\"**\n\nMakers should support their own creations. That's always been the model with citizen development, and it doesn't change here.\n\n**\"They'll need to install developer tools.\"**\n\nThey'll need VS Code (with extensions) and Node.js. That's it. Git isn't essential, and Microsoft is simplifying the CLI requirement. Compare that to learning Power Fx delegation rules and how to build responsive designs with Canvas App containers, and tell me which is the bigger barrier.\n\n## Code Apps are internal only, and that's the point\n\nOne detail worth highlighting: Code Apps are for internal line-of-business applications. They're not for external-facing apps.\n\nThis is precisely why it's safe to open them up to Makers. These are internal tools, built by people who understand the business problem, for colleagues they work with. The blast radius is contained. The governance is built in.\n\n## A note on licensing\n\nCode Apps require Power Apps Premium licences for end users. If your organisation isn't licensing users, I'd advise sticking to micro apps that aren't business-critical. You shouldn't be building anything important on Power Platform without Premium anyway, and if you're already paying for Premium, Code Apps are included.\n\n## What I'm suggesting\n\nI'm not suggesting you throw open the gates tomorrow, although I'm also not inherently against that. Here's what I'd recommend:\n\n1. **Start a pilot.** Identify your most technical Makers - the ones who've already pushed Canvas Apps to their limits.\n2. **Give them access to Code Apps.** Let them experiment. Let them build things. Don't overthink the use cases.\n3. **Watch what happens.** Analyse the results. See where they succeed, where they struggle, and what they produce.\n4. **Expand gradually.** As you see successes, and realise there's no harm in it, open access to more Makers.\n\nThe barrier to building software has collapsed. The question is whether your organisation will recognise that, or whether you'll keep your Makers confined to tools that were designed for a world that no longer exists.","contentHtml":"

Microsoft just announced that Code Apps is now Generally Available, so I'm going to make an argument that might ruffle a few feathers in the Power Platform community: your Makers should be using Code Apps, not just your developers.

I'm not talking about your developers picking up another tool. I'm talking about the same citizen developers who currently build Canvas Apps. The ones who aren't software engineers. The ones who've never written TypeScript in their lives.

Let me explain why.

AI changed everything

If you'd asked me two years ago whether a non-developer could build a production-quality web app in React, I'd have said no. The learning curve was too steep. You needed to understand components, state management, build tooling, and a hundred other things that take years to internalise.

That's no longer true.

With modern AI assistants, anyone can build web applications using natural language. You describe what you want, AI writes the code. When you get stuck, you ask. When something breaks, you paste the error and ask for a fix. AI doesn't just write code - it explains, debugs, refactors, and teaches as you go.

I've been vibe coding websites and web apps for a while now, and when Claude Opus 4.5 was released, I noticed a huge step change. Previously, working with AI felt like walking a dog on a lead; you had to guide it constantly or it would wander off. Now, it stays to heel. It builds excellent software without needing technical instructions from me, although technical instructions can undoubtedly improve the output.

This isn't a small improvement. It's a fundamental shift in who can build software.

Canvas Apps are harder than they look

Here's something the Power Platform community doesn't talk about enough: Canvas Apps are deceptively difficult.

Yes, they're easy to get started with. Drag a button onto a screen, connect to a data source, write a simple formula. You can build a basic app in an afternoon.

But try to build something more ambitious. Try to create a smooth, beautiful interface. Try to handle complex data operations. Try to refactor an app that's grown organically over six months. You'll quickly discover that the abstraction layer that made simple things easy makes difficult things incredibly difficult.

Canvas Apps have a reputation for being slow and looking dated. That reputation exists for a reason.

And here's the thing: if you push Canvas Apps far enough, you end up in pro-code territory anyway. You hit limitations that force you towards PCF components, Dataverse plug-ins, JavaScript web resources, etc. The ceiling is lower than it appears.

Code Apps massively raise the ceiling

Code Apps let you build with React, Vue, or any other modern web framework while still benefiting from Power Platform's managed environment. You get:

Microsoft Entra authentication out of the box - no code required
Access to 1,500+ Power Platform connectors, callable directly from JavaScript
Hosting, deployment, and ALM handled for you
Your organisation's governance policies enforced automatically

You're writing real code, which means there's a really high ceiling. If you can describe what you want, AI can help you build it.

\"But what about the risks?\"

I can already hear the objections. Let me address them.

\"Makers won't be able to maintain code they didn't write.\"

Canvas Apps are notoriously difficult to maintain. Refactoring is almost impossible. With Code Apps, maintenance becomes straightforward, because AI can read the code, understand it, and modify it. If a Maker built it with AI assistance, they can maintain it with AI assistance.

\"What about security?\"

Authentication is included by default with Code Apps. No code needed. The apps are locked down with Content Security Policies, so Makers can't call external services unless explicitly permitted. Yes, they need to handle authorisation themselves, but that's true of Canvas Apps too.

\"Who's going to support these apps?\"

Makers should support their own creations. That's always been the model with citizen development, and it doesn't change here.

\"They'll need to install developer tools.\"

They'll need VS Code (with extensions) and Node.js. That's it. Git isn't essential, and Microsoft is simplifying the CLI requirement. Compare that to learning Power Fx delegation rules and how to build responsive designs with Canvas App containers, and tell me which is the bigger barrier.

Code Apps are internal only, and that's the point

One detail worth highlighting: Code Apps are for internal line-of-business applications. They're not for external-facing apps.

This is precisely why it's safe to open them up to Makers. These are internal tools, built by people who understand the business problem, for colleagues they work with. The blast radius is contained. The governance is built in.

A note on licensing

Code Apps require Power Apps Premium licences for end users. If your organisation isn't licensing users, I'd advise sticking to micro apps that aren't business-critical. You shouldn't be building anything important on Power Platform without Premium anyway, and if you're already paying for Premium, Code Apps are included.

What I'm suggesting

I'm not suggesting you throw open the gates tomorrow, although I'm also not inherently against that. Here's what I'd recommend:

Start a pilot. Identify your most technical Makers - the ones who've already pushed Canvas Apps to their limits.
Give them access to Code Apps. Let them experiment. Let them build things. Don't overthink the use cases.
Watch what happens. Analyse the results. See where they succeed, where they struggle, and what they produce.
Expand gradually. As you see successes, and realise there's no harm in it, open access to more Makers.

The barrier to building software has collapsed. The question is whether your organisation will recognise that, or whether you'll keep your Makers confined to tools that were designed for a world that no longer exists.

\n","image":"https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/featured/1769907912866-ska6m.webp","ogimage":null,"datePublished":"2026-02-04T07:00:00+00:00","tags":["Power Apps"],"published":true,"readTimeMinutes":5,"authorId":"c2867773-6a1a-4b30-a003-cf813a4ac2a6","featured":false,"viewCount":0,"updatedAt":"2026-02-04T07:52:29.42778+00:00","deprecated":false,"showUpdated":false},{"id":"8f7b30a1-42be-4dd3-8a7b-11d1ad05a514","title":"Microsoft Learn Extractor Solution","slug":"microsoft-learn-extractor","description":"Have you ever wanted to be able to check your Makers knowledge? You can use this solution to automatically save users' completed modules, certifications and applied skills into Dataverse.","content":"\r\n## Table of contents\r\n\r\n## Why did I build this?\r\n\r\n1. **Governance**: You want to know that a Maker has learnt something before allowing them to use a tool or service, reducing risk to your organisation.\r\n2. **Skills database**: Tracking what your developers know.\r\n3. **Gamification**: Rewarding your Makers or Developers for learning. Everyone benefits.\r\n\r\n## How does someone use it?\r\n\r\nYou would go to [Microsoft Learn](https://learn.microsoft.com/en-us/) → **Profile** → **Transcript** and then copy your **Share link**. You would then go to the Learn Transcript Extractor App and paste in your share link, and then click on the **Send transcript** button. That's it!\r\n\r\n[![Microsoft Learn Extractor App form input](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/microsoft-learn-extractor/transcript-input.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/microsoft-learn-extractor/transcript-input.webp)\r\n\r\nThis triggers a flow that calls an undocumented API and extracts your Microsoft Learn Certifications, Completed Modules and Applied Skills and saves them to Dataverse.\r\n\r\n[![Microsoft Learn Extractor App results](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/microsoft-learn-extractor/learn-results.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/microsoft-learn-extractor/learn-results.webp)\r\n\r\n## Where can I get it?\r\n\r\nIt's open-source and available on GitHub: https://github.com/chumleesockson/Microsoft-Learn-Extractor-Solution\r\n\r\nYou can view more technical details there as well. If you just want the unmanaged solution, you can [download it using this link](https://github.com/chumleesockson/Microsoft-Learn-Extractor-Solution/blob/a7272aa812feb215724c1b2edab4b8bca31c2357/MicrosoftLearnExtractor_1_0_0_1_unmanaged.zip).\r\n\r\nYou will need to click on the 'Download raw file' button on that page.\r\n\r\n[![How to download a zip file from GitHub](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/microsoft-learn-extractor/download-from-github.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/microsoft-learn-extractor/download-from-github.webp)\r\n","image":"https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/microsoft-learn-extractor/microsoft-learn-extractor.webp","ogimage":"https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/microsoft-learn-extractor/microsoft-learn-extractor.webp","datePublished":"2025-11-26T00:00:00+00:00","tags":["Governance","Tools","Solutions"],"published":true,"readTimeMinutes":1,"authorId":null,"featured":false,"viewCount":0,"updatedAt":"2026-01-02T00:23:12.284073+00:00","deprecated":false,"showUpdated":false},{"id":"645e262c-c83c-43ab-a5cb-14204da22bce","title":"Environment variables in Canvas Apps","slug":"environment-variables-in-canvas-apps","description":"In this tutorial, we'll look at how you can use the values from Environment Variables in your Power Apps Canvas Apps.","content":"\r\n## Table of contents\r\n\r\n## What are Environment Variables?\r\n\r\nEnvironment variables are a way to store and manage configuration data that can be reused across apps, flows, and other components within a Dataverse environment. They help make your solutions more portable, maintainable, and scalable.\r\n\r\nAs an example, you might be storing your files in Azure Blob storage. You would want to have separate containers for development and production. You would then use an environment variable to tell the app which container to communicate with, depending on whether it's in development or production.\r\n\r\n## Licensing\r\n\r\nEnvironment variables are stored in Dataverse. There was talk about them potentially being available without needing to query Dataverse, but nothing has come to fruition from that. As such, directly accessing environment variables in your canvas app will force the designation to be **premium**.\r\n\r\nYou can use environment variables for your SharePoint sites and lists/libraries and maintain the standard license designation, as these are imported into your app with the Power Apps engine communicating on your behalf. When connecting to SharePoint choose **Advanced** to be able to use an environment variable.\r\n\r\n[![SharePoint environment variable](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/sharepoint-environment-variable.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/sharepoint-environment-variable.webp)\r\n\r\n## Creating an environment variable\r\n\r\nAs a best practice, always use solutions in Power Platform. From within your solution, you can create a new environment variable.\r\n\r\n[![Create environment variable from solution](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/create-environment-variable.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/create-environment-variable.webp)\r\n\r\nYou will be able to choose from multiple data types. What you choose will depend on what you want to achieve. If you're looking to connect to a SharePoint list or library, you'll want 2 environment variables. The first one will contain the SharePoint site, and the second one will contain the list or library.\r\n\r\n[![New environment variable form](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/create-environment-variable-form.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/create-environment-variable-form.webp)\r\n\r\n## Accessing environment variables from Power Apps\r\n\r\nIn order to directly call an environment variable, the first thing you will need to do is add the Dataverse tables to your app. They are called `Environment Variable Values` and `Environment Variable Definitions`. As you can probably gather, one table contains the definitions and the other contains the values.\r\n\r\n[![Environment variable Dataverse tables](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/environment-variables-tables.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/environment-variables-tables.webp)\r\n\r\nTo query your environment variable you will need to reference the **Schema Name**. You could reference it using the **Display Name**, but this might change, whereas the schema name will not.\r\n\r\n```js\r\nLookUp('Environment Variable Values', 'Environment Variable Definition'.'Schema Name' = \"csex_InDevelopment\").Value\r\n```\r\n\r\nYou can find the schema name by looking at the environment variable in your solution.\r\n\r\n[![Environment variable schema name](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/environment-variable-schema-name.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/environment-variable-schema-name.webp)\r\n\r\nThat's it! You're ready to start using Environment Variables in Canvas Apps. If you're regularly referencing an environment variable, I would recommend using a named formula for it, so that the Power Apps engine can decide when to call it and cache it.\r\n\r\n[![Environment variable called from a canvas app](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/final-result.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/final-result.webp)\r\n","image":"https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/environment-variables-in-canvas-apps.webp","ogimage":"https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/environment-variables-in-canvas-apps/environment-variables-in-canvas-apps.webp","datePublished":"2025-09-17T00:00:00+00:00","tags":["PowerApps","EnvironmentVariables"],"published":true,"readTimeMinutes":3,"authorId":null,"featured":false,"viewCount":0,"updatedAt":"2026-01-02T00:23:09.592636+00:00","deprecated":false,"showUpdated":false},{"id":"583c5853-13b4-4454-b0cb-670979c67adb","title":"YAML Generation in Power Apps","slug":"yaml-generation-in-power-apps","description":"Did you know that you can generate your canvas app controls using YAML? Here's a free solution to show you how.","content":"\r\n## Table of contents\r\n\r\n## What is YAML?\r\n\r\nYAML (which stands for YAML Ain't Markup Language) is a human-readable computer language that's most commonly used for configuration files.\r\nYou might have seen it if you've ever had to work on Azure DevOps pipelines for your Power Platform projects.\r\n\r\nIn the context of Power Apps, in basic terms, it's tells a canvas app what properties a control has, and looks something like this:\r\n[![YAML code of a canvas app control](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/yaml-generation-in-power-apps/yaml-in-canvas-apps.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/yaml-generation-in-power-apps/yaml-in-canvas-apps.webp)\r\nIt might look a bit daunting, but this is just a text control with a font colour, some Power Fx to figure out what to display, and the X and Y properties.\r\n\r\n## Why is this useful?\r\n\r\nThere are a few reasons why it's useful to be able to view, copy and paste YAML code. One of the major reasons is that it gives us the ability to generate YAML code to paste directly into our apps. This means that, instead of copying and pasting controls and then manually changing things, we can set some criteria and then generate everything already changed. For example, we could automatically rename our controls instead of having to do it manually.\r\n\r\nThe app I've created will add the following screen to your clipboard, and all you have to do is paste it into your app. How cool is that? I'd love to see what you come up with, using the same concept.\r\n\r\n[![YAML Generated Screen](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/yaml-generation-in-power-apps/yaml-generated-screen.webp)](https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/yaml-generation-in-power-apps/yaml-generated-screen.webp)\r\n\r\n## Download\r\n\r\n[YAML Generator Solution.zip](/posts/yaml-generation-in-power-apps/YAML%20Generator%20Solution.zip)\r\n\r\nJust import this solution in https://make.powerapps.com\r\n","image":"https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/yaml-generation-in-power-apps/yaml-generation-in-power-apps.webp","ogimage":"https://bbnqrewmvsuhiwkdzats.supabase.co/storage/v1/object/public/posts/yaml-generation-in-power-apps/yaml-generation-in-power-apps.webp","datePublished":"2025-03-02T00:00:00+00:00","tags":["PowerApps","YAML"],"published":true,"readTimeMinutes":2,"authorId":null,"featured":false,"viewCount":0,"updatedAt":"2026-01-02T00:23:19.174632+00:00","deprecated":false,"showUpdated":false}],"pagination":{"total_records":24,"current_page":1,"total_pages":5,"next_page":2,"prev_page":null}}