[BI-1927] - Entry Numbers Not Displaying #338
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Story: https://breedinginsight.atlassian.net/browse/BI-1927
Testing
The bug occurred with old data that lacked the
listEntryNumbers
key inadditionalInfo
. The fix allows the frontend to fall-back on theimportEntryNumber
, as the import file represents the first/original list. (When support was added to DeltaBreed for multiple lists per Germplasm, thelistEntryNumbers
key was added). I've tested creating new lists with old germplasm data and it works; the first/original list position is stored by theimportEntryNumber
, while the subsequent lists will uselistEntryNumbers
. When testing locally you can use BreedBase andChecklist: