The file is not read as a certificate
Batch checks lists the file as Not read, and the report under it gives one of these messages.
“isn’t a laboratory certificate the app can read. It reads SIF files, comma-separated or fixed width.”
Cause: the app looks for the certificate number on the first line and the header rows under it, such as CLIENT and # of SAMPLES. It did not find that layout.
What to check:
- Open the file in a text editor, not Excel. The first line should be the certificate number, with Finalized or Preliminary beside it. If the file starts with column headings, it is an export, not a certificate. Ask the lab for the SIF file.
- If the file was opened and saved in Excel, ask the lab for the original. Excel changes dates and quotes.
- If it is a PDF or an Excel workbook, the app cannot read it. The lab’s SIF export is the file to use.
“is empty or too short to be a laboratory certificate.”
Cause: the file has fewer than three lines. It is empty, or it was cut short on the way.
What to check: the file’s size. Download it from the lab again.
“has no method and element rows above its results.”
Cause: the app found the header rows but not the blank line that ends them, or the method and element rows under it.
What to check: open the file in a text editor. After the header rows there should be a blank line, then rows with each column’s method, element, unit and detection limit. A certificate without them cannot be checked, because the app would not know what each column holds.
“has no result columns, because its element row is empty.”
Cause: the element row is there but holds nothing.
What to check: ask the lab for the certificate again. If every certificate from this lab reads this way, send one to us from the Feedback tab and we add the layout.
If the file is inside a zip
A zip is read file by file. One that is not a certificate is listed as Not read and the rest are checked.