Closed AstridBVW closed 4 days ago
Debugging version 1.2.0 I could not reproduce the phenomenon as it immediately saves the whole value upon the first save:
@AstridBVW Could you please test again in version 1.2.0 ?
NOTE: I did not have a "controlled vocabulary data matrix" to use, so maybe that is the factor that makes a difference here...
Check latest version of App and try and reproduce with and without data matrix
I have assigned this to @RebekkaML instead. She is familiar with this ticket and have a version of the app on her computer that she can use for testing (I have a mac).
I tested this in version 1.2.0 and could not reproduce this error there either. I tried it both with the "controlled vocabulary data matrix" and by typing the comment manually, and both worked fine. It also didn't make a difference whether I entered the comment first and then the barcode or entered the barcode, saved it and the clicked "GO BACK" to enter the comment, it appeared correctly in the database in all cases. It appears this bug was fixed with the latest version of the app.
Describe the bug While digitising we are having problems with information added to the notes field in the digi app not being saved even though the "SAVE" button is used.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expected all of the information in the notes field to be saved by clicking on the "SAVE" button once.
Screenshots
Please complete the following information:
Additional context The steps above are what happened while I was digitising (AstridBVW). I also tried adding information to the notes field BEFORE scanning the barcode and then the information was saved correctly. @RebekkaML also looked into this while digitising and figured out some more. She found the same as me when adding information to the notes field and then scanning the barcode, but she also found that if you scan the barcode, click "GO BACK", add the information to the notes field, move the cursor to the barcode field and then click"SAVE", it saves correctly. So it seems to be a problem relating to some rule about the barcode field and saving.