Tag Archives: PowerAutomate

Why you should consider periodic / on demand refresh for the Canvas Apps / Flows

Have you ever noticed the following paragraph in the Canvas Apps coding guidelines? Periodically republishing your apps The PowerApps product team is continually optimizing the Power platform. Sometimes, for backwards compatibility, these optimizations will apply only to apps that are published by using a certain version or later. Therefore, we recommend that you periodically republish… Read More »

“When an item is created” SQL trigger in Power Automate

There is a SQL Connector in Power Automate, and it has couple of triggers which are dependent on the IDENTITY/ROWVERSION columns in SQL: The existence of those two columns in the table is a pre-requisite for the trigger to work: https://docs.microsoft.com/en-us/connectors/sql/#when-an-item-is-created-(v2) There is a catch there, though, and I probably would not know about it… Read More »

How to: not to get stuck on the required fields when creating a Power Automate Flow

Microsoft Dataverse has a somewhat unique interpretation of what a “required” field is. It’s a bit of “do as I say not as I do”. For example, I can’t create an account in the user interface not having “account name” populated (since it’s a required field): But, of course, behind the scene… whether through Excel… Read More »

Incremental refresh for the Dataflows which are loading data from SQL to Dataverse

In one of the earlier posts this month I was seemingly unhappy about the missing “incremental refresh” option: https://www.itaintboring.com/dynamics-crm/power-platform-dataflows-have-i-missed-incremental-refresh-option-somehow/ But, having thought about it a bit more, I don’t think it’s such a big issue. Not when working with the SQL data sources, at least. All we really need is a view that will pre-filter… Read More »