James Bartlett :terminal:<p>One of my <a href="https://techhub.social/tags/PowerShell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PowerShell</span></a> hacks for <a href="https://techhub.social/tags/PowerBI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PowerBI</span></a> just got a huge <a href="https://techhub.social/tags/upgrade" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>upgrade</span></a>: <a href="https://techhub.social/tags/Pipeline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pipeline</span></a> support! </p><p>In layman's terms, this means that one <a href="https://techhub.social/tags/function" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>function</span></a> can be strung together with another function in a single PowerShell command, and the outputs from the first function feed directly into the second's inputs. The best part is that the whole chain of functions can operate as a <a href="https://techhub.social/tags/stream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>stream</span></a>, so as soon as the first item is available, it gets passed down to the next function in the chain, which begins processing that item, while the previous function is working on the next item in the queue. It's like an <a href="https://techhub.social/tags/AssemblyLine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AssemblyLine</span></a> for data!</p><p>Of course, now I'll have to go back and apply this technique to all of the other functions I've written previously. <a href="https://techhub.social/tags/NoRestForTheWicked" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NoRestForTheWicked</span></a> 😈</p>