When your lab sends results to FarmQA automatically, every import is recorded in Settings › Logging. You can see whether all of a lab file came in, which samples didn't, and why, without checking your fields one by one. A partial import is easy to miss on the map, so check the log whenever results look incomplete or haven't appeared.
Each import is one row in the log with the source Soil lab import. This article covers reading those rows and what to do when an import doesn't fully succeed. For the log itself, including filtering and grouping, see Check the status of background operations.
| Action | Where | Who |
|---|---|---|
| Check a lab results import | Web | Enterprise Administrator |
For every role and what it can do, see Breakdown of user permissions.
If you don't see Logging under Settings, ask an Enterprise Administrator on your account to check the import for you.
Find the import
- Select Settings, then select Logging.
- In the Source column, filter to Soil lab import.
- Find the import by its Created date and time. The most recent imports are at the top.
Each row's Status tells you how the import went:
| Status | What it means |
|---|---|
| Successful | Every sample and measurement in the lab file imported. |
| Warning | Some of the lab file imported and some didn't. |
| Error | Nothing from the lab file imported. |
Read the import details
Select the row to open the Details pane. Only the details FarmQA has for that import appear.
- Lab: The lab that sent the results.
- Original filename: The lab file the results came from.
- Organization name, Field, and Work item: Where the results were matched, and the soil sampling task they belong to.
- Samples imported: How many samples came in, followed by a list of them.
- Samples unmatched: Samples FarmQA couldn't match to a sample in your account.
- Samples failed: Samples that matched but couldn't be saved.
- Measurements imported: How many individual results came in across all samples.
- Samples not imported: The samples that didn't come in.
- Message: The reason, when the import ended in a warning or an error.
- Event code: An identifier for this delivery from the lab. Include it if you contact support.
Fix an incomplete import
If the status is Warning, open the row and check Samples not imported and Message.
- If samples are unmatched, compare their sample IDs or barcodes with the ones on the soil sampling task. A barcode entered differently in the field and at the lab is the most common cause.
- To bring the missing samples in, upload them manually. See Upload soil test result using an import profile [LINK-3].
If the status is Error, nothing from that file came in. Upload the results manually using an import profile, or contact the FarmQA support team with the Event code and Created time from the row.
Future imports from the lab continue automatically after a failed one.
Frequently asked questions
Q: My lab says it sent results, but there's no row in the log. A: The log records results once they reach FarmQA. If there's no row, the results haven't arrived yet. Check with your lab that the file went to FarmQA, then contact support if it still doesn't appear.
Q: Do results I upload with an import profile show up here? A: No. The log records results your lab sends automatically. A manual upload shows its outcome when you finish the upload.
Related articles
- Automatic lab submission and results import
- Add a soil lab to your account
- View and export your soil data