INSERT statement conflicted with the FOREIGN KEY constraint - SQL Server

I used code-first migrations to build my database for an MVC 5 application. The seed method in my configuration.cs file was causing the issue, creating a table entry for the table containing the foreign key before creating the entry with the matching primary key.

1. run sp_helpconstraint
2. pay attention to the constraint_keys column returned for the foreign key

That error means that the table you are inserting data into has a foreign key relationship with another table. Before data can be inserted, the value in the foreign key field **must** exist in the other table first.

The error you're encountering is due to a violation of the FOREIGN KEY constraint `FK_Sup_Item_Sup_Item_Cat` when attempting to insert a value into the client_id column of the sup_item table. The error message indicates that the value you're trying to insert does not exist in the referenced table Sup_Item_Cat in the dev_bo database.

To resolve this issue, you should ensure that the value you're inserting into the client_id column matches an existing value in the referenced table Sup_Item_Cat. You can verify the available values in the `Sup_Item_Cat` table and make sure you're providing a valid client_id.

Here's an example query to retrieve the existing client_id values from the Sup_Item_Cat table:

SELECT client_id
FROM dbo.Sup_Item_Cat;

Review the output of this query and confirm that the value you're trying to insert into the client_id column exists in the `Sup_Item_Cat` table.

[![enter image description here][1]][1]

To identify which other tables and columns a particular table depends on, you can use the information from the Keys folder and Depends on [dbForge Studio for SQL Server.][2]


[1]:

[2]:

[To see links please register here]

I experienced same issue while running the query:

```
INSERT INTO [dbo].[work_flow_actions] ([work_flow_id] ,[actions_id]) VALUES (70004, 150044)
```

Meanwhile, I confirmed that the values 70004 and 150044 exist in the corresponding tables.

I fixed this by including the database name as follows:

```
INSERT INTO [TIS].[dbo].[work_flow_actions] ([work_flow_id] ,[actions_id]) VALUES (70004, 150044)
```