<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ash @ Getsplash on Medium]]></title>
        <description><![CDATA[Stories by Ash @ Getsplash on Medium]]></description>
        <link>https://medium.com/@getsplashnz?source=rss-d3152b41f605------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*75zU7pEczIX0NDzN5LmISA.png</url>
            <title>Stories by Ash @ Getsplash on Medium</title>
            <link>https://medium.com/@getsplashnz?source=rss-d3152b41f605------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:18:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@getsplashnz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AgentCamp Christchurch 2026]]></title>
            <link>https://medium.com/@getsplashnz/agentcamp-christchurch-2026-4228048ade2a?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/4228048ade2a</guid>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Sat, 07 Mar 2026 03:15:10 GMT</pubDate>
            <atom:updated>2026-03-07T03:15:10.172Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>A few months ago I saw the call for speakers for AgentCamp Christchurch and also maybe had a wee nudge from boss man to submit a talk. My first thought was, I am not really an expert in agents, I have not done a whole lot with them yet. I have seen a lot, I know the language, I can talk about it, but what would I actually present?</blockquote><p>So I decided to just present on my own journey. The steps I have taken to understand the technology. Simple as that.</p><p>AgentCamp Christchurch was a one day event run by Steve and Bryn which had a wide range of speakers across two streams, one developer focused and one low code focused. It was an excellent day full of meeting people and seeing some really impressive presentations. You could really see the community growing and getting genuinely excited about agents and AI.</p><p><strong>What was my session about?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nXU8E8sQleHLXodmy6qz4g.png" /></figure><p>My mission was to present a crash course in the Agent Academy Recruit course, 9 missions in 45 minutes. Yes, it was a lot of content! But overall I was hoping to show what Copilot agents are, how they behave, and where they fit into day to day work.</p><p>I’ve seen some genuinely impressive demos. I’ve heard great stories about agents being used in real production environments. But if I’m being honest? I hadn’t really gotten my hands dirty myself. So when I came across Agent Academy, it felt like the perfect excuse to stop watching everyone else build things and do something myself. The course gave me a proper understanding of how agents are designed, how they behave, and how they could realistically fit into businesses.</p><p>It gave me a practical way to move from watching demos to building something real. The missions within the course cover things like why declarative agents are such a mindset shift, and how prompts, topics, and agent flows come together to support real work rather than just answer questions.</p><p>If you haven’t had a go at Agent Academy yet, I definitely recommend it. You can check it out with the link below:</p><p><a href="https://microsoft.github.io/agent-academy/">Copilot Studio Agent Academy | Agent Academy</a></p><p>The biggest thing I kept coming back to is that agents are powerful but they need to be designed with intention. Give Copilot a clear role, the right knowledge, and sensible boundaries and it can support people in a way that feels natural and genuinely useful.</p><p><strong>The one thing I wanted people to walk away with</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*DKhcsSr3p-u35uZ0cgFU4Q.png" /></figure><p>Apart from going and gaining the recruit badge yourself, build the skills, apply them in real scenarios, bring others along with you, and make sure the right governance is in place so everyone can explore confidently and safely.</p><p>And honestly, just enjoy it. This space is moving quickly and it is a great time to start learning by doing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4228048ade2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fixing Outdated SharePoint Term Labels in Power Automate]]></title>
            <link>https://medium.com/@getsplashnz/fixing-outdated-sharepoint-term-labels-in-power-automate-7eaea67f4d02?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eaea67f4d02</guid>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Wed, 04 Feb 2026 06:11:36 GMT</pubDate>
            <atom:updated>2026-02-04T06:11:36.300Z</atom:updated>
            <content:encoded><![CDATA[<p><em>To say 2026 has started with a bang is an understatement. I reckon I’ve been pushed out of my knowledge zone more times in the past three weeks than in the last six months of 2025! All jokes aside, I’ve been tackling some problems that I didn’t get a chance to look into last year, as well as some bugs that were definitely outside my comfort zone.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qvsPsWjHCT0g-3ASzVf7uQ.png" /></figure><p>One challenge I managed to crack was the ‘Stale Label’ problem, syncing taxonomy with the Term Store using Power Automate.</p><h4>The Problem</h4><p>We have a client who manages both documents and pages for their intranet in SharePoint, using managed metadata for labelling. Here’s where it gets interesting: when labels in the global term store get updated, the display labels in SharePoint update automatically, you can see the new values when you’re viewing pages or documents in the browser. Perfect, right?</p><p>Not quite.</p><p>The catch is that when Power Automate retrieves this data, it pulls the <em>original</em> label value (unless the page or document has been published since the change) that was set when the item was first created or last modified, not the current term store value. So while everything looks correct in SharePoint’s interface, your automated workflows and reports are working with stale data.</p><p>This creates a real headache for reporting. Management is making decisions based on outdated information because the labels in their reports don’t reflect what’s actually showing in SharePoint. I mentioned last year that 2026 would be the year to tidy our data and ensure everything is correct, clean, and up to date, and this was exhibit A of why that matters.</p><p><strong>Here’s a real example:</strong> In the Term Store, the value is ‘Administration and Management’, but when you use a Get items action in Power Automate, it returns ‘Administration’ which is the old label. My flow fixes this so the report correctly shows ‘Administration and Management’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*bUoOggXRyWQq01frjknAsw.png" /><figcaption>Capture of the Global Term Store (name has been changed)</figcaption></figure><p>Output from the Get Items action (out of date label):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/1*LpT20RozQw6KfeXhCCQwgw.png" /><figcaption>Extract from the get items property showing the old label.</figcaption></figure><p>Report with correct Term Store Label:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*DhyvlOOqaPXyaHHhsEKaEQ.png" /><figcaption>The report created from the flow solution with the correct new label.</figcaption></figure><h4>The Solution</h4><p>Use Power Automate to access the global term store values directly and update your reports with the correct, current labels. Simple concept, trickier execution.</p><p>I found a few articles referencing different pieces of what I was trying to accomplish, but nothing that tied it all together. So I thought I’d share how I achieved this end-to-end solution. The flow needed to handle both single-select and multi-select managed metadata columns, which added an extra layer of complexity.</p><p>The results? The flow processes approximately 6,000 pages in roughly 25 minutes. In the scheme of things, that’s pretty quick.</p><h4>Step by Step:</h4><p><strong>Trigger and Setup</strong><br>First things first, set up your trigger. I went with a manual trigger for testing, but you could use a recurrence schedule or even kick it off from Power Apps. Whatever works for your scenario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/221/1*utaMISvg3eP1tOxrlKz5LQ.png" /><figcaption>Manually trigger a flow</figcaption></figure><p><strong>Fetch Live Term Store Data</strong><br>Use the Send an HTTP request to SharePoint action to call the SharePoint Taxonomy API. This is crucial as you are bypassing the cached data and going straight to the source of truth in the Term Store.</p><p>I targeted the specific Term Set ID to keep things lean. No point pulling down the entire taxonomy when you only need a subset. I used the article below to pinpoint the correct IDs I needed for the term sets and terms.</p><p>Quick tip: store those IDs as variables or environment variables to make them easier to manage down the track. I’ve hard-coded them in my example to show how it works, but you’ll thank yourself later if you parameterise them properly.</p><p><a href="https://alexanderhenkel.dk/post/sharepoint-powerautomate-filter-termstore/">Filter and search the termstore in SharePoint with Power Automate</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9rA0PCdYw2uNR9tQ8fkEIQ.png" /><figcaption>Capture the ID values through api call</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*-Q7HhE3WUUcinOmP4rwRTA.png" /><figcaption>Send http request to the global term store</figcaption></figure><pre>Site Address: Environment Variable or site you want to connect to<br>Method: Get<br>URL: _api/v2.1/termStore/groups/{groupid}/sets/{setsid}/terms</pre><p><strong>Initialise Your “Lookup” Variable</strong><br>Add an Initialise Variable action and set it as an Array called varAllTerms. Point its value to the body/value from your HTTP request. Think of this as your live lookup table that the rest of the flow will reference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*2VQ0HI6h7r1y8PYb0CLI_g.png" /><figcaption>Initialise variable varAllTerms</figcaption></figure><pre>@{body(&#39;Send_an_HTTP_request_to_SharePoint&#39;)?[&#39;value&#39;]}</pre><blockquote><em>Duplicate the Send HTTP request and set varAllTerms (rename for each set or terms) for each term store sets that you will be using in the report.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/249/1*letF35MjI6NpGKb_tkchBg.png" /><figcaption>Duplicate actions for all Terms sets</figcaption></figure><p><strong>Prepare the Excel Collector</strong><br>Initialise another Array variable called varExcelRows. We are going to process data inside a loop, as we don&#39;t want to write to Excel inside that loop as that would be painfully slow. Instead, we&#39;ll collect each finished row here and dump them all into Excel in one go at the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*6xLp1xTzE6CSIoFCECS3Sg.png" /><figcaption>Initialise array for holding the table values.</figcaption></figure><p><strong>Get Your SharePoint Data</strong><br>Use Get items (or Get files if you’re working with Site Pages) to retrieve your list data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*6bTro3LeLAmqJ1_-J4hZ5Q.png" /><figcaption>Get the SharePoint Data</figcaption></figure><p><strong>Clean It Up (Optional but Worth It)</strong><br>Add a Select action to pick only the columns you actually need from SharePoint. This isn’t strictly necessary, but it speeds things up and makes the data cleaner before it hits the loop and I’m all about making the flow run faster when I’m dealing with thousands of items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*Fyf5p6z_B7cy5TajB1Gyxg.png" /><figcaption>Select to get the necessary columns</figcaption></figure><p>From:</p><pre><br> @{body(&#39;Get_items_-_get_Product_Marketing_Site_Pages&#39;)?[&#39;value&#39;]}</pre><p>Map:</p><pre>{<br> &quot;Product or Service&quot;: @{item()?[&#39;ProductService&#39;]},<br> &quot;ID&quot;: @{item()?[&#39;ID&#39;]},<br> &quot;Title&quot;: @{item()?[&#39;Title&#39;]},<br> &quot;Business Audience&quot;: @{item()?[&#39;BusinessAudience&#39;]}<br>}</pre><p>T<strong>he Core Loop: Transforming the Labels</strong><br>Add an Apply to each loop using the output from your Select action. This is where we swap out the old labels for the new ones:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*5DH6NlaFJp3ZKCiZbml5zw.png" /><figcaption>Apply to each from the select action</figcaption></figure><pre>@{body(&#39;Select_-_SharePoint_Data&#39;)}</pre><ul><li><strong>For multi-select columns:</strong> Add a Select action inside the loop. Use a filter expression to find the matching TermGuid in your varAllTerms variable and pull back the updated label.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*9GEF0jyKCM58EW9ynMQOnA.png" /><figcaption>Select for multi select columns</figcaption></figure><p>From:</p><pre>@{item()?[&#39;Product or Service&#39;]}</pre><p>Map:</p><pre>@{addProperty(<br>    removeProperty(item(), &#39;Label&#39;),<br>    &#39;Label&#39;,<br>    first(xpath(xml(json(concat(&#39;{&quot;Root&quot;:{&quot;Item&quot;:&#39;, string(variables(&#39;varAllTerms&#39;)), &#39;}}&#39;))), concat(&#39;//Item[id=&quot;&#39;, item()?[&#39;TermGuid&#39;], &#39;&quot;]/labels[isDefault=&quot;true&quot;]/name/text()&#39;)))<br>)}</pre><ul><li><strong>For single-select columns:</strong> I used an XPath expression directly when building the row, basically doing a VLOOKUP-style lookup for the term name, continue to the next step for this expression.</li></ul><p><strong>Construct the Final Row Object</strong><br>Add a Compose action called Compose_FinalRow. Here&#39;s where you construct a JSON object representing one row of your Excel table. For multi select columns I used the join() expression to turn those taxonomy arrays into nice, clean semicolon-separated strings (like &quot;App; Service; Technology&quot;).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*sHsukXWJAuD9LNCBhtskRA.png" /><figcaption>Compose all final data with expressions to manage multi and single select columns.</figcaption></figure><pre>{<br>  &quot;ID&quot;: @{item()?[&#39;ID&#39;]},<br>  &quot;Title&quot;: @{item()?[&#39;Title&#39;]},<br>  &quot;Topic&quot;: &quot;@{join(xpath(xml(json(concat(&#39;{&quot;Root&quot;:{&quot;Item&quot;:&#39;, string(body(&#39;Select_FixLabels&#39;)), &#39;}}&#39;))), &#39;/Root/Item/Label/text()&#39;), &#39;; &#39;)}&quot;,<br>  &quot;Business Audience&quot;: &quot;@{if(empty(item()?[&#39;Business Audience&#39;]?[&#39;TermGuid&#39;]), &#39;&#39;, first(xpath(xml(json(concat(&#39;{&quot;Root&quot;:{&quot;Item&quot;:&#39;, string(variables(&#39;varAllBusinessAreaTerms&#39;)), &#39;}}&#39;))), concat(&#39;//Item[id=&quot;&#39;, item()?[&#39;Business Audience&#39;]?[&#39;TermGuid&#39;], &#39;&quot;]/labels[isDefault=&quot;true&quot;]/name/text()&#39;))))}&quot;<br>}</pre><p>Here are the expressions used in the multi line and single line values:</p><p>Multi:</p><pre>join(xpath(xml(json(concat(&#39;{&quot;Root&quot;:{&quot;Item&quot;:&#39;, string(body(&#39;Select_FixLabels&#39;)), &#39;}}&#39;))), &#39;/Root/Item/Label/text()&#39;), &#39;; &#39;)</pre><p>Single Choice:</p><pre>if(empty(item()?[&#39;Business Audience&#39;]?[&#39;TermGuid&#39;]), &#39;&#39;, first(xpath(xml(json(concat(&#39;{&quot;Root&quot;:{&quot;Item&quot;:&#39;, string(variables(&#39;varAllBusinessAreaTerms&#39;)), &#39;}}&#39;))), concat(&#39;//Item[id=&quot;&#39;, item()?[&#39;Business Audience&#39;]?[&#39;TermGuid&#39;], &#39;&quot;]/labels[isDefault=&quot;true&quot;]/name/text()&#39;))))</pre><p><strong>Append to Collection</strong><br>Use Append to array variable to push the output from Compose_FinalRow into your varExcelRows variable. Each time the loop runs, you&#39;re adding another completed row to your collection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*psCuTgz0P8wGm6cM1sUUpA.png" /></figure><p><strong>Generate the Excel Report</strong><br>Once the loop finishes, add your array into a create csv table and then a create file action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*xvwenp_zfBMvDf9Qlo6_Fg.png" /><figcaption>Add a create CSV table using the varExcelRows as the input.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*tVFT_eLOwThryq4BOV6sxw.png" /><figcaption>Add a create file using the body of the create csv table.</figcaption></figure><p>Note: If you are using the create file action (and want to update the existing item) it is important to switch the content transfer toggle in settings to “Off” otherwise the flow will fail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*ZfRlwIjcbiFR0zArhG8Ezg.png" /><figcaption>Turn content transfer off to allow the file to be overridden if you want it to be updated each time you run the flow.</figcaption></figure><h4>Full Flow:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*dkmKVoVqsr62N9BQyrkRGw.png" /><figcaption>Capture of full flow solution.</figcaption></figure><h4>Why This Approach Works</h4><p><strong>It separates the doing from the getting.</strong> You grab all your data upfront, then transform it. No back-and-forth API calls slowing things down.</p><p><strong>It handles complexity without breaking a sweat.</strong> Single-select columns? Multi-select columns? The same loop handles both without needing separate branches or duplicated logic.</p><p><strong>It’s actually fast.</strong> By collecting everything into an array and writing to Excel once at the end, you avoid the bottleneck of trying to update Excel inside a loop. That’s what gets you from “this might take hours” to “done in 25 minutes.”</p><h4>The Bottom Line</h4><p>If you’re dealing with stale taxonomy labels with power automate, this approach will sort you out. It’s not complicated once you’ve got your head around it, and the payoff is worth it, you will have accurate data that actually reflects what’s in your Term Store.</p><p>Give it a go and let me know how you get on. And if you’ve tackled this problem differently, I’d love to hear how, I am always open to how others are solving the same challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eaea67f4d02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflecting on 2025: A Year of Growth and Collaboration]]></title>
            <link>https://medium.com/@getsplashnz/reflecting-on-2025-a-year-of-growth-and-collaboration-7e1b49feab10?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e1b49feab10</guid>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Thu, 18 Dec 2025 20:34:03 GMT</pubDate>
            <atom:updated>2025-12-18T20:34:03.688Z</atom:updated>
            <content:encoded><![CDATA[<p>Rather than writing a technology-focused end-of-year blog, I wanted to share a few highlights for me personally. This includes a lot about my team because honestly, I wouldn’t be able to do what I do without them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UpqxSdeG11jOMhTs.png" /></figure><h3>Our Focus and Achievements</h3><p>This year, we’ve worked on strengthening our Power Platform capabilities and delivering solutions that make a real difference. From streamlining processes to creating centralised systems for better visibility, the team has consistently shown creativity and resilience. We tackled how we want to approach governance, complex challenges, simplified workflows, and ensured that what we built was not just functional but impactful.</p><p>One project that really challenged me was one that incorporated PnP Modern Search. Adapting the layout using JSON and HTML to get a specific look and feel definitely rocked my boat a wee bit, but it was fun, challenging and rewarding. Now, it feels like a breeze, but at the time it stretched me in ways I didn’t expect.</p><h3>Team Dynamics and Growth</h3><p>One of the highlights for me was our end-of-year retro. It almost reflected the whole year, there were some laughs, some snarky comments, hard work and then serious conversations about what’s next. It reminded me how far we’ve come as a team. We’ve built a culture where learning from each other is the norm, and nearly every day someone had something new to share.</p><p>A moment that really surprised me this year was coming back from leave to only about five Teams messages and no urgent emails. That’s a true testament to the improvements we’ve been making in how we work. The second half of this year, especially after bringing on Rich Burdes, felt like a turning point, we cleared our backlog and started focusing on the work and improvements we want to be doing for our clients and as a team.</p><p><strong>Thank you to my Power Platform team</strong> for your hard work, creativity and resilience. You’ve made this year not only productive but enjoyable. And a big thanks to the wider <strong>M365 team</strong> for the collaboration we had across different projects working together has been energising and inspiring.</p><h3>Personal Reflections</h3><p>This year was definitely one of growth for me. Graduating from my psychology course was a proud moment, and attending team lead workshops gave me tools that spill over into leadership every day. Passing PL-400 was another milestone, but honestly, I feel richest in the knowledge I’ve gained from working alongside this team. Leading through change and uncertainty isn’t always easy, but seeing the team thrive has been the most rewarding part of my year.</p><h3>Special Thanks</h3><p>A huge thank you to Steve Knutson for his mentorship, guidance and for being an amazing person to work for. You’ve created such an awesome team, and I’m grateful every day for that.</p><p>And to Mel Ross (my work wife) thank you for listening to me vent, providing endless sarcastic comments, sharing the love for coffee, snacks and walks, understanding my eyebrows and just putting up with everything. You make the hard days easier and the good days even better.</p><h3>Looking Ahead</h3><p>Ignite left me excited for what’s next. Co-pilot agents will be a big growth area in 2026, and AI-driven automation is becoming central to modern workplaces. My advice? Focus on tidying up and governance now because new releases are only as good as the data going in. Understanding the difference between automation and AI will also be critical, because AI is not the answer to every business need. Sometimes automation is the smarter and simpler choice. I’m looking forward to continuing this journey with the same energy and commitment that defined this year.</p><h3>Closing Thoughts</h3><p>This year wasn’t just about technology, it was about people, resilience and shared success. I’m proud of what we’ve achieved and even more excited about what’s ahead. Here’s to 2026 and everything it brings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e1b49feab10" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Apps with Just Words: Trying Vibe Power Apps]]></title>
            <link>https://medium.com/@getsplashnz/lunchtime-play-testing-the-new-vibe-power-apps-portal-0a4032c5aa2f?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a4032c5aa2f</guid>
            <category><![CDATA[powerapps]]></category>
            <category><![CDATA[microsoft-ignite]]></category>
            <category><![CDATA[microsoft-power-apps]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Thu, 27 Nov 2025 05:12:07 GMT</pubDate>
            <atom:updated>2025-11-27T05:21:00.512Z</atom:updated>
            <content:encoded><![CDATA[<p><em>At Microsoft Ignite, one announcement that really caught my attention was the new Maker Portal at vibe.powerapps.com. So today during lunch, I decided to actually give it a go and see what all the buzz was about.</em></p><p><em>And honestly? It’s wild seeing where Power Apps is heading.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HWrwx-4mW0z28MWvDI-MMQ.png" /></figure><h4>What Is Vibe, Anyway?</h4><p>Vibe is an AI-native platform that builds solutions to business problems, including requirements, data, and full apps with generated code. Essentially, you describe what you want in plain language, and it generates a full React-based application with a Dataverse backend.</p><p>No drag-and-drop. No formulas. Just basically talking to the prompt. It even includes a prompt enhancer which improves your prompt…</p><h4>The Reality Check</h4><p>I’ll be honest, I think this <strong>very</strong> early preview territory and there are a lot of questions floating around the community right now, and for good reason.</p><p>But I wanted to show you where things are heading with this new Power App creation experience. Even in this rough state, you can see glimpses of something pretty cool.</p><h4>What I Built</h4><p>During my quick lunch break, I threw together a simple prompt to test it out, allow the tool to improve my prompt and then watch it work through the requirements, build the data model, and generate actual React code, even if I have no idea what React code actually looks like.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FoXVxn_pcX20%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DoXVxn_pcX20&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FoXVxn_pcX20%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c7ee06974797a2449d253526cf64799e/href">https://medium.com/media/c7ee06974797a2449d253526cf64799e/href</a></iframe><h4>The Important Bits to Know</h4><p>If you want to try this yourself, there are some requirements:</p><p>You must run Vibe in a non-default Power Platform environment, use a US region environment, be signed in from a US language browser, and have the System Customiser role or higher.</p><p>Currently, it only works with Dataverse and again there is quite a bit of work and questions to be answered for this to be in a production state.</p><h4>Where This Fits In</h4><p>I don’t see this replacing Canvas apps or Model-Driven apps but I do see it as another tool in the toolkit for businesses to embrace with their end users.</p><p>As I mentioned in my blog about Ignite this feels like Microsoft’s vision for empowering everyday workers to build solutions. Describe what you need, and let the platform handle the technical heavy lifting.</p><h4>Useful Links</h4><ul><li><a href="https://vibe.powerapps.com/">Vibe - Power Apps</a></li><li><a href="https://learn.microsoft.com/en-us/power-apps/vibe/overview">Overview of the new Power Apps experience - Power Apps</a></li></ul><h4>The Bottom Line</h4><p>Vibe isn’t ready for production yet, but it’s definitely worth exploring if you’re curious about where Power Apps is heading.</p><p><em>Check out the video to see what I built, and if you’ve had a chance to play with Vibe yourself, I’d love to hear what you think!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a4032c5aa2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Ignite 2025: The Future is Here (But Is Your Organisation Ready?)]]></title>
            <link>https://medium.com/@getsplashnz/microsoft-ignite-2025-the-future-is-here-but-is-your-organisation-ready-58a0c8e51261?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/58a0c8e51261</guid>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[powerplatform]]></category>
            <category><![CDATA[microsoft-ignite]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <category><![CDATA[microsoft-consulting]]></category>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Wed, 26 Nov 2025 00:17:16 GMT</pubDate>
            <atom:updated>2025-11-26T04:54:22.869Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Never did I think I would be attending Microsoft Ignite in person, but thanks to Stratos Technology Partners and some fortunate travel plans, I made it happen. And “WOW”, what an event.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ae4xBJhscKrsl0KmpHyJAA.jpeg" /></figure><h4>The Scale of It All</h4><p>When I try to put it into words, I just get WOW. The sheer scale compared to anything in New Zealand is insane. For the keynote, they pile you into an NBA stadium that holds up to 19,000 people, and it was near capacity. Sitting in that crowd, watching demos live on the key stage and screens, you feel the energy of where Microsoft is heading.</p><h4>The Words That Were Repetitive</h4><p>The keynote set the scene with words that kept appearing throughout the event: <strong>Work IQ, intelligence, trust, and human</strong>. But it was another term that really stuck with me: <strong>frontier firm</strong>.</p><p>Sure, it’s probably marketing speak, but here’s what I took from it: Microsoft is focusing on a bottom-up approach which means empowering everyday workers to build their own processes with tools that are governed and monitored. The idea? Your everyday worker is the expert in their area, so give them the tools to create solutions that improve their daily workload and let them focus on tasks that need more ‘human’ interaction.</p><p>From there, admins can monitor, govern, and potentially turn those solutions into enterprise agents.</p><p>It sounds brilliant in theory. But here’s where reality hits.</p><h4>The Gap Between Demo and Reality</h4><p>From the keynote demos to the breakout sessions, everything was slick. Polished. Impressive. But I kept asking myself the same question: <em>How do we implement this in existing tenants?</em></p><p>These demos are built in pristine environments designed to showcase the latest technology. In the real world? There’s a lot of work to be done. It highlighted something crucial for me: <strong>the importance of good data and having the right tools and governance in place</strong>.</p><p>While Microsoft emphasised security and governance for these new tools, I believe there’s quite a lot of tidy-up and preparation work organisations need to do to make the most of it all. The right controls are going to be critical.</p><h4>The Announcements That Got Me Excited</h4><p>There were 70 announcements over four days which was a lot to get your head around. But from a Power Platform tech lead perspective (and as a general M365 user), here are the ones I’m most excited about:</p><p><strong>Enterprise Agents and Copilot Enhancements</strong></p><ul><li><strong>Agent 365</strong>: A new control plane for enterprise agents with unique identities, permissions, and full activity trails</li><li><strong>Agent 365 MCP Servers</strong>: Custom agents in Copilot Studio can now access Outlook, SharePoint, OneDrive, Word, and Calendar</li><li><strong>Copilot Studio Evaluations</strong>: Test agents against real-world scenarios and track performance</li><li><strong>Computer Use in Copilot Studio</strong>: Agents can automate tasks across apps and websites via virtual machines (preview)</li></ul><p><strong>Power Platform Innovations</strong></p><ul><li><strong>New Maker Portal (vibe.powerapps.com)</strong>: A new type of Power App, React full-stack applications hosted in Power Apps with Dataverse backend</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TV-ulnMZMqi3PTj_eNRaVA.png" /><figcaption>Vibe Maker Portal Example</figcaption></figure><ul><li><strong>Power Apps + M365 Copilot Integration</strong>: Full Copilot capabilities including Researcher, Analyst Agents, and Code Interpreter for on-demand charts</li><li><strong>Power Apps MCP Server</strong>: Allows agents to use Power Apps features as skills (public preview next month)</li><li><strong>Workflows (Frontier)</strong>: New workflow capabilities as part of the Frontier programme for building automated processes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ZQS1C8iqwVENkpyB-3krQ.png" /><figcaption>Workflow (frontier) example</figcaption></figure><p><strong>Microsoft 365 Copilot Updates</strong></p><ul><li><strong>Work IQ</strong>: Embedded intelligence layer with inference and memory for context-aware responses</li><li><strong>Word, Excel, and PowerPoint Agents</strong>: Create documents, spreadsheets, and slide decks directly through M365 Copilot</li><li><strong>Sora 2 Integration</strong>: AI video creation coming to M365 Copilot</li></ul><p>See the full list of announcements in the Ignite Book of News below.</p><p><a href="https://news.microsoft.com/ignite-2025-book-of-news/">Microsoft Ignite 2025 Book of News</a></p><h4>My Survival Tips for Future Attendees</h4><p>If you’re considering Ignite in the future, here’s what I learned:</p><ul><li><strong>Attend the 101 session</strong> about how to get the best out of Microsoft Ignite, seriously, do this first</li><li><strong>Look at the schedule early</strong> to get into sessions and community events</li><li><strong>Plan for the venue logistics</strong> — I missed a few sessions because it took longer to walk between rooms and buildings than I expected</li><li><strong>Make connections</strong> — the person you stand next to in the queue for a photo or lunch could become a valuable contact. This was one of the key highlights for me, was the people I met and have stayed in contact with since the event.</li><li><strong>Take breaks</strong> — during the 101 session, they mentioned using the Hub to regulate and take breaks. I thought “why would I need that?” Well, after the first day and 17,000 steps, I certainly learned why. It’s overwhelming and tiring.</li></ul><h4>What I’m Most Proud Of</h4><p>Two things stand out:</p><p><strong>Agreeing to do an interview.</strong> For those who know me, I’m quite a quiet person. Agreeing to do an on-the-spot interview was definitely out of my comfort zone, but I enjoyed it!</p><p><a href="https://www.linkedin.com/posts/teamviewer_teamviewer-microsoftignite-digitalfriction-activity-7396977312598040577-uevM?utm_source=social_share_send&amp;utm_medium=android_app&amp;rcm=ACoAAByULiMBQg-2CYu5eeyv_HZaelF4-9H9yh0&amp;utm_campaign=copy_link">#teamviewer #microsoftignite #digitalfriction | TeamViewer</a></p><p><strong>Being a woman at an event predominantly attended by males.</strong> It’s something I noticed, and something I’m proud to represent.</p><h4>The Session That Stuck With Me</h4><p>One of my favorite sessions was <strong>‘Building agents with Copilot Studio and Microsoft Foundry’</strong>. The presenters were great and very engaging, but more importantly, they tackled an issue we’ve all seen with Microsoft tools at some point in time which is different tools not talking to each other.</p><p>They discussed how Copilot Studio and Microsoft Foundry have been built on the same framework and language. For me, this lessens the boundaries of doing more hybrid projects with developers. Either tool can be used to create agents based on experience and preference. That kind of flexibility and interoperability? That’s what real-world implementation needs.</p><p><a href="https://ignite.microsoft.com/en-US/sessions/BRK314">Building agents with Copilot Studio and Microsoft Foundry</a></p><h4><strong>Other Sessions Worth a Watch</strong></h4><p>Below this blog I have listed some of the sessions I attended or have watched since the event.</p><h4>The Bottom Line</h4><p>The future of work isn’t just about AI doing tasks for us or taking our jobs it’s about empowering everyday workers to build their own intelligent solutions. But here’s where I think the catch is: <strong>it only works if organisations do the groundwork first</strong>.</p><p>The technology is there. It’s impressive. It’s ready (or almost ready). But are your data foundations solid? Is your governance in place? Do you have the right controls?</p><p>Microsoft Ignite showed me what’s possible and I have been all over the place with ideas since the event. Now the real work begins and I’ll be sharing more videos on playing around with the latest updates in my upcoming posts.</p><h4>Want to Hear More?</h4><p>Check out this webinar where I was interviewed about my experience at Ignite.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Flg3I8QAsZYw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dlg3I8QAsZYw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Flg3I8QAsZYw%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f6adfbfb960e652976d3f6d7f5632987/href">https://medium.com/media/f6adfbfb960e652976d3f6d7f5632987/href</a></iframe><p><em>Stay tuned for deep dives into the Power Platform announcements and practical implementation strategies.</em></p><p><strong>Links to sessions:</strong></p><ul><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK322">The future of Power Platform: AI-powered and enterprise-grade</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/THRSP897">Transform business workflows with Microsoft Copilot and agents</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK313">What&#39;s new in Copilot Studio and roadmap</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK309">Best practices to secure and govern low code agents, apps, and flows</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK320">Automation in Copilot Studio: Agent flows and computer use</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK275">Create apps with M365 Copilot and App Builder</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK288">SharePoint: The Knowledge Platform for Copilot and Agents</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK317">Building Multi-Agent systems with MCP and Copilot Studio</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK324">Power Platform: Innovation across apps, automation, and portals</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK323">Power Apps: Reimagine the human-agent collaboration</a></li><li><a href="https://ignite.microsoft.com/en-US/sessions/BRK321">From flows to agents: Modernizing with Copilot Studio + Power Automate</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58a0c8e51261" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Webinar: Build a flow anyone can manage.]]></title>
            <link>https://medium.com/@getsplashnz/webinar-build-a-flow-anyone-can-manage-fc535447cc2d?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc535447cc2d</guid>
            <category><![CDATA[power-automate-developer]]></category>
            <category><![CDATA[microsoft-power-automate]]></category>
            <category><![CDATA[power-automate]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Sun, 28 Sep 2025 19:21:00 GMT</pubDate>
            <atom:updated>2025-09-28T19:21:00.403Z</atom:updated>
            <content:encoded><![CDATA[<p>My amazing work colleague and I presented at our companies monthly webinar on building a workflow that anyone can manage. In the webinar, we look at building a very basic flow which may cause some issues down the track and then we spend some time updating this to make it an easy to manage, efficient and scalable flow. There was a lot to cover in 45 minutes so we tried to show as much as possible without going overboard.</p><p><a href="https://www.youtube.com/watch?v=9T2N6ED2G4k">Build a Flow anyone can manage — YouTube</a></p><p>This follows on from my blog which explains what we cover in a bit more detail.</p><p><a href="https://medium.com/@getsplashnz/building-a-flow-anyone-can-manage-workflow-best-practice-c3b0ac1259ea">Building a Flow Anyone Can Manage: Workflow Best Practice</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc535447cc2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Solutions and Environment Variables]]></title>
            <link>https://medium.com/@getsplashnz/using-solutions-and-environment-variables-c61955e9cda2?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/c61955e9cda2</guid>
            <category><![CDATA[power-apps-developer]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <category><![CDATA[power-automate-developer]]></category>
            <category><![CDATA[microsoft-power-apps]]></category>
            <category><![CDATA[microsoft-power-automate]]></category>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Wed, 03 Sep 2025 00:31:05 GMT</pubDate>
            <atom:updated>2025-09-03T00:38:44.381Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I’ll be honest with you, Solutions and Environment Variables were one of those Power Platform concepts I kept hearing about but avoided because I thought they’d be way too complicated for where I was in my career. Now that I’ve actually started using them? I can’t imagine going back to the old way of doing things.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aT7WVMdlNu27wgvPGpBtwA.jpeg" /></figure><p>Hopefully this guide will help you understand what they are and how to use them and maybe you’ll end up like me, wondering why you waited so long to start using them.</p><h4>What are Solutions and Environment Variables?</h4><p>A solution is basically a package that lets you bundle all your processes together. It enables proper Application Lifecycle Management in Power Platform and gives you consistency when building, makes everything easier to manage, and simplifies working with team members across different tenants or environments.</p><p>Let me give you an analogy that really helped me understand these concepts.</p><p>Picture yourself packing for a holiday (very topical for me at the moment!). You grab a suitcase (that’s your Solution) and start filling it with everything you need: clothes, toiletries, chargers, travel documents. But here’s the twist: instead of packing your actual passport or shoes, you put in two notes. One says “travel documents” and another says “shoes.” These notes are your Environment Variables, they’re like placeholders that tell you where to find the real thing when you actually need it</p><p><strong>Now, why is this important?</strong></p><p>Let’s say you’re going on multiple trips within a couple of months, one to the beach, one to the mountains, and one overseas. You don’t want to completely repack your suitcase from scratch each time, right? Instead, you reuse the same suitcase (your Solution) and just update those notes (your Environment Variables) based on where you’re headed.</p><p>For the beach trip, your “shoes” note might point to your jandals. For the mountains, it could point to your hiking boots. And for that overseas trip, your “travel documents” note might point to the drawer where you keep your passport instead of just your regular ID.</p><p>This flexibility means you’re not constantly rebuilding or repacking everything, you’re just updating the references. In Power Platform, this is exactly what Environment Variables do for you. They let you change values in your processes without having to rewrite or edit your actual flows or PowerApps every single time.</p><p>Plus, it keeps everything neatly organised so you can move, share, collaborate, and manage your work without losing your mind.</p><h4>The Real-World Problem This Solves<strong>:</strong></h4><p>Here’s a scenario that’ll probably sound familiar: You’ve built a flow that sends an email to the accounts team whenever a new invoice hits a specific mailbox. If you hard-code that finance team email directly into your development flow, guess what happens? They’re going to get bombarded with emails every single time you test your solution while you’re building it. Not exactly the best way to make friends with the finance team.</p><p>Instead, you use a text environment variable to hold that email address value. In development, you set it to your own email address so you can verify the flow works as expected without annoying anyone. When you move this into production, you simply update the environment variable to use the actual finance team email, and all live notifications go to the right place.</p><p>Even better, if that notification ever needs to go to someone different, you only need to update the environment variable in one spot rather than opening every single flow that references that email and manually updating each action. Trust me, your future self will thank you for this approach.</p><p>When you use an Environment Variable for something like an email address in Power Automate, you can update the value in one place, and all your flows that reference it will automatically use the new value. And by putting your flow inside a Solution, you can move it between environments, share it with others, and keep everything organised, just like reusing that trusty suitcase for different trips.</p><h4>When Should You Use Environment Variables?</h4><p>Environment variables work best for values that might change or could differ between environments, or things that might evolve as your process grows. As you build more solutions and gain experience, you’ll develop a feel for what makes sense and what doesn’t. Here are some examples of what I regularly use environment variables for:</p><ul><li>Email addresses for notifications</li><li>SharePoint site URLs</li><li>API endpoints</li><li>Internal List Names</li><li>Time delays</li><li>Database connection strings</li><li>File paths or folder locations</li></ul><h4>A Quick Tip That’ll Save You Headaches Later</h4><p>Here’s something important to keep in mind: the environment variable you create exists for the entire environment, not just the specific solution you add it to. This means you could end up with a lot of environment variables floating around. It’s crucial to name them consistently using wording that makes them easy to find but descriptive enough for all developers working in that environment.</p><p>Honestly, keeping a master list of your environment variables is incredibly useful, it helps you see what’s being used where and for what connections. Your team will appreciate the organisation, and you’ll save yourself from creating duplicate variables or losing track of what does what.</p><h4>How to Create a Solution and Environment Variable</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAtO3qfD8yeg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAtO3qfD8yeg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FAtO3qfD8yeg%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dc2af0bd40616b2c50324232f131074f/href">https://medium.com/media/dc2af0bd40616b2c50324232f131074f/href</a></iframe><p><strong>Step 1: Create a Solution</strong></p><ul><li>Go to Power Apps or Power Automate in the environment which you would like to create your solution (this would normally be in a development or sandbox environment).</li><li>In the left-hand menu, click on Solutions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9n1-e4hOXpJiCNetgFdPQ.png" /></figure><ul><li>Click + New Solution.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*nCyHO5-18-MNovFlAKoxwQ.png" /></figure><ul><li>Give it a name (e.g., “Holiday Planner”), choose a publisher (I would always recommend using a publisher that distinguhes that you have created this solution and avoid the default), and click Create.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/489/1*WsOrsyVl0Bzo1seNUvOD7g.png" /></figure><p><strong>Step 2: Add a Flow to Your Solution</strong></p><ul><li>Open your new solution.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GoYJs2U7Fzhuwg-guLU7Hw.png" /></figure><ul><li>Click + New and choose Flow.</li><li>Build your flow as usual.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*royOwBrrOM-eC_ooPKUB1A.png" /></figure><p><strong>Step 3: Create an Environment Variable</strong></p><ul><li>Inside your solution, click + New and choose Environment Variable.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vbm79wM-0HJx3VxOuriiUQ.png" /></figure><ul><li>Give it a name (e.g., “List — Holiday Planner — SharePoint Data Source Connection), choose the data type (like Data source and then SharePoint), and select the list you would like to connect the environment variable to.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*2vqS62c4o6GPnPh-4COQ9g.png" /></figure><ul><li>Select save.</li></ul><p><strong>Step 4: Use the Environment Variable in Your Flow</strong></p><ul><li>In your flow, when you need to use the value (like the SharePoint List connection), choose Environment Variable from the dynamic content list.</li><li>Select the variable you created.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sak2X7dqi7SD3W9yVqRv0g.png" /><figcaption>For a data source environment variable select ‘Enter custom value’</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y1P8YkYkv-L3dLBvPJ4vDQ.png" /><figcaption>Select the environment variable from the dynamic content</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*1y6AO46MAvYH0K47uND_YQ.png" /><figcaption>The action is now using environment variables to connect to a SharePoint List</figcaption></figure><h4>Final Thoughts</h4><p>Solutions and Environment Variables might sound intimidating at first, but they’re just tools to help you stay organised and flexible. Once you start using them, you’ll wonder how you ever managed without them.</p><p>Just like packing smarter for your holidays, using these tools means less stress, fewer mistakes, and more time to focus on what really matters which is building great automations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c61955e9cda2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Power Platform Environments Disappear: Lessons Learned & How to Prevent It]]></title>
            <link>https://medium.com/@getsplashnz/when-power-platform-environments-disappear-lessons-learned-how-to-prevent-it-7d80eb0c3ce4?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d80eb0c3ce4</guid>
            <category><![CDATA[powerplatform]]></category>
            <category><![CDATA[power-platform-training]]></category>
            <category><![CDATA[power-platform-developers]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Fri, 01 Aug 2025 01:20:06 GMT</pubDate>
            <atom:updated>2025-08-01T01:36:08.235Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article is being updated as we uncover more insights and best practices around Power Platform environment management. Stay tuned for refinements.</em></p><p>Recently, we faced a situation that could have derailed our development efforts where a Power Platform environment vanished, and it was no longer recoverable. While production remained unaffected, the loss of our developer environment meant we could no longer modify unmanaged solutions. Here’s what happened, why it matters, and how you can avoid the same fate.</p><h4><strong>What Happened?</strong></h4><p>In 2025, Microsoft introduced automatic environment clean-up policies to optimise system performance and resource usage. These policies target inactive environments, and unfortunately, one of our developer environments was deleted due to inactivity.</p><h4>Why This Was a Problem</h4><ul><li>The developer environment was our main workspace for building and updating production solutions.</li><li>Although production apps and flows remained intact, we lost access to unmanaged solutions, halting development and requiring a rebuild from scratch.</li></ul><h4>Microsoft’s New Environment Deletion Policies</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6SZEADSpEpNZ4kfE0xYPqw.png" /></figure><p>More information can be found in the Microsoft Documentation link below.</p><p><a href="https://learn.microsoft.com/en-us/power-platform/admin/automatic-environment-cleanup">Automatic deletion of Power Platform environments - Power Platform</a></p><blockquote><em>⚠️ Note: Deletion warnings are sent to the environment creator which is often a service account that may not be actively monitored.</em></blockquote><h4>What We Did to Recover</h4><p>Thankfully, we had pipelines in place that stored the latest unmanaged solution artifacts. Here’s how we rebuilt:</p><ol><li>Created a new Sandbox environment</li><li>Exported solutions from pipeline artifacts</li><li>Uploaded unmanaged solution ZIP files</li><li>Recreated environment variables and connections manually</li></ol><blockquote><em>Without pipelines, recovery would have been nearly impossible as you can’t export managed solutions from production.</em></blockquote><h4>How to Prevent This in the Future</h4><p>Here are some proactive steps to protect your environments:</p><ol><li><strong>Implement a heartbeat flow</strong></li></ol><p>Set up a lightweight flow that runs periodically to keep environments active and prevent deletion</p><p><strong>2. Store latest versions of Unmanaged Solution</strong></p><p>After each release, download and store the latest unmanaged solution in a central repository.</p><p><strong>3. Record Environment Variables</strong></p><p>Document all environment variables and connections used in dev and prod to simplify recovery and reconfiguration.</p><p><strong>4. Assign a Dedicated Environment Manager</strong></p><p>Ensure someone is responsible for monitoring environment health and receiving deletion alerts, especially if environments are created using service accounts.</p><p><strong>5. Monitor Environment Activity</strong></p><p>Use the Power Platform Admin Centre to check last activity dates and identify environments at risk of deletion.</p><p><strong>6. Review Licensing and Capacity</strong></p><p>Ensure your environments are tied to active subscriptions and have sufficient capacity to avoid deletion due to license expiration.</p><p><strong>7. Leverage the Power Platform CoE Starter Kit</strong></p><p>Use the CoE Starter Kit to gain visibility into environment usage, automate governance (like owner assignment and inactivity alerts), and track environment health. It’s a powerful tool for proactively managing and protecting your environments.</p><h4>Risks of Inaction</h4><ul><li>Permanent loss of apps, flows, and data</li><li>Unexpected downtime or project delays</li><li>Limited recovery options after deletion</li></ul><h4>Conclusion: What Are You Doing?</h4><p>This event prompted us to rethink how we safeguard our development environments, and we’re still refining our approach. I’d love to hear from others in the Power Platform community:</p><ul><li>Have you faced similar issues?</li><li>What strategies or tools are you using to safeguard your environments?</li><li>Any tips for managing environment lifecycle more effectively?</li></ul><p>Drop your thoughts in the comments or reach out — let’s learn from each other and build more resilient Power Platform practices.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d80eb0c3ce4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Recover a Deleted Power App Using PowerShell]]></title>
            <link>https://medium.com/@getsplashnz/how-to-recover-a-deleted-power-app-using-powershell-f8c1a51bc327?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8c1a51bc327</guid>
            <category><![CDATA[microsoft-power-platform]]></category>
            <category><![CDATA[microsoft-powerapps]]></category>
            <category><![CDATA[powerapps]]></category>
            <category><![CDATA[microsoft-power-apps]]></category>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Wed, 30 Jul 2025 03:24:47 GMT</pubDate>
            <atom:updated>2025-07-30T03:24:47.570Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Accidentally deleting a Power App can feel like a disaster especially if it’s a critical business application. But the good news is, if you’re working in a Microsoft Power Platform environment, there’s a way to recover deleted apps using PowerShell. This guide walks you through the process, explains why it matters, and outlines what permissions you’ll need to get it done.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1RbCMrCgh1XkHEJDNHKjA.png" /></figure><p>I recently had a client reach out in a bit of a panic as they had accidentally deleted a Power App that was being used daily to support key business processes. Naturally, they wanted to know if it could be restored. That request sent me down the path of learning how to recover deleted Power Apps using PowerShell, and what I discovered turned out to be incredibly useful, not just for them, but for anyone working with Power Platform.</p><h4>Real-World Scenario: From Hero to Heart-Stopping Moment</h4><p>Jamie is a passionate low-code developer just beginning their journey with Power Apps. Driven by curiosity and a desire to solve real business problems, Jamie builds a simple app to streamline customer onboarding. What starts as a prototype quickly becomes a hit with the business. It’s fast, intuitive, and solves a problem they’ve struggled with for months.</p><p>This is the dream of citizen development: a business user stepping up, creating a solution that works, and making a real impact. But with great success comes great responsibility, and Jamie, still new to the platform, hasn’t yet learned the ropes of Application Lifecycle Management (ALM).</p><p>There’s no source control. No backup strategy. No deployment pipeline. The app lives entirely in the default environment, and it’s now powering a core business process.</p><p>Then, one afternoon, while tidying up old apps in the Power Apps portal, Jamie clicks the options menu and without realising hits Delete on the production app.</p><p>Suddenly, the app is gone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OnyzIkXKleJSMW5YouXmDw.png" /><figcaption>Successfully deleted app</figcaption></figure><p>The sales team is locked out. Onboarding grinds to a halt. Jamie’s heart sinks. <em>Can I get it back?</em></p><h4>Why Recovering Deleted Power Apps Matters</h4><p>In Jamie’s case, the accidental deletion of a production app wasn’t just a technical hiccup, it was a business-critical event. The app was powering customer onboarding, and its sudden disappearance brought operations to a standstill.</p><p>This scenario highlights a broader truth that Power Apps often serve as the front-end for essential business processes, from intake forms and approval workflows to dashboards and automation. When one is deleted, the consequences can be severe:</p><ul><li>Disruption to operations</li><li>Loss of data or functionality</li><li>Time-consuming rebuilds and recovery efforts</li></ul><p>Having a recovery strategy in place isn’t just a nice thing to have it’s a safeguard for business continuity. And in environments where low-code experimentation is encouraged, accidental deletions are more common than you’d think.</p><h4>Prerequisites &amp; Permissions</h4><p>Before you dive into recovery, make sure you have the right access and tools. Here’s what you’ll need:</p><ul><li>Power Platform Admin or Environment Admin permissions</li><li>Access to PowerShell with the following modules installed:</li></ul><p>Microsoft.PowerApps.Administration.PowerShell</p><p>Microsoft.PowerApps.PowerShell</p><p>These permissions and modules are essential to locate and restore the app using PowerShell commands. Without them, recovery won’t be possible.</p><h4>Step-by-Step: Recover a Deleted Power App</h4><p>1. Install Required PowerShell Modules</p><pre><br>Import-Module Microsoft.PowerApps.Administration.PowerShell<br>Import-Module Microsoft.PowerApps.PowerShell</pre><p>These modules provide the cmdlets needed to interact with Power Apps environments and manage app lifecycles.</p><p>2. Authenticate to Your Tenant</p><pre><br>Add-PowerAppsAccount</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*j8TfkNWxXnhuO713XXz1cA.png" /></figure><p>This command opens a login prompt. Use your admin credentials to authenticate.</p><p>3. Identify the Environment</p><pre><br>Get-AdminPowerAppEnvironment</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dmocy_U7RdmikvRYG_q4gQ.png" /></figure><p>This returns a list of environments. Look for the one where the app was deleted — its name will be a GUID.</p><p>4. List Deleted Apps in the Environment</p><pre><br>Get-AdminDeletedPowerAppsList -EnvironmentName &#39;your-environment-guid&#39;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kcKmromarmGUatG6cTvR_g.png" /></figure><p>This shows all deleted apps in the specified environment. Note the App Name of the one you want to recover.</p><p>5. Recover the Deleted App</p><pre><br>Get-AdminRecoverDeletedPowerApp -AppName &#39;your-app-name&#39; -EnvironmentName &#39;your-environment-guid&#39;</pre><p>If successful, the app will be restored to its previous state in the environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEWkI2DN6YogMtpkuyzBOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tcN_iXOEmSeJTFJSvtDqCQ.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6c1pYTnOcgg&amp;type=text%2Fhtml&amp;schema=youtube&amp;display_name=YouTube&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6c1pYTnOcgg%3Ffeature%3Doembed" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2a100726dac20529fca17df5fefaf756/href">https://medium.com/media/2a100726dac20529fca17df5fefaf756/href</a></iframe><h4>Pro Tips</h4><ul><li>Act quickly: Deleted apps may only be recoverable for a limited time.</li><li>Use version control: Consider integrating source control with Power Platform to reduce reliance on manual recovery.</li><li>Audit regularly: Keep track of who has delete permissions and monitor app lifecycle events.</li><li>Educate your team: Make sure developers understand the importance of ALM, solutions and safe development practices.</li></ul><h4>Final Thoughts</h4><p>Recovering a deleted Power App is not only possible, it’s straightforward with the right tools and permissions. Whether you’re a Power Platform admin or a developer like Jamie, knowing how to use PowerShell for recovery can save hours of work and prevent unnecessary stress.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8c1a51bc327" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essential Power Automate Expressions for Beginners]]></title>
            <link>https://medium.com/@getsplashnz/essential-power-automate-expressions-for-beginners-95e62ad97d90?source=rss-d3152b41f605------2</link>
            <guid isPermaLink="false">https://medium.com/p/95e62ad97d90</guid>
            <category><![CDATA[power-automate-expression]]></category>
            <category><![CDATA[power-automate]]></category>
            <category><![CDATA[power-automate-training]]></category>
            <category><![CDATA[power-automate-developer]]></category>
            <dc:creator><![CDATA[Ash @ Getsplash]]></dc:creator>
            <pubDate>Sun, 13 Jul 2025 02:53:28 GMT</pubDate>
            <atom:updated>2025-07-13T02:53:28.989Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Your go-to cheat sheet for mastering basic expressions in Power Automate.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oQHN0k9gBEQsurbdDQU8dA.png" /></figure><h3><strong>Why Expressions Matter</strong></h3><p>Expressions in Power Automate are the secret to transforming basic flows into dynamic, intelligent automations. Whether you are manipulating data, formatting dates, or customising outputs, expressions give you the flexibility to build smarter workflows.</p><p>In this post, we will explore some essential expressions that every beginner should learn. I use these expressions almost daily so thought I would share them with you.</p><p>These foundational expressions are perfect for beginners and essential for every flow builder.</p><h4>Date &amp; Time</h4><p>Use these to get the current time, format it, and manipulate it across time zones.</p><pre>utcNow()<br>formatDateTime(utcNow(),&#39;yyyy-MM-dd&#39;)<br>addDays(utcNow(), 7)<br>subtractFromTime(utcNow(), 1, &#39;Hour&#39;)<br>convertFromUtc(utcNow(),&#39;New Zealand Standard Time&#39;,&#39;dd-MM-yyyy&#39;)<br>formatDateTime(convertTimeZone(utcNow(), &#39;UTC&#39;, &#39;New Zealand Standard Time&#39;), &#39;yyyy-MM-dd&#39;)<br>convertFromUtc(addDays(utcNow(),7),&#39;New Zealand Standard Time&#39;,&#39;dd-MM-yyyy&#39;)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/456/1*lvf3VkJ5IY46rwHnhqJHQw.png" /><figcaption>Returns the current date and time in Coorinated Universal Time (UTC).</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*2aNXlUcoirlI5oDASGFnFg.png" /><figcaption>Minus 1 hour from the current time</figcaption></figure><h4>String Functions</h4><p>These help you clean, format, and manipulate text dynamically.</p><pre>concat(&#39;Ash&#39;, &#39;@getsplash&#39;)<br>substring(&#39;PowerPlatform&#39;, 0 , 5)<br>tolower(&#39;Ash@GetSplash.onmicrosoft.com&#39;)<br>toupper(&#39;New Zealand&#39;)<br>trim(&#39;text&#39;)<br>replace(&#39;New Zealand&#39;,&#39;New Zealand&#39;,&#39;NZL&#39;)<br>length(&#39;EmployeeName&#39;)<br>split(&#39;a,b,c&#39;, &#39;,&#39;)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*9EIpi0yA9W3QlEvfW5xpUg.png" /><figcaption>Returns the number of characters in a string or the number of elements in an array.</figcaption></figure><h4>Math &amp; Conversion</h4><p>Perfect for calculations and converting between data types.</p><pre>add(10,34)<br>sub(34,10)<br>float(5.98)<br>int(&#39;6&#39;)<br>mul(5,6)<br>div(100,5)<br>string(123)<br>min(outputs(&#39;Compose_-_div&#39;),outputs(&#39;Compose_-_mul&#39;))<br>max(outputs(&#39;Compose_-_mul&#39;),outputs(&#39;Compose_-_div&#39;))<br>rand(1,1000)<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*xB9CcLQs2tu-GF0okxS1Ww.png" /><figcaption>Min returns the smallest value from a set of numbers or an array of numbers.</figcaption></figure><h4>Logical &amp; Conditional Expressions</h4><p>Control flow and decision-making with these logical tools.</p><pre>if(condition, trueValue, falseValue)<br>equals(value1, value2)<br>and(equals(status,&#39;Approved&#39;),greater(total,100))<br>or(condition1, condition2)<br>not(condition)<br>empty(value)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*8v9Ks_9gK4zRVHTXONS7Qg.png" /><figcaption>If is a conditional statement, evaluating a condition and returning one value if true and another if false</figcaption></figure><h4>Referencing Essentials</h4><p>Use these in <strong>Select</strong>, <strong>Apply to Each</strong>, or <strong>Condition</strong> actions to dynamically access properties.</p><pre>item()?[&#39;first_name&#39;]<br>item()?[&#39;id&#39;]</pre><h4>Simple HTML Email Template</h4><p>Use this is a <strong>Send Email (V2) </strong>to create clean, readable messages.</p><pre>&lt;p&gt;<br>Hi, &lt;br&gt;&lt;br&gt;<br>The applications for have been approved.&lt;br&gt;&lt;br&gt;<br>Thanks.&lt;br&gt;<br>&lt;/p&gt;</pre><pre>&lt;p&gt;<br>Hi, &lt;br&gt;<br>&lt;br&gt;<br>The application for outputs(&#39;Get_item_-_get_item_from_the_Expression_Cheatsheet_SharePoint_List&#39;)?[&#39;body/FirstName&#39; outputs(&#39;Get_item_-_get_item_from_the_Expression_Cheatsheet_SharePoint_List&#39;)?[&#39;body/LastName&#39;] has been approved.&lt;br&gt;<br>&lt;strong&gt;Details&lt;/strong&gt;&lt;br&gt;<br>Email: outputs(&#39;Get_item_-_get_item_from_the_Expression_Cheatsheet_SharePoint_List&#39;)?[&#39;body/email&#39;]&lt;br&gt;<br>Country: outputs(&#39;Get_item_-_get_item_from_the_Expression_Cheatsheet_SharePoint_List&#39;)?[&#39;body/Country&#39;]&lt;br&gt;<br>&lt;br&gt;<br>&lt;a href=&quot;outputs(&#39;Get_item_-_get_item_from_the_Expression_Cheatsheet_SharePoint_List&#39;)?[&#39;body/{Link}&#39;]&quot;&gt;View the item here&lt;/a&gt;&lt;br&gt;<br>Thanks.&lt;br&gt;<br>&lt;/p&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/879/1*bRAarPw5y_TLHzw6sD8Ojw.png" /><figcaption>HTML content for a Send Email action</figcaption></figure><h4>Filter Queries</h4><p>These are useful to reduce the number of items you are receiving based on data you already have in your flow or should need.</p><pre>Country eq &#39;New Zealand&#39;<br>DueDate eq &#39;addDays(convertFromUtc(utcNow(),&#39;New Zealand Standard Time&#39;,&#39;yyyy-MM-dd&#39;),-30,&#39;yyyy-MM-dd&#39;)&#39;<br>Status eq &#39;outputs(&#39;Compose_-_Choice_Value&#39;)&#39;<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*b_T91a2sg5TbRTdB9EHY_A.png" /><figcaption>Filter queries refine data allowing you to specify conditions to limit the data based on needs.</figcaption></figure><h4>Array &amp; Collection Expressions</h4><p>Manipulate and analyse arrays and collections with these essential expressions.</p><pre>length(variables(&#39;arrFruit&#39;))<br>first(variables(&#39;arrFruit&#39;))<br>last(variables(&#39;arrFruit&#39;))<br>join(variables(&#39;arrFruit&#39;),&#39;,&#39;)<br>contains(variables(&#39;arrFruit&#39;),&#39;Banana&#39;)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*4v_psC_zUGSPvEhPIJkpmA.png" /><figcaption>Checks if a string or array contains a specific value or substring.</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXURfNj6jxDY&amp;type=text%2Fhtml&amp;schema=youtube&amp;display_name=YouTube&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXURfNj6jxDY%3Ffeature%3Doembed" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5263fcabcddb9cddc1e8f995ef032762/href">https://medium.com/media/5263fcabcddb9cddc1e8f995ef032762/href</a></iframe><h3>Building Expressions into Your Flow</h3><p>When working with complex expressions, I often take a modular approach by using multiple ‘<strong>Compose</strong>’ actions to break down the logic. This allows me to isolate and test each part of the expression individually, ensuring accuracy and clarity. Once I’ve validated the outputs, I consolidate the logic into a single expression for efficiency. This method not only simplifies troubleshooting but also helps build confidence in how each component behaves within the flow.</p><p>Over time, I’ve shifted towards using expressions more strategically to streamline my flows. Instead of relying heavily on additional actions like ‘<strong>Condition</strong>’ or ‘<strong>Convert time zone</strong>’, I embed logic directly into expressions. This keeps my flows lean, reduces nesting, and improves readability. By minimising the number of actions, I maintain a smoother flow structure that’s easier to manage and scale.</p><h3>Final Thoughts</h3><p>Expressions are the backbone of Power Automate. Mastering them unlocks a new level of automation power. Bookmark this post, share it with your team, and start building smarter flows today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95e62ad97d90" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>