[CoE Starter Kit - BUG] Upgrade Failed with Error code 80047009 - Cannot delete attribute: admin_aibuildermodelid from Entity: admin_AiBuilderModel since the attribute is not a custom field

[jitendra-bhagwat-insight]

Does this bug already exist in our backlog?

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

Describe the issue

While upgrading CoE starter kit Core Components from version 4.31 to version 4.97 the import failed with following error
Error code 80047009 - Cannot delete attribute: admin_aibuildermodelid from Entity: admin_AiBuilderModel since the attribute is not a custom field
Activity ID - 9cf8d8b8-8173-4740-8a08-5eb4892f3c2c

Expected Behavior

Expected behavior is to Import of Core Components to be successful.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.37

What app or flow are you having the issue with?

NA

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

1. CoE starter kit with version 4.31 to be ready for upgrade
2. Import latest Core Components Solution (version 4.37)

Anything else?

[Jenefer-Monroe]

Hello. I'm afraid you've hit some kind of product bug here.
That field has not been deleted from the solution. Here it is, in the August relesae.

You can try doing a update instead of an upgrade to work around this.

[jukkan]

I just experienced this exact same error, with the same 4.31 -> 4.37 upgrade. The import process ran for 1h 17min before crashing into this. Could definitely be a platform issue as well, I'll try it again to see if it goes through.

[Jenefer-Monroe]

I just tested 4.34 to 4.37 in the preview region and it worked.
I can test 4.31 to 4.37 but my test case for that is in US region. What region are you folks?

[jukkan]

EMEA. It now went through in 30min when using the Update option.

[Jenefer-Monroe]

ok great to know. Thats a good work around for now, to use update.
ill let you know how my test case goes in US

[Jenefer-Monroe]

4.31 to 4.37 worked for me in US region. There appears to be some intermittent issue with product upgrade.

Jukka has confirmed that Update works as a workaround for now

[jitendra-bhagwat-insight]

Thank you @Jenefer-Monroe @jukkan
I am in Aus not sure if that is in EMEA or Oceania region :)
For time being I will go with the workaround 'Update' instead of 'Upgrade' and will report the outcome here.

[jitendra-bhagwat-insight]

Confirming - the workaround is successful and am able to update Core Components from 4.31 to 4.37

[Jenefer-Monroe]

Another user with another field also not removed in #8848

Would be great if you folks could create support tickets.

[jitendra-bhagwat-insight]

Another user with another field also not removed in #8848

Would be great if you folks could create support tickets.

Can you please assist with link or steps to raise support ticket?
Also, should I close (as completed) this ticket?
Thank you!

[Jenefer-Monroe]

How you raise a ticket depends on your tenant and role. But here is the starter link from the product team:
https://learn.microsoft.com/power-platform/admin/get-help-support

Let's leave this open a few days so we can see how wide spread the issue is.
Thanks!

[Jenefer-Monroe]

similar repro with different table #8870

[Jenefer-Monroe]

Marking as product bug and assigning to Grant to press as this is occurring for multiple tables
And it appears there is also a capacity issue to contend with as a result of upgrade being broken here, see #8854

Folks in this thread please take a look at the capacity of the environment and see if you have issues similar to those described in #8854

[Jenefer-Monroe]

Another user found a way around this as follows:

[shmcarth]

There was a regression in the solution framework that is fixed. It will be completed rollout worldwide by this weekend. Please retry.