Why am I not a fan of auto converters which allow you to magically turn something old into something new? In the context of Dynamics 365, old Java Script into a new format, SQL reports into FetchXML, workflows into Flows etc. It's because I believe that "new" is not just about tools, it's about the… Continue reading Don’t auto-convert. Think. Transform.
Implementing a required field validation is the way to force encourage a system user to enter the information which is critical for your business. There are some options below to support this in PowerApps: 1. Too Easy and too obvious. App level validation. It’s a Card property on the Edit form. Select the card you… Continue reading Multiple ways to implement a required field validation in PowerApps. Part 1.
Recently, I am trying to ignore workflows and move all the custom functional logic into Flows. This time I created a very simple Flow converting a text field value into a number and copying it to another field. I needed it for my chart. I run the Flow on a custom entity. An I forgot… Continue reading Help! My Flow is not triggered (for a custom entity)
Customisation & Configuration No Add-Ons + Add-Ons Business Logic Complicity No Add-Ons + Add-Ons + Add-Ons + “No coding” coding Support Support Responsibilities *US - a Dev team for the continues development or a Customer/Support Team - for after GoLive Triage Responsibilities *US - a Dev team for the continues development or… Continue reading Add-Ons, No-code and Other Imaginary Friends vs System Support and Maintenance (random drawings)
If (you know) you are going to repeat some steps of the Flow logic (actions, conditions etc) in multiple Flows for different triggers and entities, think about using a child Flow as a container for a reusable logic. Although you can always clone your Flow via Export-Import, making changes to a single module is much easier… Continue reading Flow: parent-child flows for a reusable logic