Duplicate Entry / process run twice

RE: Duplicate Entry / process run twice

manjit.1486 — Wed, 18 Sep 2024 18:48:19 GMT

Thank you so much. I will try to do this and get back to you.

RE: Duplicate Entry / process run twice

mathurambika0708 — Wed, 18 Sep 2024 18:47:25 GMT

Deleting the unique constraint is the solution here, as it allows for the insertion of multiple cases for an employee, regardless of where the data is coming from.

RE: Duplicate Entry / process run twice

manjit.1486 — Wed, 18 Sep 2024 18:44:21 GMT

yes, I didn't create before. But data is coming from somewhere else.

RE: Duplicate Entry / process run twice

mathurambika0708 — Wed, 18 Sep 2024 18:42:39 GMT

Okay, then you need to remove/delete the unique constraint from the 'EmpID' column in the 'EMP_CASE' table. It didn't happen before, and my guess is that you might not have created multiple cases for an employee.

RE: Duplicate Entry / process run twice

manjit.1486 — Wed, 18 Sep 2024 18:37:11 GMT

One more thing, this didn't happen before. It starts throwing error suddenly

RE: Duplicate Entry / process run twice

manjit.1486 — Wed, 18 Sep 2024 18:32:57 GMT

Yes, this is a unique key in table. This is one to many relationship

RE: Duplicate Entry / process run twice

mathurambika0708 — Tue, 17 Sep 2024 21:57:34 GMT

May I ask why the 'EmpID' is configured as a unique key column in the Employee case table?

Since it is a unique key, it will prevent the insertion of case details with the same employee ID multiple times, meaning multiple cases cannot be created for or by the same employee. If the relationship is intended to be one-to-one, this makes sense. Otherwise, I would suggest removing the unique key constraint from the 'EmpID' column in the Employee case table.

RE: Duplicate Entry / process run twice

manjit.1486 — Tue, 17 Sep 2024 21:00:15 GMT

EmpID is unique key in this table.
ID is autoincremented. It is unique also.

RE: Duplicate Entry / process run twice

mathurambika0708 — Tue, 17 Sep 2024 20:02:25 GMT

Hi Manjit,

I believe 'EmpID' is a foreign key in the 'EMP_CASE' table. If that's the case, could you verify whether a 'UNIQUE' key constraint has been added to this column? Since this is a one-to-many relationship, where multiple cases can be raised for an employee, the unique key constraint is not required and can be removed if it has been added

RE: Duplicate Entry / process run twice

manjit.1486 — Tue, 17 Sep 2024 17:33:21 GMT

Primary key

RE: Duplicate Entry / process run twice

manjit.1486 — Tue, 17 Sep 2024 17:32:35 GMT

Yes. But MNI is not configured

RE: Duplicate Entry / process run twice

Soma — Tue, 17 Sep 2024 17:02:03 GMT

What is the nature of EmpId column? Is it a foreign key?

RE: Duplicate Entry / process run twice

GauravSingh — Tue, 17 Sep 2024 17:00:13 GMT

Are you seeing multiple instance getting created when you run this process ? If yes, its quite possible that your process is configured as MNI.

RE: Duplicate Entry / process run twice

Soma — Tue, 17 Sep 2024 16:51:06 GMT

Did you try checking the logs for more information?

RE: Duplicate Entry / process run twice

manjit.1486 — Tue, 17 Sep 2024 16:47:15 GMT

Highlighted one is autoincrement ID column and next one is EmpId column.

RE: Duplicate Entry / process run twice

GauravSingh — Tue, 17 Sep 2024 16:44:23 GMT

Verify if the last record in DB and the Sequence is same or not. If not you will keep on getting this error.

You can google to set the index in DB.

RE: Duplicate Entry / process run twice

manjit.1486 — Tue, 17 Sep 2024 16:41:37 GMT

Yes, DB already has record against 229.

RE: Duplicate Entry / process run twice

GauravSingh — Tue, 17 Sep 2024 16:40:03 GMT

Could you check and confirm if your DB has value already stored for EmpID: 229.

This happens when you have used auto increment in Appian and Database Sequence has already passed that value or contains some value for given sequence.