Tip #1392: Missing entities in Power Automate

Missing piece

The classic “give me 5 minutes and I’ll whip a flow for you” did not start well. Users entity table was not there. Options Choices: It’s something trivial and I’m simply no longer worthy. ‘u’ is not an actual ‘u’ but Russian ‘и’ typed accidentally but in a weird font. It’s a UI bug It’s […]

Tip #1367: Tell apart create, update, and delete events

It’s not every day one gets to chime in on a post from Jerry, the lifetime tipster and Power Automate connoisseur. In this post Jerry talks about When a record is created, updated, or deleted trigger in CDS (current environment) connector and how to tell the event that triggered the flow using a clever combination […]

Tip #1311: Use entity name in Flow lookups

If you are building your Flows from solutions and connecting to Common Data Service, you should use the CDS (current environment) connector. When you do, if you populate lookup fields, you might get a “resource not found” error message. If you get this error, like I did, you are probably just putting the guid of […]

Tip #1227: Use CDS instead of Dynamics 365 connector in Flow

A hand plugging a wire into a network router

People have been reporting that Dynamics 365 triggers in Flow are not consistent. Sometimes they fire twice, sometimes not at all, sometimes they fire after a manual test run. There are some other weird side-effects I did not even look into. Why? Because of one of them quick tips. Where possible, use Common Data Service […]

Tip #275: Uninstalling the MDM Connector

If you implement Microsoft Dynamics Marketing, Microsoft documents the process of installing the MDM connector. However, should you ever need to remove the connector, the instructions are not as clear. At a high level, the process of uninstalling the connector is:  Be sure the connector queues are drained. Verify in Azure management portal that there are […]