Hi all.
I have been working with Power Platform for a little more than a year. I work for a bigger corporation where Power Platform is not officially OK'd, but our region has received some special exemptions and are allowed to work in and develop automations, apps etc. Within certain boundaries. This also means that we do not currently have access to setup Pipelines for deployment and testing, and must do the majority manually or through Visual Code.
We are currently struggling a little bit with the best practice for some of our Solutions.
I have a DEV Environment, Test environment and a PROD environment, so the Solutions should go from DEV -> Test -> PROD, but I am finding it difficult to figure out how best to accomplish this with Triggers that require Environment specific variables.
As an example, we are using Dataflows to create Databases and backends for some of our automations and apps, and we have specific flows triggering when the dataflows are updated. However, I have to hardcode the Environment as well as the Dataflow in my Trigger
I have tried using workflow() outputs to determine the environment, but that made the trigger fail constantly.
I would prefer to be able to deploy a complete solution with everything related to that specific process (Dataflows, Tables, Apps, Flows etc.) and not have to go into the Test or PROD environment afterwards and manually update the Managed flows.
I have considered simply changing the Solutions manually through PowerShell or similarly before importing into the new environment, but that also seems like an annoyance and would require us to import the Dataflows and Tables separately so the IDs of the individual entities are created in the other environment(s).
Is there a solution to this that is easy to maintain and setup?
