[Michael Carrick]

We are using AX-2012 R3, and we keep having a situation where users get an error message when they try to make a contact. The error message is the standard “Cannot create a record in Contacts (ContactPerson). Contact ID: CID1022781. The record already exists.”

The contact number cited in the error message changes with each instance, of course, but the rest is the same. The above example is the latest one that occurred. 

The error message occurred because the value on the error message was BOTH already used on an existing contact AND also marked as free in the status list for the corresponding number sequence.

This happens regularly, though thankfully (not yet) frequently.

I am wondering if someone can help me understand what the cause of this situation is. I had thought that EITHER the number value would be used for an existing contact OR it would be available as ‘Free’ in the status list.

The attached screenshots outline the issue in more detail.

If anyone has any insights to offer, I would greatly appreciate it. 

Thanks very much, and have a great day! 🙂

Mike Carrick
Business Analyst – Applications
Secure Energy Services

——————————
Mike Carrick
Secure Energy Services
Calgary
——————————

[Andrew Ford]

Mike,

Have you tried unchecking the  Continuous checkbox?  

My best guess at the cause would be customization that does not mark the number used after getting it, either by design or by lack of (/customized breading of) TTS control.  Clearing the Continuous box would resolve this problem (Next number is 22782, the system is only trying to backfill 22781because the sequence is marked continuous).  

From the link below: “Unless there is a regulatory requirement that you use continuous number sequences, we recommend that you use non-continuous number sequences for better performance. “

Number sequence overview [AX 2012] 

——————————
Andrew Ford
Lead AX Developer
Nivel Parts & Manufacturing Co., LLC
Jacksonville FL
——————————
——————————————-

[Zvika Rimalt]

you know, a smart person can get out of trouble a wise person would have not gotten into in the first place…

your number sequence is marked as “continuous” – does that serve any actual business requirements?

There are very few functionalities where it is actually required by the system to use continuous sequence.

Rather than struggle with the various bugs and peculiarities of number sequences behavior with “continuous” maybe just turn off that “feature”?

——————————
Zvika Rimalt
Functional Consultant
Vancouver BC
——————————
——————————————-