I’ve long being using Update action of the Dataverse connector to do “upserts”, and it just turned out there are, now (have been for a while?), two separate actions: Update a rowUpsert a row Behind the scenes “Upsert a row” is the old good “UpdateRecord” action. And “Update a row” is a new “UpdateOnlyRecord” action.… Read More »
In the previous post, I did show it off a bit, but how do we actually set it all up? Well, see below, just be ready for a l-o-o-o-ng read. First things first, what’s the ultimate goal? This just speaks “reverse proxy”, but how do I set it up? And there is one more requirement:… Read More »
Apparently, “http request” cloud flows don’t want me to use redirect responses. Well, will have to do it differently I guess? This works:
We don’t always get to choose the technology we work with in the Power Platform world. Strict security, missing subscriptions, long approvals… if you’ve ever worked on the government projects, you know the drill. However, sometimes, this leads to a very unusual combination of tools and technologies, and, in this series of posts, I’m going… Read More »
Quick note to whoever is reading: this post is a bit of an experiment. It’s useful, but it pretty much sticks to the facts and there is no personal touch. This is intentional, there is another post which explains why Back in October, Microsoft has started rolling out updates to the Dataverse connector which will… Read More »
I’m having a strange dilemma, which is that I think I’m supposed to be using Power Automate as much as I can, but I am just not clear on how to license them now. They would be a better choice for automations: However, if I wanted to do ALM, I’d better have Power Automate flows… Read More »
If you created a very minimal custom connector and looked at the swagger definition right after, you’d notice a bunch of attributes added by default: However, not all of those are literally “required” when creating a new connector. For example, I could have removed “schemes” node, and it would still be acceptable: The problem would occur later,… Read More »
It seems I still can’t quite get over those Power Automate licensing updates – new questions keep coming up, we keep digging, and that brings some new revelations. Well, today’s topic is multiplexing. First off all, “multiplexing” is not a bad word 😉 Here is how Microsoft defines it in the Client Access License (CAL) Requirements: “Multiplexing” is when individuals… Read More »
I’ve been trying to figure out the exact definition of what being “in app context” means for Power Automate flows, since that’s where it matters for license enforcement, but every time I seem to come close to having it all figured out, there is always something that does not quite add up. Here is a… Read More »
Hope you have not missed the news – I blogged about it before here, and it’s still coming. Soon enough, you may need to ensure your premium Power Automate flows are either get associated to the apps in order to keep running on the Power Apps licensing plans, or you’ll need to license those flows differently.… Read More »