PowerApps RAW!

While recently walking a colleague through Power Automate, I was reminded of one of my long-standing frustrations: how difficult it is to copy expressions once they’ve been inserted into actions like a Compose , Filter Array , or For Each . For example: workflow()['tags']['environmentName'] item()?['logicalName'] Once fields are wrapped in certain expressions or are in certain actions, you can no longer open them in the expression popup—you or easily copy them out to reuse elsewhere. That makes it frustrating when you want to replicate logic in another flow or simply document what you’ve written. There is a copy action functionality but that copies the entire action and sometimes you just want a specific expression. The Workaround (Until Now) To deal with this, I used to: Add expressions to a comment or note in the action so I could reference them later Open DevTools and inspect the DOM to grab the full title attribute that contains the expression ...

Introduction Azure Data Factory (ADF) provides versatile ways to connect and interact with Dataverse. Understanding the connection options and configurations is crucial for securely and efficiently managing your data integration tasks. This guide walks through the primary methods for connecting Azure Data Factory to Dataverse, covering their benefits, best practices, and detailed walkthroughs to get you started. provides versatile ways to connect and interact with Dataverse. Understanding the connection options and configurations is crucial for securely and efficiently managing your data integration tasks. This guide walks through the primary methods for connecting Azure Data Factory to Dataverse, covering their benefits, best practices, and detailed walkthroughs to get you started. Disclaimer: These thoughts are my own and based on my personal experience. If you have different ideas or approaches, I’d love to hear them—I’m always eager to learn more from others in the community. C...

After installing a new hotend on my Creality CR-6 SE , I ran into a frustrating issue: when printing above 210°C, the hotend temperature would swing wildly—fluctuating by 5–10°C. The printer wouldn’t even start the print due to this instability. 🧠 The Fix: PID Tuning (Thanks to Community Firmware) This issue led me to discover PID tuning , a way to calibrate how the printer regulates temperature using smarter controls. Out of the box, Creality’s firmware doesn’t always support this—but I’m running the excellent CR-6 SE Community Firmware based on Marlin, which includes PID autotuning support via G-code commands. 🔧 How to Tune the Hotend Using OctoPrint Open the Terminal tab in OctoPrint. Turn on the cooling fan before tuning for accuracy, if you typically run the fan during your prints: M106 S255 Run PID autotune at a typical print temp (I used 215°C with 10 cycles): M303 E0 S215 C10 After sending the M303 command, you’ll see a series of output logs in the te...