You’re offline. This is a read only version of the page.
193
Hi,
When a solution has cloud flows with HTTP triggers, we don't know what is the trigger URL until it's saved in the destination environment. How do we do ALM on that? Currently, I have maintained the URL in a dataverse table. After solution import is finished, I get the URL from the destination env manually and update it in the dataverse table
Hi,
Just joining in as I'd be interested to know this as well.
I'm currently using a similar approach whenever I have this type of flow. Since it's a one time only configuration I just manually save and get the URL after the initial release, configure it on an environment variable (or some other variable storing method) and configure it on the pipelines if needed.
But interested to know if there's a way to automate it as well
Share
Report
All responses (
Answers (
