<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cascading Dropdowns on Chris Worth</title><link>https://chrisworth.dev/tags/cascading-dropdowns/</link><description>Recent content in Cascading Dropdowns on Chris Worth</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 21 Aug 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://chrisworth.dev/tags/cascading-dropdowns/index.xml" rel="self" type="application/rss+xml"/><item><title>Cascading Dropdowns in Canvas Apps: Building Dependent Pickers That Do Not Lie</title><link>https://chrisworth.dev/posts/power-apps-cascading-dropdowns-guide/</link><pubDate>Fri, 21 Aug 2026 09:00:00 -0500</pubDate><guid>https://chrisworth.dev/posts/power-apps-cascading-dropdowns-guide/</guid><description>&lt;p>A form went out with &lt;code>cboTeam&lt;/code> still holding a value from the Department the user had picked thirty seconds earlier. They changed Department, the Team combo box never cleared, and the record saved with a Team that did not belong to the new Department at all. Nobody caught it until someone tried to report against it later. The bug was not in the filter formula. It was in everything around the filter formula: what happens when the parent changes, and what happens while the form is still loading.&lt;/p></description></item></channel></rss>