The more I use Solutions, the more I am starkly reminded how they can add both complexity and unintended issues, despite their obvious advantages . He is the latest issue I am seeing:
In my flows I have deep links that are built up from Compose Actions. Now I need to ensure I am using the correct App Id in these deep links depending on whether the flow is running in Production or Development environments.
Do I end up with yet more environment variables: one for each of my App IDs which I am expected to change during the deployment cycle? If I can check the current environment in my Power App via a system environment variable then that would help , to detect the correct var to use , either a String or json type.
Solved! Go to Solution.
I think this maybe a start but for Power Automates, tho still need to store and manage those App IDs (sigh🙄)
I think this maybe a start but for Power Automates, tho still need to store and manage those App IDs (sigh🙄)
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
10 | |
8 | |
5 | |
3 | |
2 |