[CoE Starter Kit - BUG] The connectionreference(111e6575-5fea-41bd-844a-2188584a7759) component cannot be deleted because it is referenced by 3 other components. For a list of referenced components, use the RetrieveDependenciesForDeleteRequest.

sakshiporwal95 commented 1 week ago

Does this bug already exist in our backlog?

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

Describe the issue

The connectionreference(111e6575-5fea-41bd-844a-2188584a7759) component cannot be deleted because it is referenced by 3 other components. For a list of referenced components, use the RetrieveDependenciesForDeleteRequest.

We are seeing this issue when trying to update the COE starter kit. PFA logs

4483b7ca-e2e7-4fc2-8930-286154c10ec8_CenterofExcellenceCoreComponents_reports (2).zip

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.45

What app or flow are you having the issue with?

admin - sync template v3 apps

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response

Jenefer-Monroe commented 1 week ago

Please go find what objects have that dependency. You can do that as shown here (shown for a different connection of course)

sakshiporwal95 commented 1 week ago

Jenefer-Monroe commented 1 week ago

ok the latter is the issue.

So what you've hit here is a product bug in their upgrade processes where you have a flow thats been deleted (Admin | Sync Template v3 (Apps)) referencing a connection referencing that has also been deleted (CoE Core - HTTP Azure AD)

But during upgrade it fails because it thinks it cannot delete the connection reference as it does not check to see if the dependencies are also deleted.

The product team is aware of this issue and is working on it. However in the meantime you will need to remove the dependency. The images below are for a different flow/connection reference, but the same idea applies, you will do the delete from your Admin | Sync Template v3 (Apps) flow

How to work around the bug

As a result, in order to upgrade you will break the dependencies. You will need to:

Delete the _Upgrade solution (if one was left behind)
Open all the flows above, delete most of whats in them, and resave
Do this until the connection reference no longer shows dependencies
Try the upgrade again
Step 2 example

Example of how to do the workaround for one of the flows:

Thats just awful!

Yes I apologize for the hassle. The product team is aware of this issue but the fix has not yet come out.

sakshiporwal95 commented 1 week ago

No upgrade worked but flows are not getting turned ON.

Flow client error returned with status code "Forbidden" and details "{"error":{"code":"ConnectionAuthorizationFailed","message":"The caller object id is '###################################'. Connection 'admin_CoECoreDataverseEnvRequest' to 'shared_commondataserviceforapps' cannot be used to activate this flow, either because this is not a valid connection or because it is not a connection you have access permission for. Either replace the connection with a valid connection you can access or have the connection owner activate the flow, so the connection is shared with you in the context of this flow."}}".

Jenefer-Monroe commented 1 week ago

Great news we've gotten past that issue. It sounds now like your connections are either wrong or misconfigured Please log in as the user who’s identity installs and runs the kit and do the following, then try to turn the flow on as that identity.

Fix connections.

Browse to the connections in the envt. If there are any broken connections please repair them

Fix HTTP with Microsoft Entra ID (preauthorized)

Make sure all the HTTP with Microsoft Entra ID (preauthorized) connections are pointing to your graph URL

Fix Connection References

Lastly go to the Default Solution > Connection References Make sure they are all pointed to the correct identity which is intended to run the flows by doing the below for all connection references.

AAKP95 commented 1 week ago

ok the latter is the issue.

So what you've hit here is a product bug in their upgrade processes where you have a flow thats been deleted (Admin | Sync Template v3 (Apps)) referencing a connection referencing that has also been deleted (CoE Core - HTTP Azure AD)

But during upgrade it fails because it thinks it cannot delete the connection reference as it does not check to see if the dependencies are also deleted.

The product team is aware of this issue and is working on it. However in the meantime you will need to remove the dependency. The images below are for a different flow/connection reference, but the same idea applies, you will do the delete from your Admin | Sync Template v3 (Apps) flow

How to work around the bug

As a result, in order to upgrade you will break the dependencies. You will need to:

Delete the _Upgrade solution (if one was left behind)

Open all the flows above, delete most of whats in them, and resave

Do this until the connection reference no longer shows dependencies

Try the upgrade again

Step 2 example

Example of how to do the workaround for one of the flows:

Thats just awful!

Yes I apologize for the hassle. The product team is aware of this issue but the fix has not yet come out.

Hi,

I got the same connection reference issue for Dataverse -legacy. When I tried above method by- removing actions in flows, now it has created unmanaged layers in flows. How to resolve it?

Jenefer-Monroe commented 1 week ago

Yes thats correct, however those are unmanaged layers in flows that will be deleted.

The issue is that the product upgrade code said... we cant delete connection x because its used in flow y! But flow y is also deleted so its ok to remove the connection.

So on your upgrade these flows will be removed

AAKP95 commented 1 week ago

Yes thats correct, however those are unmanaged layers in flows that will be deleted.

The issue is that the product upgrade code said... we cant delete connection x because its used in flow y! But flow y is also deleted so its ok to remove the connection.

So on your upgrade these flows will be removed

I've got 17 flows with dependency. So all these will be removed and re-added?

Jenefer-Monroe commented 1 week ago

Are referring to the 17 that you did the above workaround for? If so yes those are all the old v3 versions of the sync flows that used the old dataverse connector.

sakshiporwal95 commented 1 week ago

Flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowNeverPublished","message":"The workflow with id 'b677aa25-8de4-ed11-a7c7-0022480813ff' cannot be used as a child workflow because it has never been published. Child workflows need to be published at least once before they can be included in a published parent workflow."}}".

This is the new error we are seeing :( after fixing connection references

Jenefer-Monroe commented 1 week ago

Sorry what state are you in? Did you perform these steps already?

Delete the _Upgrade solution (if one was left behind)
Open all the flows above, delete most of whats in them, and resave
Do this until the connection reference no longer shows dependencies
Try the upgrade again

And if so did you boot the setup wizard? It will turn the flows on in the correct order.

sakshiporwal95 commented 1 week ago

I did followed all the steps but now when I am running set up wizard.

When trying to turn on : helper maker check , below is the error :(

Turn on failed. Flow client error returned with status code "Forbidden" and details "{"error":{"code":"ConnectionAuthorizationFailed","message":"The caller object id is 'd3bbb0b6-4e6b-4614-a883-3c3a4d98a153'. Connection 'admin_CoECoreO365Users' to 'shared_office365users' cannot be used to activate this flow, either because this is not a valid connection or because it is not a connection you have access permission for. Either replace the connection with a valid connection you can access or have the connection owner activate the flow, so the connection is shared with you in the context of this flow."}}".

Jenefer-Monroe commented 1 week ago

ok there is something wrong with your user then.

Are you logged in as the user that setup the kit? If not please do so and try again
If you are, please return to the connections suggestions above.

sakshiporwal95 commented 1 week ago

Most of the flows are Turned On, except admin sync template v4 | app, admin sync template v4 | flows.

flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowNeverPublished","message":"The workflow with id 'b677aa25-8de4-ed11-a7c7-0022480813ff' cannot be used as a child workflow because it has never been published. Child workflows need to be published at least once before they can be included in a published parent workflow."}}".

Also, how do I delete the upgraded solution to install the upgrade again.

Please help here , I really need to get this fixed today.

Jenefer-Monroe commented 1 week ago

ok sounds like you are still in a bit of an unknown state then.

Please follow these steps. I've included a screenshot form another bug on how to delete the _Upgrade

Delete the _Upgrade solution (if one was left behind)
Open all the flows above, delete most of whats in them, and resave
Do this until the connection reference no longer shows dependencies
Try the upgrade again

microsoft / coe-starter-kit