[4.2] - Auto Number field does not get the correct number

Posted by IramK on 20-Sep-2016 06:02

Hello,

I have an auto number field called "case number". Whenever I am importing new records, the "starting number" field value gets updated to the correct number but when I try to create a new record it still tries to create a record with a number that is already used. May I know when this issue would be fixed please?

Cheers.

Iram

Posted by Saraswathi Krishnan on 14-Dec-2016 07:23

It has been fixed in the 4.4 release.

Regards,

Saras

All Replies

Posted by IramK on 20-Sep-2016 06:18

And every time I refresh the new page, the case number field value keeps incrementing.

Posted by Santosh Patel on 28-Sep-2016 01:12

Is the casenumber part of the import?

Can you share a sample import file?

"And every time I refresh the new page, the case number field value keeps incrementing."

This is by design. Auto number fields can be part of the New Page and hence need to be pre-assigned (hence, marked as consumed) for a particular request. So all parallel requests by users get unique auto numbers.

Another strategy would be to never show the number, in which case the number would be assigned when actually successfully creating a record. We have not chosen this strategy.

Posted by IramK on 28-Sep-2016 08:50

Hello [mention:7e24e60fbecc4ff8baf4669a65bae0a0:e9ed411860ed4f2ba0265705b8793d05],

Yes the case number is a part of the import. I have attached a sample import file for you to have a look, it doesn't have many records but I'm sure you'll get the idea.

Yes but despite pre-assigning auto number field value, it retains the old value (it thinks is still available which isn't) and allows me to enter information and upon clicking save, it alerts by saying that the case number is already taken.

Iram

Posted by Santosh Patel on 28-Sep-2016 22:08

I don't see the sample file.

Posted by Saraswathi Krishnan on 29-Sep-2016 03:53

The bug has been logged for the reported issue - #54736

Posted by IramK on 13-Dec-2016 04:03

[mention:84d458308cc54f429f660536194c00ae:e9ed411860ed4f2ba0265705b8793d05] ,

Thanks. Any updates on a fix date for this or has this been fixed already?

Iram

Posted by Saraswathi Krishnan on 14-Dec-2016 07:23

It has been fixed in the 4.4 release.

Regards,

Saras

This thread is closed