Unanswered

Trigger a flow from within code (that still works after promoting solution)

(0) Share

Report

Posted on by Wauters

We'd like to trigger a flow from within a model driven app by using code (JavaScript WebResource).

We have used HTTP POST as a trigger for our flow and this works by calling the HTTP POST URL from within our code. But, every time we promote our solution (e.g. from DEV to TEST), our code is broken as the HTTP POST URL of our flow has changed. Is there any other way we can trigger a flow from within code that won't break when promoting solutions? Previously, to manually trigger a Workflow, we could use the WorkflowId that remained consistent between environments.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

summitb on at

Like (0)

Report

You can create a constant.js where urls for each of the env is stored and add a logic that check if the env is dev or prod.

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
Hi @Wauters,

Unfortunately this isn't supported yet and haven't found a way to preconfigure the POST URLs beforehand when deploying with CDS solutions. It has been a big pain for us to manage through the different environments especially that we have everything automated in Azure DevOps... Here are a couple of workarounds but are more advanced:

Haven't try this yet but hopes this works! Build a PowerShell script that:

runs after your solution import that gets the flow http url with the Flow PowerShell cmdlets

Set the URL in a system configuration entity. If you don't already have one, you can use CDS environment variables

In your JavaScript get the URL by retrieving it from the config entity.

The other method which I used was by leveraging Logic Apps instead of Power Automate where I deployed them with ARM templates and was able to automatically wire up the URLs.

Similar the #1, in your JavaScript reference a configuration entity to retrieve the URL. Manually set the URL in each environment once the flows are deployed in and URLs are known.

I suggest you submit the idea here and I'll vote: https://powerusers.microsoft.com/t5/Power-Apps-Ideas/idb-p/PowerAppsIdeas

Hope this helps!

Was this reply helpful? Yes No