Recently I was working on the solution and in the middle of the development discovered that I desperately need to refer to the previous item in the loop. Let's say, I iterate through the list of items I received via List Rows (Dataverse). I check a condition in the next iteration and based on the… Continue reading Power Automate with Dataverse: “Apply to each” current item/previous item
Working with real customer’s deployment requires managing multiple environments – at least Test and Production or additionally a Dev environment. One of the common patterns we use in the solutions is to use Azure Functions as an effective, serverless extension of the point-and-click Power Automate flows. This pattern utilises a Custom Connector created to embed the function call and parameters into… Continue reading Azure Functions in Power Platform multiple environments
In the morning i tried to bring back some stuff from UAT. When I tried to import my solution back to DEV I was getting errors. My solution contained Flows. Why do I use the classic admin interface to import solutions? Read this article: https://wordpress.com/block-editor/post/msolenacrm.blog/1608 I went the classic interface to import the solution. I've… Continue reading Import solution to CDS. Missing Connection references error…
It's not even a post ... Just saying I was wondering how simple is to group or ungroup conditions in the Condition action block. Very simple! From Scratch For existing - Group For existing - Ungroup It seams pretty obvious but I wasn't sure it exists in a user-friendly manner. It does!
The real-life scenario: a portal user (agency) indicates that they don't manage a particular property anymore. The action is performed via self-service portal. From a user experience perspective, the property has to "disappear" from the list of active properties immediately after "no manage" action is performed. If we choose to use Deactivate as an action… Continue reading Power Apps Portal: deactivate account, no workflow please, thank you