Category: Flow

  • Power Automate: sum(field1, field2, field3, field4) is greater than 0.Easy?

    The requirement is to summarize 4 number field values to determine if the total is greater than 0. What could possibly go wrong? You think it should be somewhere in the Expression under Math functions. Think again. The add only allows to summarise 2(!?) numbers. Not 3, not 4. It let me to add extra…

  • Power Automate: Group/Ungroup in Advanced Condition

    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!

  • Power Automate: watch your (white)space!

    Well, as per the title. Watch your whitespace. For example, I was getting this error on the checker and tried to figure out what is wrong with the reference name. When you use expressions you have to type things in. This is where you have to extra careful. It seams to look OK but in…

  • Power Automate: PARSE JSON action with value or null

    Power automate is endless fun! Today we are going to explore a very “simple” issue which are 2 issues actually: how to define “allow null” in a schema to avoid annoying errors how to get away with the 1. without the painful consequences Let’s start from the beginning! PARSE JSON is a very useful action…

  • Power Automate for CDS: “what was it before we run the update?” or “bye,bye, no-code!”

    The requirement: for Account(Property in our case) if related Contact(Tenant) is “un-linked”, create a Note. No-code solution: none. Why? These are triggers available for CDS(current environment): We choose Update trigger for Contact filtering by parentcustomerid … and this is it. This is where our no-code journey ends. When Update triggers on our Contact the value…