Accidental duplicates due to missing zero-padding

Get Help
1

Hi there,
occasionally our volunteers/interns produce the following situation, which prevents adding any new collection objects to our database.

They most likely edit or clone an object and somehow manage to save it without the leading zeros which creates duplication in our system.

duplicate_no_leading_zeros
duplicate_no_leading_zeros1198×216 42.3 KB

We use the default CatalogNumberNumeric format, so it shouldn’t happen, but somehow it is still happening time to time and then it’s blocking the whole system, until we find and delete the duplicated catalog number without the leading zeros.

default_catno_numeric_9digits
default_catno_numeric_9digits1123×349 70.4 KB

It might be a bug or some misconfiguration on our end, either way it would be nice to prevent it in the future. :slight_smile:

Let us know if you bumped into this problem before/you have an idea how to fix it!
Thank you!
/Zsuzsanna

Specify 7 System Information - 2026-01-29T13_51_12.177Z.txt (4.8 MB)

2

Hi @ZsPapp,

Thanks for your screenshots and explanation! I am tracking this issue on GitHub now (#7388) and I’ve added your report to it as well. We are still determining the best solution to resolve this.

From what I can tell, this is only possible when using ‘Carry Forward’ or ‘Clone.’ However, I cannot recreate the scenario in which this occurs. If you discover a consistent method for reproducing this, please let us know!

3

Thank you @Grant, for looking into this!
I’m also not able to reproduce this error, since whenever I try to create a catalog number without padding zeros, it is automatically fixed to have the proper format.
Though, some of our colleagues and interns managed to bump into this scenario several times. We keep on eye on it and let you know, if we have further information!

1 Like