Power Apps - Power Apps Pro Dev & ISV

Error: The DELETE statement conflicted with the REFERENCE constraint "appaction_appaction"

Like (1) Share

Report

Posted on 16 Oct 2024 20:28:12 by HaydnCoffee2024

In DEV I have removed custom commands and their command library to create a new one.

Since then I keep getting this error:

`The reason given was: Sql error: Statement conflicted with a constraint. The DELETE statement conflicted with the REFERENCE constraint "appaction_appaction". The conflict occurred in database "db_crmcoreemea_[...]", table "dbo.appactionBase", column 'ParentAppActionId'.`

I have tried removing dependencies and running tables separately, but no success.

Any help would be very welcome.

Categories:

Application Lifecycle Management (ALM)

All responses (2)

Answers (0)

HaydnCoffee2024 4 on 17 Oct 2024 at 07:52:22

Like (0)

Report

Error: The DELETE statement conflicted with the REFERENCE constraint "appaction_appaction"

I am working on a model driven app in a solution with several tables etc.

There were custom buttons on the command bar of one of the table that I have deleted/removed, including the Default Command Library associated with it.

All this works fine in DEV, all the buttons are gone and all the objects/records associated with it, it's clean and published.

When I run the DevOps pipeline to move the solution into another environment, the import works successfully.

But when the pipeline tries to upgrade the solution and attempts to delete the old command library, I get this error.

I have been checking the tables App Actions and App Elements, and dependencies around them, but with no success: it keeps telling me that the app actions associated with the command library that I want to remove cannot be deleted.
Suggested answer

Michael E. Gernaey 41,324 Super User 2025 Season 1 on 17 Oct 2024 at 06:52:23

Like (1)

Report

Error: The DELETE statement conflicted with the REFERENCE constraint "appaction_appaction"

Hi

I am not understanding what you are doing, as you simply showed an error, but not code or actions etc. We dont know your tables, they are yours, you have to share more than the above.