Share
ReportHi guys, basically I have a powerapps that calls a power automate that call a dataflow that write some data in a dataverse table.
Everything works fine in dev environment, but when I tried to deploy to a prod env (managed) I can see the last two parts (dataflow and dataverse) in prod are not being used.
I mean, Prod Power automate calls dataflow from dev environment and then this dataflow write data in dev dataverse.
I tried use environment variable to indicate the correct environment, but for some reason the EnvironmentName is not being recognized by power automate dataflow connector.
Anyone faced something like that?
Everything works fine in dev environment, but when I tried to deploy to a prod env (managed) I can see the last two parts (dataflow and dataverse) in prod are not being used.
I mean, Prod Power automate calls dataflow from dev environment and then this dataflow write data in dev dataverse.
I tried use environment variable to indicate the correct environment, but for some reason the EnvironmentName is not being recognized by power automate dataflow connector.
Anyone faced something like that?
P.S: I made a little test in automate in dev environment pointing directly to the dataflow in prod env and then deploying it.
It works partially because dataflow in Prod also is pointing to dataverse in dev environment and I didn't find a way to change that in dev environment.
It works partially because dataflow in Prod also is pointing to dataverse in dev environment and I didn't find a way to change that in dev environment.
Categories:
All responses (
Answers (
146,695
