Finance | Project Operations, Human Resources, ...

Existing unique index changed may cause unique index violation

(0) Share

Report

Posted on by Senthil Yadav

492

Hello Team,

We are facing the Error for Unique Index Changed in CustInvoiceTable, CustInvoiceTrans and CustPackingSlipTrans. Please see below snap for your perusal.

Please help us to resolve the issue ASAP. Thank You.

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi Senthil,

it's actually a warning, not an error. You will see errors in the "Error" tab. Not sure what changes you have made in the table. But generally you don't need to care about this warning.

Was this reply helpful? Yes No
Senthil Yadav 492 on at

Like (0)

Report

Hello Nikolaos,

Thanks for the quick response. But users are not able to post the Invoices, while posting invoice Error message is displayed as shown in below snap.

Please suggest.

Was this reply helpful? Yes No
nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi Senthil,

this seems to be some new problem that you didn't mention at all in your initial message.

I don't understand what is the relation between this problem and your original post.

I think it would be good if you could start by sharing as much information about your situation as possible.

Thanks!

Was this reply helpful? Yes No
Senthil Yadav 492 on at

Like (0)

Report

Hello Nikolaos,

The first Warning message is displayed when i synchronize the Tables CustInvoiceTable, CustInvoiceTrans and CustPackingSlipTrans. I did not click on continue but clicked on Cancel and proceeded further. Now when the users are trying to post invoices the second snap error message is displayed on user screen that SQL Server Database has an issue related to CustInvoiceTrans Table. How can i over come this error for Unique Indexes and Index Violation. We want to post the Sales Invoice Transaction smoothly. Please suggest. Thank You.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Most likely the runtime error (that users are seeing) happens because you haven't done database synchronization since last changing something in your data model.

When updating your prod system with latest code, you must always run a succesful database sync (well, to be precise, it's only needed if you have some data model changes). You can't let users resume using the system until the update is finished succesfully. I recommend that you review - and if necessary - adjust your prod deployment process to avoid similar issues in the future.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Senthil,

Are there any changes done on the listed tables? I would recommend to review changes and test in a separate environment (copy of the current production) if the DB sync will be successful. As it mentioned a changed primary index, I would act careful and not directly do it in production. Haven't you seen the same issue when moving objects from DEV to an acceptance test environment?

Was this reply helpful? Yes No
Senthil Yadav 492 on at

Like (0)

Report

Hello Andre,

It successfully went through in the Copy of LIVE server, we first tested in from DEV to COPY of LIVE Server there it was successfully populated and no error messages. This is happening in LIVE server. Can you please tell what can be done now to resolve this issue. Thank You.

Was this reply helpful? Yes No
Senthil Yadav 492 on at

Like (0)

Report

Hello Nikolaos,

We did the Synchronization after importing from DEV environment, but still the same error was being displayed. Please let us know the resolution. Thank You.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

It's still a warning, not an error. Assuming you talk about the original issue from your initial question.

Anyway, you need to identify what changes you have made in the system since the last time when you didn't have this issue. It should be easy since you do db sync whenever you deploy new changes to test/prod.

We don't know how you manage your deployments, but either you know, or someone in your organization knows the process. Talk with them. You need to solve it with people who know what has been changed.

Finally, once it's solved, review and adjust your deployment process to prevent it from happening again. This kind of issue should always be noticed in test system, or very latest during deployment to prod.

Was this reply helpful? Yes No