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 our Contact the value for parentcustomerid will be null. Meaning we can’t attach to the previous parent customer anything because we have no idea what it was before it changed.

And this is where I created my plugin for the first time in years. It was an exciting experience for another blog post.

Here is what makes it different and gives us extra functionality to solve the problem with a code.

Plug-in pre-image

I created an idea for this issue, please support me if you think it’s cool to have this functionality in Power Automate:

https://powerusers.microsoft.com/t5/Power-Automate-Ideas/CDS-Update-trigger-Pre-Image-is-required-to-review-field-values/idi-p/582088

Happy no-coding!

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

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s