Category Archives: Power Automate

Using Environment Variables to configure Word Template action in the cloud flows

Power Automate word templates are much more fun to work with than the classic D365 word templates, yet we can happily use them in the model-driven app with a bit of javascript: https://www.itaintboring.com/dynamics-crm/power-automate-word-templates-in-model-driven-apps-forms-integration/ However, how are we supposed to deploy flows containing “Populate a Microsoft Word Template” action in different environments so that each environment… Read More »

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 »

Form component controls and field validations / event handlers

Form components controls (https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/form-component-control) can be extremely useful. It may not look so, at the first glance, since, after all, what they give us is, essentially, one extra tab on the “main” table form. In that tab, we can display columns from the secondary table. This comes at the cost of not having access to… 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 »