The Import Vineyard Event and Crop Estimates action allows you to create new vineyard events and crop estimates via a CSV file. You can create your own CSV file for importing or use the template provided here to get you started (recommended).
This article covers:
- Using the Import Vineyard Event and Crop Estimate Action
- Specifications for the CSV import file
- Troubleshooting the import
Using the Vineyard Event and Crop Estimate Import
- You can select "Import events and crop estimates" from the
button in the Vineyard Dashboard, Vineyard Details, and Block Details pages (anywhere you can create a vineyard action). - Click "Upload CSV" and choose your file to upload. Make sure the CSV file matches the required format exactly. We recommend using the example csv template within the action.
- Click "Import events and crop estimates."
Specifications for the CSV import file
- Each line of the CSV file represents either a single 'Vineyard Event', or a single "Crop Estimate." You can create new and backdated events via the import.
Tip: You cannot include both an event and an estimate on the same line.
- Files must be in the same format as the example CSV provided. Columns across the top, in order, include:
- Date
- Not required. If left blank, the event date will be recorded as of the upload date.
- If included, dates must in the following format: MM/DD/YYYY or YYYY-MM-DD
- Vineyard
- Required. Must match exactly the name of an existing vineyard in the winery.
- Block
- Required. Must match exactly the name of an existing block in the specified vineyard.
- Variety
- Required. Must match exactly the name of a variety in the specified block.
- Clone
- Only required if the Vineyard/Block/Variety combination has an existing clone.
- Leave blank if no clone currently exists for the block.
- Vintage
- Required. Must be 4-digit year (ex: 2019).
- Event or Crop Estimate
- Required. Must exactly match an existing event within the three main event types to specify a vineyard event, or, be "Crop Estimate," in order to record crop estimates.
- Required. Must exactly match an existing event within the three main event types to specify a vineyard event, or, be "Crop Estimate," in order to record crop estimates.
- Percentage (phenology)
- Required ONLY if the event type is an event within Phenology. Otherwise, this field must be blank.
- Crop Estimate
- Required ONLY if the event type is "Crop Estimate." Otherwise, this field must be blank.
- Crop Estimate Units
- Required ONLY if the event type is "Crop Estimate." Otherwise, this field must be blank.
- This field must match the weight units (tons, tonne or kg) associated with the account.
- Date
-
- Details
- Optional.
- Details
FAQs
Q. I can't get my file to upload! What should I try?
A. Please be sure to double check the following items:
- Make sure all details in the CSV file match your existing vineyards, blocks and varieties. Each line item must match to an existing, unique vineyard/block/variety/clone (or no clone) combination within InnoVint.
- Be sure you are uploading a .csv file
- Try changing the file type to CSV UTF-8
Q. Can I upload a .txt or .xls file instead?
A. Currently, we do not accept .txt or .xls files.
Q. I'm getting this error message:
A. You likely have a typo for an 'exact match' field, or you are missing required fields. Check the list of errors provided on the screen to troubleshoot any issues.