Business Applications, Flow, power automate

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. Flow Checker error When you use expressions you have to type things in. This is where you have to extra careful. Typing in expressions may… Continue reading Power Automate: watch your (white)space!

Business Applications, Common Data Service, Flow, power automate, PowerApps, Uncategorized

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 errorshow to get away with the 1. without the painful consequences Let's start from the beginning! PARSE JSON is a very useful action and… Continue reading Power Automate: PARSE JSON action with value or null

Flow, No-code vs Code, power automate, Uncategorized

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): CDS current environment triggers 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… Continue reading Power Automate for CDS: “what was it before we run the update?” or “bye,bye, no-code!”

Common Data Service, Flow, power automate

CDS current connector: Filter expression. My Flow doesn’t trigger!”

I thought you will love this one. It's that type of "Help! My Flow hasn't get triggered" thing which we all love. How to reproduce For the CDS entity which has some existing records then a new optionset field has got created. As a result some records may not have this field populated. If you… Continue reading CDS current connector: Filter expression. My Flow doesn’t trigger!”

Common Data Service, Flow, power automate

CDS current environment connector : “The following filtering attributes are not valid:…”

Life is pain... "The following filtering attributes are not valid:..." {  "error": {    "code": "0x80040203",    "message": "The following filtering attributes are not valid:  lastname"  }} Fix the trigger ...error Remove the white space between the comma and the next attribute! A white space between filtering attributes causing the error. No white space between filtering attributes It is simple... always... after 🙂