PowerApps solution update not accepting new tables - wants to delete attribute

[AOuellette]

Hi everyone,

For a few days now whenever is try to add a table to my solution and send it to the production environnement, it gives me the following error before cancelling the update:

"Failed to import solution "PlanificationArmature": ImportAsHolding failed with exception: Cannot delete attribute utcconversiontimezonecode from Entity: aoop_tbl_PA_test since the attribute is not a custom field."

A few important points:

1- Everything works great in the development environnement

2- The production environnement accepts the update file at first and stops the update after a few minutes, giving this message

3- It only does it to new tables (i had to delete 3 new tables and then tried this test one without adding any column or making any changes)

4- Last week I changed the format of a date in another table from "date only - user local date" to "date only - date only"

5- Updating the solution caused no issue after I removed the new tables

6- The database is entirely on Dataverse tables

I hope someone can help me figure this one out!

Best regards,

Alex

[sathan]

Same here. Don't know why, I'm investigating.

[Devvj]

Hi @AOuellette
Are you able to try to run an upgrade instead of a update and see if that works?
It is usually a more clean approach, since it deletes stuff that are no longer in the solution. 

[sathan]

For me, I am always upgrading. Still the same problem.

[sathan · Accepted solution]

Found a solution :

Import your solution as an update. It should go through.

Then republish your solution as a new version, then import as upgrade.

Fixed it for me. Still not the best, but I raised an internal support request with the Power Apps team so they could look more into it.

Hope it helps.

[AOuellette]

This seems to be the way to fix it!

Thanks a lot!

[sathan]

For your information, this is the update I got from the Product Team :

I wanted to update that we have an update from our PG team, and they confirmed that this issue was happening due to a regression, and we already have a fix in place for this issue which is planned to be deployed in your environment this weekend. According to the PG team you can try from next week and solution upgrade should also work as expected.

Bon succès dans tes projets 🙂