Category Archives: Power Automate

User Dataverse connector with non-current environments

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 »

Getting an “object reference not set to an instance of an object” error when deploying a custom connector?

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 »

Multiplexing is fine, as long as you are properly licensed. But can you say if you are?

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 »