One (current) issue affecting both PowerApps and Flow is that neither support Managed Metadata Columns properly. This post outlines a method that – after getting access tokens – uses REST endpoints to update managed metadata columns.
This is a crazy one, and if you have read ALL my Microsoft Flow blog posts, you’ll be familiar with all these pieces. We are going to connect them a different way though, and the result is still awesome.
In real world environments, organizations usually want to restrict the group provisioning so that IT can control the wild growth of groups. This article series shows how to create an Office 365 group with an attached approval process with SharePoint Online, Flow and Azure functions. See how this works here!
Perhaps because of technological convergence through DVRs and TiVo, television fragmentation, and the so-called post-network era, for many television scholars working on “important” texts – most often masculinized shows that air in primetime – flow has become passé, bygone, and moved beyond in television studies. Choosing not to engage with the (super)text and focusing only on the narrative elements of a show makes for concerning, unremarked-upon assumptions about “quality” audiences and spectatorship practices with strong implications for erasures of class and gender beyond what I can cover here. But flow is, of course, alive and well and even, as I’ll argue, desired. Moreover, it’s not only characteristic of network broadcasting (especially in daytime), but cable and non-network spaces are themselves begging for ‘flownalyses.’ For instance, I’m an avid viewer of Logo’s #sitcomtherapy nights, which air old episodes of queer-friendly sitcoms like The Golden Girls and Roseanne, punctuated by bumpers showing gay men and couples, PSAs by gay puppets educating audiences about AIDS, and programs for queer shows with queer bodies like RuPaul’s Drag Race, all the while overlaid by Tweets, hashtags, and queer trivia.