[CoE Starter Kit - BUG] Failed Import - SavedQuery (Abandoned PowerApps)

[bleaeib]

Does this bug already exist in our backlog?

• [X] I have checked and confirm this is a new bug.

Describe the issue

The exception that we are seeing is: Microsoft.Crm.CrmException: The SavedQuery(f9d327af-b6b4-e911-a85b-000d3a372932) component cannot be deleted because it is referenced by 1 other components. For a list of referenced components, use the RetrieveDependenciesForDeleteRequest

investigation conducted by MS

Type 26 - SavedQuery Type 80 - AppModule

It seems that the view that is being referenced in the App Module was removed by the developers, since doesn't seem to exist in the customization.xml anymore. It tried to find it but doesn't seem to have any:

Expected Behavior

import and upgrade correctly.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.31

What app or flow are you having the issue with?

Center of Excellence Core Component

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

1. import the solution CenterofExcellenceCoreComponents_4.33_managed.zip
2. upgrade solution
3. after an 1h getting the error : Microsoft.Crm.CrmException: The SavedQuery(f9d327af-b6b4-e911-a85b-000d3a372932) component cannot be deleted because it is referenced by 1 other components. For a list of referenced components, use the RetrieveDependenciesForDeleteRequest

Anything else?

No response

[Jenefer-Monroe]

Hello. I believe one other user hit this https://github.com/microsoft/coe-starter-kit/issues/8682 and we were able to find a workaround

The change: We removed a view called Abandoned PowerApps from the kit as it was found to be a confusing duplicate. We did remove it from the MDA's at that time as well of course or it would not have let me delete it.

The issue: For some reason the product's upgrade code is choking on this for some users. I think its because its reviewing all the views and seeing that one has a dependency before checking to see if that dependency had been removed from the MDA.

The workaround This worked for the other person, you can try to remove our dependency on it manually and see if that fixes

1. Remove the _upgrade core solution if it exists
2. Go to Apps > find the Power Platform Admin View app > Edit
3. Remove the problematic view and publish
4. Try your upgrade again.

The ask If this works out please share that feedback with the support person you worked with. They need to get this dependency ordering issue to the product team so that they can resolve it.

[bleaeib]

Corporate Use

Hi,

Thanks for your help. After applying the work around I was able to upgrade to 4.33

@.***

Thanks

Pac

From: Jenefer Monroe @.> Sent: Thursday, August 1, 2024 2:26 PM To: microsoft/coe-starter-kit @.> Cc: BLÉ Anthelme (Ext) @.>; Author @.> Subject: Re: [microsoft/coe-starter-kit] [CoE Starter Kit - BUG] ISSUE TITLE (Issue #8747)

Hello. I believe one other user hit this #8682https://github.com/microsoft/coe-starter-kit/issues/8682 and we were able to find a workaround

The change: We removed a view called Abandoned PowerApps from the kit as it was found to be a confusing duplicate. We did remove it from the MDA's at that time as well of course or it would not have let me delete it.

The issue: For some reason the product's upgrade code is choking on this for some users. I think its because its reviewing all the views and seeing that one has a dependency before checking to see if that dependency had been removed from the MDA.

The workaround This worked for the other person, you can try to remove our dependency on it manually and see if that fixes

1. Remove the _upgrade core solution if it exists
2. Go to Apps > find the Power Platform Admin View app > Edit image.png (view on web)https://github.com/user-attachments/assets/7a36f8f4-6b25-4f6b-8d24-a59ce01040be
3. Remove the problematic view and publish image.png (view on web)https://github.com/user-attachments/assets/fe365cfb-12c3-4dff-bde5-1864b1371381
4. Try your upgrade again.

The ask If this works out please share that feedback with the support person you worked with. They need to get this dependency ordering issue to the product team so that they can resolve it.

- Reply to this email directly, view it on GitHubhttps://github.com/microsoft/coe-starter-kit/issues/8747#issuecomment-2262912636, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKIAB6WTTTQ6CYHVPYDFJ5TZPISOPAVCNFSM6AAAAABL2HN4SGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRSHEYTENRTGY. You are receiving this because you authored the thread.Message ID: @.**@.>>

Les informations contenues dans ce message et/ou ses annexes sont reservees a l'attention et a l'utilisation de leur destinataire et peuvent etre confidentielles. Si vous n'etes pas destinataire de ce message, vous etes informes que vous l'avez recu par erreur et que toute utilisation en est interdite. Dans ce cas, vous etes pries de le detruire et d'en informer la Banque Europeenne d'Investissement.

The information in this message and/or attachments is intended solely for the attention and use of the named addressee and may be confidential. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error and that any use of it is prohibited. In such a case please delete this message and kindly notify the European Investment Bank accordingly.

[Jenefer-Monroe]

Wonderful news! I'll go ahead and close this out then but please do reach out if you need other help in the future.

[send2mark]

1. unintalled failed solution
2. In the apps area for the Power Platform Admin View I removed the Abandon Apps
3. Saved
4. Published
5. Opened the app again to make sure the changes too affect which it did.
6. Same error

Doing all these steps produces and unmanaged layer. When I remove that it reverts my changes of removing the Abandon Apps from the Power Platform Admin view and I continue to have the issue. I am trying to install 4.33