If the Number Generator Storage was flushed, the code to figure out the starting point for the sequence returned 0 for non-configure content types like e.g. Client
Desired behavior after PR is merged
The start of the sequence is calculated correctly
--
I confirm I have tested this PR thoroughly and coded it according to PEP8 standards.
Description of the issue/feature this PR addresses
Linked issue: https://github.com/bikalims/bika.lims/issues/2310
This is a post-fixture for PR: https://github.com/bikalims/bika.lims/pull/2311.
Current behavior before PR
If the Number Generator Storage was flushed, the code to figure out the starting point for the sequence returned 0 for non-configure content types like e.g.
Client
Desired behavior after PR is merged
The start of the sequence is calculated correctly
-- I confirm I have tested this PR thoroughly and coded it according to PEP8 standards.