<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Power Apps on Chris Worth</title><link>https://chrisworth.dev/skill-tag/power-apps/</link><description>Recent content in Power Apps on Chris Worth</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 07 Apr 2025 19:23:16 -0600</lastBuildDate><atom:link href="https://chrisworth.dev/skill-tag/power-apps/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering Variables in Power Apps: Context, Global, and Named Formulas</title><link>https://chrisworth.dev/posts/power-apps-variables-mastery-guide/</link><pubDate>Mon, 07 Apr 2025 19:23:16 -0600</pubDate><guid>https://chrisworth.dev/posts/power-apps-variables-mastery-guide/</guid><description>&lt;p>An order form app I built once stored the entire cart in a single global variable. Every screen shared it, so every screen re-rendered on every change, and the app slowed to a crawl on mobile as the order grew. Moving cart state to context variables scoped per screen, plus a collection for the final order items, fixed it. The wrong scope, not the wrong logic, is usually what&amp;rsquo;s actually killing performance.&lt;/p></description></item><item><title>Canvas Apps Offline: Using SaveData and LoadData When Connectivity Drops</title><link>https://chrisworth.dev/posts/power-apps-offline-capabilities-guide/</link><pubDate>Mon, 03 Mar 2025 10:00:00 -0600</pubDate><guid>https://chrisworth.dev/posts/power-apps-offline-capabilities-guide/</guid><description>&lt;p>Our field technicians were reverting to paper notes because their inspection app couldn&amp;rsquo;t retrieve equipment details in areas with no signal. After we added offline support with SaveData and LoadData, data entry errors dropped 70% and technicians got back nearly an hour a day they&amp;rsquo;d been losing to re-entering lost work. This article shows the same pattern: how to build a Canvas app that keeps working when the connection doesn&amp;rsquo;t, using the Power Apps functions &lt;strong>SaveData&lt;/strong> and &lt;strong>LoadData&lt;/strong>.&lt;/p></description></item><item><title>SharePoint Delegation in Canvas Apps: Mastering In-Out and Out-In Filtering Methods</title><link>https://chrisworth.dev/posts/sharepoint-list-delegation-power-apps-guide/</link><pubDate>Thu, 27 Feb 2025 14:30:00 -0600</pubDate><guid>https://chrisworth.dev/posts/sharepoint-list-delegation-power-apps-guide/</guid><description>&lt;p>The first time I hit this, my app was only searching the first 500 records of a 10,000-item SharePoint list. It missed the other 9,500 silently: no error, no warning the user would ever see, just wrong results. The cause was &lt;em>delegation&lt;/em>, and if you&amp;rsquo;ve built Canvas Apps against SharePoint lists you&amp;rsquo;ve likely already seen its warning icon (the blue underline or yellow triangle in the Power Apps studio) without knowing exactly what it was protecting you from.&lt;/p></description></item><item><title>Deep Linking in Power Apps Canvas Apps</title><link>https://chrisworth.dev/posts/power-apps-deep-linking-implementation-guide/</link><pubDate>Mon, 18 Nov 2024 08:32:39 -0600</pubDate><guid>https://chrisworth.dev/posts/power-apps-deep-linking-implementation-guide/</guid><description>&lt;p>We built QR codes that opened our equipment inspection app directly to a specific item&amp;rsquo;s details screen, cutting field technicians out of searching through hundreds of items. We used the same pattern for expense approvals: notification emails now link straight to the relevant approval screen, and approval time fell about 70% because managers stopped hunting for the right record. That&amp;rsquo;s what deep linking does: instead of routing users through multiple screens to reach one destination, a single link puts them there directly.&lt;/p></description></item></channel></rss>