When you tired, it's 9PM on Monday ... It's Monday. I'm too tired to slap you. Could you please bash your face against my palm? Respond to PowerApp or flow action Respond to PowerApp or flow action doesn't get triggered. I wonder why... Respond to PowerApp or flow action doesn't get triggered ActionConditionFailed I've got… Continue reading Child Flow: the ‘runAfter’ condition is not satisfied.
As you know I am a very big fan of Dataflows. The biggest ask from me was always the ability to trigger the Dataflow refresh on demand from a Power App. Initially, Dataflows you could only run from the maker portal. You need all sort of "powerful" security roles and permissions to do so. Dataflows… Continue reading Dataflows for Power Apps: run import from the app
Within Power Automate I am trying to make SINGLE(paginated) call to Dataverse to get the list of Work Orders with the particular status linked to Account but not directly but via extra layer. Also, I can retrieve extra lookup tables which are required by logic. All in a single call because making extra API calls… Continue reading Power Automate with Dataverse: Saving API calls to Dataverse. Expand or Link-Entity?
Recently I was working on the solution and in the middle of the development discovered that I desperately need to refer to the previous item in the loop. Let's say, I iterate through the list of items I received via List Rows (Dataverse). I check a condition in the next iteration and based on the… Continue reading Power Automate with Dataverse: “Apply to each” current item/previous item
Dataflow magic in Power Automate. SQL with Power Query in Power Automate. Did you know you can do this?
“We are screwed!”
me at the moment of technology induced panic
That was the feeling when I saw the below error messages.
The client’s setup is an on-prem SQL server exposed to the cloud via an on-prem Gateway. It works perfectly fine for exiting Dataflow integration, but this time we needed data from a function in Power Automate.
Now problem, you can use SQL server connector, right?
Almost (but yes, if you read this post or knew before).
Set back #1
You cannot use “Execute a SQL query (V2)” with an on-prem gateway connection. Not supported!
Sure, let’s then use “Execute stored procedure (V2)”.
Set back #2
Apparently, you cannot return dataset from the function. Can call it if it was just a function or procedure without return value. But if it returns data – bad luck!
Panic mode on!
Wait, but what if…
Power Query to the rescue! Again.
View original post 159 more words