|
|
I'm rejecting this issue as "no change required" because I don't think we have to change the copy store process. However, maybe some additional discussion is needed, and maybe we need to report another issue in the BackOffice depending on the outcome of this discussion.
I believe the copy store module itself is working correctly in this case:
- When cloning an existing sequence, it would not make sense to consider the "Next assigned number" property, as the new sequence is supposed to start from the beginning, not from the point in which the existing sequence currently is.
- The question then, is what should be the beginning point, for each sequence. For this, it seems the sequence mechanism currently has a property called "Starting no", that is used in sequences that are restarted every year. The copy store is not only copying this property, but it is also using it to initialize newly cloned sequences. In general, I think this makes sense, as creating a new sequence is basically equivalent to reseting the current sequence, and as both sequences are supposed to be used for the same concept (but in different stores), it looks like it makes sense to initialize them like this.
- The tricky thing is how to configure this "starting no" column, as it is currently hidden in the backoffice. By default, it always receives the value 1000000. This is why when copy store copies a sequence, it always starts in 1M.
I think internally we should discuss if the "starting no" column should be visible always, as it would then allow users to configure this value, that I believe makes sense to be used by copy store for this. |
|
wwe.png (53,493) 2022-11-10 14:05