Custom Page AppMetadataFetchFailed Invalid environment name referenced

(0) Share

Report

Posted on by Cosmic_Kitchen

105

Hey all,

I recently copied a production environment to a Dev environment. Several Custom Pages were included in the initial environment that I copied.

When I try to access these custom pages within the Model-driven app in the Dev environment I am getting this error:

The incorrect environment reference listed in the error message is in fact the production environment. The listed locations highlighted in red are not custom connections, that I am aware of and when followed take me to Microsoft scripts.

As a test, I created a new custom page from within the Dev environment with no custom connectors. It is only connected to two Dataverse tables for the 'current environment' - and I am getting this error for that custom page as well.

All custom pages in the dev environment are causing this same error.

Any Ideas?

Please let me know what additional information I can provide.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

QuentinDURIEZ 547 Moderator on at

Like (0)

Report

Hello,

I am getting the exact same error after copying an production environment to a sandbox environment, did you found a solution after all this time?

Thanks you,

Was this reply helpful? Yes No
Cosmic_Kitchen 105 on at

Like (0)

Report

@QuentinDURIEZ I'm sorry I missed your question here. This was never resolved and MSFT support was unable to help.

My support tech suggested this issue was likely a consequence of copying the environment (where that functionality doesn't very well support copying of custom pages and flows). Their suggestion was to manually transfer all components in solution to a new environment. Which I did into a fresh environment, and I continued getting the same error.

Let me ask, do you have any custom connectors in the environment that you copied?

This problem is specific to only one of our model-driven apps. Even in the first copied environment, I created a new model-driven app and custom pages work fine in that app. Just not the original app that the error appeared in. The error message is specifically talking about a custom connector, which I did not move between environments. I suspect my predecessor ingrained something into this specific model-driven app related to this custom connector (where the error occurs) that I have yet to find.

Was this reply helpful? Yes No
QuentinDURIEZ 547 Moderator on at

Like (0)

Report

Hi @Cosmic_Kitchen !

Thanks you for sharing your solution !

It was indeed my model driven application, after creating a new one, all of my problems are gone

Have a good day !

Was this reply helpful? Yes No