<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DynamicApps dev notes]]></title><description><![CDATA[DynamicApps dev notes]]></description><link>https://devnotes.dynamicapps.com</link><image><url>https://cdn.hashnode.com/res/hashnode/image/upload/v1745885822054/4358b98c-f017-46f5-ad03-fb3e0187af0a.jpeg</url><title>DynamicApps dev notes</title><link>https://devnotes.dynamicapps.com</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 24 Apr 2026 18:20:55 GMT</lastBuildDate><atom:link href="https://devnotes.dynamicapps.com/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Connection Reference errors after deployment]]></title><description><![CDATA[The safest way to use Connection References is to create them in the solution instead of inside Power Automate. You should then be able to select that connection reference from multiple solutions and flows.]]></description><link>https://devnotes.dynamicapps.com/connection-reference-errors-after-deployment</link><guid isPermaLink="true">https://devnotes.dynamicapps.com/connection-reference-errors-after-deployment</guid><category><![CDATA[Power Apps]]></category><category><![CDATA[power-automate]]></category><dc:creator><![CDATA[John Reilly]]></dc:creator><pubDate>Tue, 29 Apr 2025 00:21:42 GMT</pubDate><content:encoded><![CDATA[<p>The safest way to use Connection References is to create them in the solution instead of inside Power Automate. You should then be able to select that connection reference from multiple solutions and flows.</p>
]]></content:encoded></item><item><title><![CDATA[Power Automate flows are on in dev but turn off when deployed to production]]></title><description><![CDATA[This is actually a feature. Some flows are turned off by default when imported into the production environment. I’ve seen it happen with scheduled ones and ones that use external connectors. In any case, you just manually have to turn them on using P...]]></description><link>https://devnotes.dynamicapps.com/power-automate-flows-are-on-in-dev-but-turn-off-when-deployed-to-production</link><guid isPermaLink="true">https://devnotes.dynamicapps.com/power-automate-flows-are-on-in-dev-but-turn-off-when-deployed-to-production</guid><category><![CDATA[power-automate]]></category><category><![CDATA[Power Apps]]></category><category><![CDATA[Canvas PowerApps]]></category><dc:creator><![CDATA[John Reilly]]></dc:creator><pubDate>Tue, 29 Apr 2025 00:04:23 GMT</pubDate><content:encoded><![CDATA[<p>This is actually a feature. Some flows are turned off by default when imported into the production environment. I’ve seen it happen with scheduled ones and ones that use external connectors. In any case, you just manually have to turn them on using Power Automate in the production environment.</p>
]]></content:encoded></item></channel></rss>