Duplication Key Error When Using Custom Number Sequence

(0) Share

Report

Posted on by TNGrizzly

Hey D365FO community!

I hope you're all doing well. I'm currently working on a project in D365FO as a developer, and I've hit a roadblock that I could use some assistance with. Here's a breakdown of the issue:

**The Problem:**

I created a custom number sequence and linked it as an index for a new table. Initially, everything seemed to be working fine. However, I'm now encountering a duplication key error that I can't seem to resolve.

**What I've Tried So Far:**

I've attempted to delete all records associated with this number sequence and even created a new one from scratch, but the error persists.

I delete the key and it didntt solve the prblm

It seems like there's an underlying issue that I haven't been able to identify.

**Additional Information:**

To provide more context, here are some additional details:

- I make sure that no other insert or doinsert call are done before

I'm open to any suggestions or insights you may have. Thanks in advance for your help!

I have the same question (0)

All responses (1)

Answers (1)

Verified answer

Martin Dráb 237,668 Most Valuable Professional on at

Like (1)

Report

Duplication Key Error When Using Custom Number Sequence

I suggest the following:

1. Stop in debugger in insert().

2. Open SSMS and check out if the value already exists in database. If so, it means that you number sequence conflicts with existing data.

3. If you don't see it in committed data, try uncommitted (e.g. by WITH (NOLOCK)). If so, it seems that the same value is inserted twice in the same transaction.

4. If nothing is there, you probably have a problem with a different unique index. The error message mentions a field from the primary index, but the actually conflicting index may be different.

Was this reply helpful? Yes No