Tip #1351: Flows not triggering after environment copy

Today’s tip from Ankita Chavan – a good reminder to get your housekeeping in order while copying the environments. Got a tip of your own? Send it to jar@crmtipoftheday.com! We were working on the full copy of data from UAT Environment to dev Environment and we were testing existing functionality. We found that flow was […]

Tip #1350: Modify webhook return status as needed in Power Automate

Power Automate is very handy to serve as a webhook. Add When a HTTP request is received trigger and you’ll get a URL to call after you save the flow. (Genuinely curious if it should be “an HTTP“ instead.) Any flow triggered by HTTP request executes asynchronously, i.e. it returns to the caller immediately after […]

Tip #1317: Make lead qualification better with Power Automate

You work on a lead in Dynamics 365–you have several conversations and enter some notes. After you qualify the lead, the activities show up on the account or contact record that was created in the qualification process, but the notes are left behind on the lead. Power Automate to the rescue! Create a Flow that […]

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 #1310: Using Flow to test concurrency

A number of silver wind pipes lined up in parallel

Today’s tip is from Shidin ‘D365fanboi’ Haridas – thank you! Got a tip of your own? Why won’t you send it to jar@crmtipoftheday.com when you have a minute? Now, over to Shidin. Most CRM implementations, at some point, would have required to implement a bespoke auto-numbering system. However, testing the custom built auto-numbering solution end-scenarios, […]