While using the File Upload functionality, Envisio checks the file to ensure that it matches what the system expects to receive. If you have encountered any error messages, use this article to help understand how to edit your file. If you are still having troubles, please contact our support team.
Visit Using the Plan Upload Feature for information on how to create a plan by uploading a file.
Using this guide
This guide refers to the columns and spreadsheets provided in the template file (see article above). References to the sheets are in bold and columns are underlined. All columns in the spreadsheet marked with an asterisk * are mandatory.
Plan Elements
The following error messages are related to the first sheet (plan_element). Ensure that all mandatory fields are completed (number, description, and owner) and that the numbers use the following format:
- Goal 1
- Strategy 1.1
- Action 1.1.1
- Strategy 1.1
| Plan element: Missing plan elements data! | One of the mandatory fields (number, description, owner) is missing. |
| Plan element: Cannot find employee [#{email}]! | Email address provided in the spreadsheet does not match any of the email addresses in the Employees (users) section. Add the email address to Envisio, then upload the file again or assign the element to another person. |
| Plan element: Element number [#{element_number}] is invalid! | Formating issue with the element number. Check to make sure there are no extra periods or spaces. Follow the 1 or 1.1 or 1.1.1 convention for numbering. |
| Plan element: Duplicate element number [#{curr.join(".")}] is invalid! | One of the plan element numbers is already used. |
| Plan element: Missing element number between [#{prev.nil? ? "start" : prev.join(".")}] and [#{curr.join(".")}]! | Element numbers must be sequential (e.g.- 1.1.1, 1.1.2, 1.1.3, etc.). |
| Plan element: Start date [#{start_date}] needs to be before end date [#{end_date}] ! | The start date must be before the end date. |
Plan Element Assignments
The following error messages are related to the second sheet (plan_element_assignments). Filling in this sheet is optional and used to assign contributors. If you are assigning contributors, use one row per contributor.
| Plan element assignment: Cannot find employee [#{email}]! | Email address provided in the spreadsheet does not match any of the email addresses in the Employees (users) section. Add the email address to Envisio, then upload the file again or assign the element to another person. |
| Plan element assignment: Plan node number [#{number}] is invalid! | Formating issue with the element number. Check to make sure there are no extra periods or spaces. Follow the 1 or 1.1 or 1.1.1 convention for numbering. |
| Plan element assignment: Owner/contributor/observer emails need to be unique for plan node number [#{number}]! | Use one row per element per contributor. If you want to assign 3 contributors to an action, there should be 3 rows– one for each contributor or observer. |
Checklist Items
The following error messages are related to the third sheet (checklist_items). Filling in this sheet is optional and used to assign checklists to actions. Make sure that on the plan_element sheet that you have specified that the action has a checklist (set the Checklist Weighting Type field for that row).
| Checklist item: Plan node number [#{number}] is invalid! | Formating issue with the element number. Check to make sure there are no extra periods or spaces. Follow the 1 or 1.1 or 1.1.1 convention for numbering. |
| Checklist item: Checklist item weight cannot be 0 for manual weighting lists! | Manual weighting checklist items must add to 100 and each checklist item needs a weight assigned. |
| Checklist item: Missing plan node number [#{number}]! | All of the rows in checklist_items must have a number that relates to one of the rows in plan_elements. The row in plan_element must have a checklist option set in Checklist Weighting Type. |
| Checklist item: Checklist items need to be unique for plan node number [#{number}]! | Checklist items must be unique when on the same element. |
| Checklist item: Checklist item weight need to add up to 100% for manual weighting lists. Plan node number [#{number}]! | The checklist must add to 100 and each checklist item needs a weight assigned. |
Custom Fields
The following error messages are related to the fourth sheet (custom_field_records). Filling in this sheet is optional and used to populate custom fields. Custom fields must be created on the plan settings before using the file upload and must match exactly.
| Custom field record: Plan node number [#{number}] is invalid! | One of the plan element numbers in the Number column is incorrect. Double check the formatting to ensure it matches what is on the plan_elements page. |
| Custom field record: Custom field [#{field_name}] is invalid! | The Field Name does not match the custom fields configured in the plan settings. Please make sure this matches exactly to the field you'd like to use for the upload (copy & paste). |
| Custom field record: Text field [#{field_name}] cannot exceed #{::CustomField::MAX_TEXT_FIELD_LENGTH} characters! | Ensure that the values for the custom fields do not surpass the character count limit configured in your plan settings. |
| Custom field record: Text field [#{field_name}] is required! | If using a mandatory custom field, make sure that the Content is populated upon import. |
| Custom field record: RichText field [#{field_name}] is required! | If using a mandatory custom field, make sure that the Content is populated upon import. |
| Custom field record: Number field [#{field_name}] is not number! | The Content entered is not a number, custom fields using the Number type must have number values. |
| Custom field record: Number field [#{field_name}] is required! | If using a mandatory custom field, make sure that the Content is populated upon import. |
| Custom field record: Single select picklist field [#{field_name}] has invalid items! | The Picklist Items contains a value that is not valid. Make sure the value matches one of the options configured for that custom field (copy & paste). |
| Custom field record: Single select picklist field [#{field_name}] has multiple selections! | Too many options are selected for the Single Select Picklist, only enter one value for the Picklist Items of this field. |
| Custom field record: Single select picklist field [#{field_name}] is required! | If using a mandatory custom field, make sure that the Picklist Items is populated upon import. |
| Custom field record: Multi select picklist field [#{field_name}] has invalid items! | If using a mandatory custom field, make sure that the Picklist Items is populated upon import. |
| Custom field record: Multi select picklist field [#{field_name}] has duplicate items! | There is a repeat option in the multi-select– all selected options inputted into the Picklist Items must be unique. |
| Custom field record: Multi select picklist field [#{field_name}] is required! | If using a mandatory custom field, make sure that the Picklist Items is populated upon import. |
| Custom field record: Missing required fields for plan node number [#{number}]: [#{missing.join(", ")}]! | If using a mandatory custom field, make sure that the value is populated upon import. |
| Custom field record: Duplicate fields for plan node number [#{number}]: [#{duplicates.join(", ")}]! | The custom field is being set in duplicate rows, make sure that it is only being populated once. |
Comments
0 comments
Please sign in to leave a comment.