Have you ever had your flows turned off when importing them through a solution? It’s been a bit of a mystery to me for a while. I had some idea about what to look at, but it’s only now that I looked closer. Maybe you’ll find it useful, too. First of all, every Flow can… Read More »
It is often helpful to split bigger Power Automate flows into a bunch of smaller ones, so there is a parent flow, and, possibly, a few child flows. However, when the child flow fails, here is what you might see as a result in the flow run history: In the example above, there was a… Read More »
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 »
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 »
Just learned the other day that where Power Automate actions can be showing “display” names in various dropdowns, it might still be some sort of ID/Guid that we should be using when trying a custom value there. For example, in the flow below, when using a “custom value”, I have to use a GUID to… Read More »
When handling errors in the Flows, we can add parallel branches so one of those would run on success, the other one would run on error. However, in the example below, there is a Flow with two parallel branches configured that way, and, even though “On Error” branch is there, the Flow would only execute… Read More »
With the image columns in Dataverse, we can easily add fields to store images directly in the tables like this: This is great, since this makes all those images/documents much easier to identify than if they are stored in Sharepoint. In terms of storage, those images are stored in the file storage which is cheaper… Read More »
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 »
“Common Data Service” connectors don’t have an “Upsert” action: And it would have been a problem for one of the flows I had to implement recently if not for David Yack who pointed out that Update action will do an Upsert. What?? Well, he was absolutely right, here you go: Have fun folks. And thank… Read More »
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 »