Power Platform Tip of The Day presents: Power Automate expressions you didn’t know you needed until you found them. Everyone keeps a stash of useful Power Automate expressions in Notepad++, VS Code, EMacs, vi, or sticky notes if you don’t know what any of the above mean. Good citizens and developers (Amey “ABC” Holden, Antti […]
Tip #1424: The user does not have sufficient access right to run flow with custom connector
I’ve tried all the right things: Created, deployed, and configured custom connector into the target environment before importing the solution that uses the connector. All tests pass. Created a manual Power Automate flow as part of the solution. Shared the flow with the user (should not need to for the solution flows but just in […]
Tip #1418: In-app notifications in model-driven apps
Welcome to inaugural video shorts where all human knowledge is compressed into the bites of 60 seconds or less, to be consumed while waiting for the paint to dry. In this episode we help Lisa to enable in-app notifications in model-driven Power Apps without any code using a freshly baked XrmToolBox tool by Ivan Fricko. […]
Tip #1417: Power Excel in SharePoint
You’ve seen us in Tip #1415 doing some Microsoft Graph abracadabra to call Excel functions directly from Power Automate. To do that we use Excel spreadsheet located on OneDrive for Business. Documentation mentions in passing that “You can use Microsoft Graph to allow web and mobile applications to read and modify Excel workbooks stored in […]
Tip #1415: Call Excel functions from Power Automate
If you know Excel you’ll be very comfortable with Power Automate, they said. Except most of the Excel functions do not even have an equivalent in Power Automate. But what if we could access all Excel functions in Power Automate? Say no mo In the Episode 13 of Citizen Can Amey and George talk about […]
Tip #1408: When tomorrow comes in Power Automate
Ever wondered how to use Dataverse date filters like “Today” or “Tomorrow” when listing records in Power Automate? Yes, plonking in the entire FetchXML with <condition attribute=”enabler_stamp” operator=”tomorrow” /> is one way to handle that. The other is to use query function Tomorrow in the filter: Microsoft.Dynamics.CRM.Tomorrow(PropertyName=’enabler_stamp’) Here’s the catch: “tomorrow” is relative. If you live anywhere west […]
Tip #1406: Flow history takes long time to load
Cover photo by invisiblepower from Pexels
Tip #1404: App secrets that last longer than 2 years
Using service principals is the great way to ensure that Dataverse connections in your Power Automate flows are not user-dependent and nothing is going to break when the original creator’s account gets disabled. These are good step-by-step instructions: How to setup a Common Data Service Application User (and why) (I’ll give Nick Doelman a separate […]
Tip #1401: Round time in Power Automate
Today’s conversation: – Hey, wanna see cool way to round time in Power Automate?- Sure- *shows the trick*- Why it’s not a tip yet?- Mmmmm, dunno… True story. Sometimes we need to round time in Power Automate. For example, you want to schedule a meeting for tomorrow, at the same time as now. Except “now” […]
Tip #1397: Reduce extra Power Automate runs and overcome trigger limitations
You know I’m a sucker for some open source goodness. This time the goodness is from Aiden “President” Kaskela. (Got something to share? Send your wares to jar@crmtipoftheday.com). The Common Data Service (Current Environment) trigger in Power Apps allows you to run your cloud flow when certain fields are updated, but there are two shortcomings: […]