Share
Report
7Hi everyone,
I’m encountering an issue after migrating a Power App from one environment into our development environment. The migration itself went smoothly, and the app works as expected in the new environment: all screens, controls, and logic function correctly, and the connections to the underlying data sources appear to be present and operational.
However, when I attempt to add the app into a Solution in the development environment, I receive a warning indicating that a connection reference is missing. The reference points to the ID of the connection from the original environment, which no longer exists in the development environment. This happens despite the app seemingly working correctly and all connections being available in the new environment.
This raises several questions and concerns:
-
What is the proper way to re-map or update connection references when moving an app to a different environment?Is it recommended to create new connection references in the target environment and manually replace the old ones inside the app or the Solution?
-
Are there any best practices for managing connection references to avoid these issues when using Solutions for ALM (Application Lifecycle Management) or CI/CD pipelines?
-
Could this cause any runtime issues if the app is used without resolving the connection reference warnings?
I want to ensure that the app can be safely included in a Solution for deployment or ALM purposes without breaking any connections, and that future migrations between environments will be smooth.
Any guidance, step-by-step procedures, or best practices from the community would be greatly appreciated.
Thank you in advance for your help!
All responses (
Answers (
