Unanswered

AppMetadataFetchFailed error when trying to call custom page

(0) Share

Report

Posted on by TS-29051325-0

I have an application that is working in my Dev, QA and production environments, but when I try to get it working in a new environment, I get an error. The app is model-driven with several custom pages. I fire these custom pages through a command button that calls Java to pass the record id to the custom page. I get the following error on all such calls.

Error Code: AppMetadataFetchFailed

Encountered internal server error. The correlation Id is 'e99bfa3e-337e-404c-8f65-10ac8b11b459'.

I've tried restoring a backup of an environment that is working fine and also creating a new Sandbox and installing the solution. I get the same error. It's been 9 months since I've really tried to delelop with these environments and I'm wondering if a Power Apps update may be causing this in new environments. I can't find anything helpful on any forums or articles.

Todd

Categories:

General Questions

I have the same question (0)

All responses (4)

Answers (0)

SaiRT14 1,988 Super User 2025 Season 2 on at

Like (0)

Report
AppMetadataFetchFailed error when trying to call custom page

Pls try the following:

Validate the Custom Page: Open the Power Apps Maker Portal for the affected environment. Navigate to Apps > Locate your Model-Driven App > Edit. Ensure the custom page is listed under Pages.

Ensure Proper URL Passing: If you’re using JavaScript to pass the record ID, confirm the syntax matches the expected URL format.

Xrm.Navigation.navigateTo({
pageType: "custom",
name: "your_custom_page_name",
entityName: "account",
recordId: "<record-id>"
});

Was this reply helpful? Yes No
TS-29051325-0 26 on at

Like (0)

Report

AppMetadataFetchFailed error when trying to call custom page

Thanks for the reply. Custom page is part of the model driven app and the java format is exactly as you listed.

This is code that has been working fine, and is still working fine on established environments (Prod, QA, Dev) I'm only having problems when I try to get it working on new environments.

Was this reply helpful? Yes No
TS-29051325-0 26 on at

Like (0)

Report

AppMetadataFetchFailed error when trying to call custom page

I've actually got another button that just does a Formula call to launch Google Maps and it also isn't working in the environments but is working fine in existing environments.

Was this reply helpful? Yes No
TS-29051325-0 26 on at

Like (0)

Report

AppMetadataFetchFailed error when trying to call custom page

After doing some more testing, I've now discovered that even adding a new command button that does a simple FX formula (launching maps.google.com) isn't working either. It appears that all custom commands in my solution are broken in a new environment. Any ideas? Thanks.

Todd

Was this reply helpful? Yes No