Issue:
In the Sample Tracker, while receiving the assay results (file), on the last step, Finalise, you may get the error:
"
AN ERROR OCCURRED
The INSERT statement conflicted with the FOREIGN KEY constraint "ST_DESPATCH_STANDARD_FK2". The conflict occurred in database "GB_ DATABASE_DATA", table "dbo.ST_XS_STANDARD", column 'STANDARD_ID'.
The statement has been terminated.
------------------------------------------------------------------------------------------------
SAVE FAILED
------------------------------------------------------------------------------------------------
Summary
Skipped File : 1
- QC ASSAY PROCESS 12345.csv : The INSERT statement conflicted with the FOREIGN KEY constraint "ST_DESPATCH_STANDARD_FK2". The conflict occurred in database "GB_DATABASE_NAME", table "dbo.ST_XS_STANDARD", column 'STANDARD_ID'.
The statement has been terminated.
------------------------------------------------------------------------------------------------
Receipt Process Completed
"
Reason:
The table ST_DESPATCH_STANDARD has a foreign key constraint ST_DESPATCH_STANDARD_FK2, which only allows the insertion of STANDARD_IDs that already exist in the ST_XS_STANDARD table.
However, this constraint is currently being violated (according to the error message).
So, we are missing the particular standard specified in the loading file, which is not defined in the Metadata.
Solution:
You need to add definitions for all the standards presented in the loading assay files:
- Check if standards exist: SELECT * FROM [ST_XS_STANDARD] WHERE STANDARD_ID IN ([list of the received standards]).
- In Geobank, go to Metadata, then to Sample Tracker Metadata.
- Add missing standards to the Standards tab on the left frame using the [+] button on the right upper corner.
Note: It is a good practice to check that Sample metadata has everything supplied from the laboratory before loading the files (ST Receipt).
Want to learn more?
Online Help Manuals - Click here for the latest version
Learning Management System - Click here to login or here to request access
Comments
0 comments
Please sign in to leave a comment.