Story Number Sequence gets changed and following the numbering from PROD instance after Cloning

[Ankit67]

We have cloned from PROD to TEST instance recently. I noticed that before cloning last Story Number created is STRY0139794. After cloning first Story created is STRY0130947.

The numbering has started according to Story numbers on PROD. Right now it is following the sequencing of the Story No. from PROD but we need to Preserve same Story Sequence No. what we have maintained in TEST instance. Any idea on this issue?

[Maik Skoddow]

Hi

Open module "Number maintenance" and fix the respective record 

Maik

[Laszlo Balla · Accepted solution]

As a quick fix, you can go to the sys_number_counter list, search for the story table, and set the next number (the value in the number field) manually.

Otherwise, you should consider preserving this record in this table as part of your next clone. If you decide to exclude this table entire from a clone, make sure you preserver all records, otherwise the table will end up being empty, and I imagine that might cause some issues (tough I have never tried). Proceed with caution 🙂

[adrian08]

Dear community,

I have a different problem here. We carry over records from PROD to DEV every cloneback. The problem is the number counter (sys_number_counter) is not updated. We basically need to update all sys_number_counter from PROD to DEV. How do we do this automatically during cloneback? Or do we have to do this manually?