You’re offline. This is a read only version of the page.
11
Downloaded the latest COE Starter Kit today from Git Hub - However I couldn't get past step 1 - importing the solution... I am trying it on a new environment with new CDS. I can confirm that the account is a global admin and the owner of the environment and the CDS. Below is the error message. Any ideas?
An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics 365 Community for solutions or contact your organization's Microsoft Dynamics 365 Administrator. Finally, you can contact Microsoft Support. : Microsoft.Crm.Metadata.EntityMetadataNotFoundException: The entity with a name = 'CanvasApp' with namemapping = 'Logical' was not found in the MetadataCache. MetadataCacheDetails:
Thanks
Hi @Sudharsanan,
this appears to be a different error/problem to the original post. Can I suggest that you either post this as a new topic, or submit it to the GitHub issue list: GitHub - microsoft/powerapps-tools: Unsupported PowerApps Tools & Apps
Thanks
Craig
Getting Unexpected : Object reference not set to an instance of an object. while importing CenterofExcellenceAuditComponents_3.13_managed, in one Tenant, but it worked on another tenant.
Have used
CenterofExcellenceCoreComponents_4.17_managed.zip
CreatorKitCore_1.0.20230727.2_managed
Sorry for the long delay - I have a solution from Microsoft Support
The problem was a difference in the versions of PowerApps Microsoft had deployed between different regions - so when my support engineer tested he could import in a PowerApp tenant in Europe, but not in the UK region.
On the 2 September Microsoft updated the other regions, and now it is working - if you experience this problem contact Microsoft Support, they should then be able to tell you when your region will be updated
Hi - We're you able to get info from Microsoft?
We are also experiencing this issue, our environments are in AU region as well.
Just logged the issue to Microsoft but haven't heard back from them yet
Thanks
Understandable. I've logged it on the GitHub site. Let's see who gets a resolution first 🙂
Thanks - I'll log it with MS, because I'm limited to storing our data in certain geographic regions
Try using a different location for the Environment.
I found our Default Australian ones didn't work. But a USA based one did work.
Encountering the same error - excluding the App from the solution isn't really a solution, because the whole point is to deploy the app.
Anyone have any other ideas?
Just created a new PowerApps Environment - USA based - and the import worked!!
I was using Australia based Envrionments previously.
Still got the Flow warning - but I think that will be fixed in later steps.
#1
Michael E. Gernaey
11
Super User 2025 Season 1
#2
stampcoin
9
#3
bscarlavai33
5
Super User 2025 Season 1
Share
Report
All responses (
Answers (
