In “Troubleshooting bulk imports via CSV in HighLevel Support Portal,” you’ll find a comprehensive guide to tackling any issues you may encounter while importing contacts in bulk via CSV. This informative video tutorial walks you through the process of navigating error logs and resolving errors that may arise during a contact import bulk action. From formatting mistakes to invalid property values and duplicate contact IDs, this troubleshooting resource covers it all. Additionally, you’ll discover the list of supported timezones for importing and the necessary custom field format requirements for a seamless import process.
This image is property of images.pexels.com.
Troubleshooting bulk imports via CSV in HighLevel Support Portal
Importing contacts in bulk via a CSV file can be a convenient way to add or update multiple contacts at once in the HighLevel Support Portal. However, it is possible to encounter various errors and issues during this process. In this article, we will guide you through the troubleshooting steps for common problems that may arise during bulk imports.
Formatting mistakes
One of the most common errors that can occur during a bulk import is formatting mistakes in the CSV file. These mistakes can include incorrect column headers, mismatched data types, or improperly formatted values. To resolve this issue, carefully review the CSV file and ensure that the formatting is correct. Make sure that the column headers match the expected format and that the data in each column is in the appropriate format as well.
Multiple owners
If you encounter an error regarding multiple owners, it means that there are conflicting owner information for a contact. This can happen when multiple columns or fields in the CSV file contain owner information. To resolve this error, review the CSV file and ensure that there is only one column or field designated for owner information. Remove any duplicate or conflicting owner data, and try the import again.
Invalid sheet count
If you receive an error message indicating an invalid sheet count, it means that the CSV file contains more sheets or tabs than what is allowed for a bulk import. The HighLevel Support Portal only allows a specific number of sheets to be imported at once. To fix this issue, check the CSV file and make sure that it contains the correct number of sheets. If there are extra sheets, remove them and try the import again.
Invalid required property
An invalid required property error occurs when a required field is missing or has an incorrect value in the CSV file. To address this error, review the CSV file and ensure that all required fields are included and populated with the correct information. Double-check the formatting and spelling of each required property to ensure accuracy.
Invalid enumeration option
If you come across an error related to an invalid enumeration option, it means that a field in the CSV file contains an option that is not recognized or accepted by the HighLevel Support Portal. To troubleshoot this issue, verify the available options for the field in question and make sure that the values in the CSV file align with those options. Correct any incorrect or unrecognized options and try the import again.
Invalid contact ID
An error regarding an invalid contact ID indicates that the contact ID specified in the CSV file does not exist or is incorrect. To resolve this issue, verify the contact ID and cross-reference it with the existing contacts in the HighLevel Support Portal. If the contact ID is indeed invalid, correct it in the CSV file and try the import again.
File not found
If you receive a “file not found” error, it means that the system could not locate the CSV file for the bulk import. To troubleshoot this issue, double-check the file path and ensure that the CSV file exists in the specified location. If the file is located in a different directory or location, update the file path accordingly and try the import again.
Failed validation of email
A failed validation of email error occurs when an email address in the CSV file is not in the correct format or is invalid. To address this issue, review the email addresses in the CSV file and verify that they follow the proper email format. Make sure there are no typos, missing characters, or extra spaces in the email addresses. Correct any errors and try the import again.
Empty unique property value
If you encounter an error regarding an empty unique property value, it means that a required unique property in the CSV file is either missing or has no value. Unique properties are used to identify and differentiate contacts, so they cannot be left empty. To resolve this issue, review the CSV file and ensure that all unique properties have valid values. Fill in any missing values or remove the empty unique property entirely if it is not required.
Duplicate unique property value
A duplicate unique property value error occurs when there are multiple contacts in the CSV file with the same value for a unique property. Unique properties must be unique to each contact, so duplicates are not allowed. To fix this issue, review the CSV file and ensure that each contact has a unique value for the specified unique property. Remove any duplicate values and try the import again.
Duplicate contact ID
If you receive an error message about a duplicate contact ID, it means that there are multiple contacts in the CSV file with the same contact ID. Each contact ID must be unique to avoid conflicts. To address this error, review the CSV file and ensure that each contact has a unique contact ID. Remove any duplicate contact IDs and try the import again.
Could not parse the phone number
An error stating that the phone number could not be parsed indicates that the phone number format in the CSV file is incorrect or cannot be understood. To resolve this issue, review the phone numbers in the CSV file and ensure that they are in the correct format. Remove any special characters, spaces, or extra digits that may be causing parsing errors.
Could not parse the date
A “could not parse the date” error occurs when a date value in the CSV file is not in the correct format or cannot be interpreted as a valid date. To troubleshoot this issue, review the date values in the CSV file and ensure that they follow the specified date format. Correct any formatting errors or mismatches and try the import again.
Could not find the owner
If you encounter an error indicating that the owner could not be found, it means that the specified owner in the CSV file does not exist or is incorrect. To resolve this issue, verify the owner information and cross-reference it with the existing owners in the HighLevel Support Portal. If the owner does not exist or is incorrect, correct the information in the CSV file and try the import again.
Ambiguous enumeration option
An ambiguous enumeration option error occurs when a field in the CSV file contains an option that can be interpreted in multiple ways. This ambiguity can lead to errors and conflicts during the import process. To troubleshoot this issue, review the options in the CSV file and ensure that they are clear and unambiguous. If needed, provide additional clarification or specificity to avoid any ambiguities.
Location does not allow duplicate contacts
If you receive an error message stating that the location does not allow duplicate contacts, it means that the specified location in the CSV file has a restriction on duplicate contacts. To fix this issue, review the CSV file and ensure that each contact has a unique identifier or property for the specified location. Remove any duplicate contacts or update the unique identifier to ensure uniqueness.
Custom field not supported
An error indicating that a custom field is not supported means that the specified custom field in the CSV file is not recognized or accepted by the HighLevel Support Portal. Custom fields must be configured and supported in the system for the import to be successful. To troubleshoot this issue, verify the custom field settings in the HighLevel Support Portal and ensure that the field name and format in the CSV file match the configured custom field.
Invalid custom field value
If you encounter an error regarding an invalid custom field value, it means that the value specified for a custom field in the CSV file is not accepted or does not meet the requirements set by the HighLevel Support Portal. To fix this issue, review the custom field values in the CSV file and ensure that they align with the accepted format and requirements. Correct any invalid values and try the import again.
Failed to create a contact
If you receive an error message stating that the import failed to create a contact, it means that the system encountered an issue while attempting to create a new contact from the CSV file. To troubleshoot this problem, review the CSV file and ensure that all required fields and properties are included and populated with the correct information. Check for any formatting mistakes or errors that may have caused the creation failure.
No email, phone, first name, and last name
An error indicating that there is no email, phone, first name, and last name in the CSV file means that these required contact details are missing or not provided for some contacts. To resolve this issue, review the CSV file and ensure that each contact has valid and populated email, phone, first name, and last name fields. Add or correct the missing information and try the import again.
Contact not found
If you receive an error stating that a contact was not found, it means that the specified contact ID or identifier in the CSV file does not match any existing contacts in the HighLevel Support Portal. To address this error, verify the contact ID or identifier and cross-reference it with the existing contacts. If the contact ID or identifier is incorrect, correct it in the CSV file and try the import again.
Failed to update a contact
If you encounter an error message indicating that the import failed to update a contact, it means that the system encountered an issue while attempting to update an existing contact from the CSV file. To troubleshoot this issue, review the CSV file and ensure that all required fields and properties for updating are included and populated with the correct information. Check for any formatting mistakes or errors that may have caused the update failure.
Failed to add campaign/workflow
An error stating that the import failed to add a campaign or workflow means that there was an issue adding the specified campaign or workflow to a contact during the import process. To troubleshoot this issue, review the CSV file and ensure that the campaign or workflow information is correct and matches the available options in the HighLevel Support Portal. Check for any incorrect names or discrepancies that may have caused the failure.
Supported timezones for importing
When importing contacts, it is important to specify the correct timezone for accurate scheduling and communication. The HighLevel Support Portal supports a wide range of timezones, ensuring that you can import contacts from various regions without any issues. Here is a list of supported timezones for importing:
- Pacific Standard Time (PST)
- Mountain Standard Time (MST)
- Central Standard Time (CST)
- Eastern Standard Time (EST)
- Alaska Standard Time (AKST)
- Hawaii Standard Time (HST)
- Atlantic Standard Time (AST)
- Greenwich Mean Time (GMT)
- Coordinated Universal Time (UTC)
- And many more…
Make sure to select the appropriate timezone when importing your contacts to ensure that all time-related actions and communications are accurate and aligned with the respective regions.
This image is property of images.pexels.com.
Accepted custom field format requirements
Custom fields can be a powerful way to organize and categorize your contacts based on unique attributes or characteristics. However, it is essential to ensure that the custom field format in the import file meets the requirements set by the HighLevel Support Portal. Here are the accepted custom field format requirements for the import file:
- Custom field names should not contain any special characters or spaces. Use alphanumeric characters and underscores (_) instead.
- The custom field values should be in the correct format and follow any specified rules or guidelines. For example, if the custom field is for a phone number, ensure that the values are in a valid phone number format.
- If the custom field is optional and can be left empty, the import file should indicate this by leaving the respective column or field blank for those contacts.
- Ensure that the custom field values match the specified data type for each field. For example, if the custom field is for a date, ensure that the values are formatted as dates.
By adhering to these custom field format requirements, you can ensure smooth and error-free imports of contacts with custom fields in the HighLevel Support Portal.
In conclusion, troubleshooting bulk imports via CSV in the HighLevel Support Portal can sometimes be a complex task. However, by following the steps outlined in this article and carefully reviewing the error logs, you can resolve any issues that may arise during the import process. Remember to double-check the formatting, verify the data integrity, and ensure that all required fields and properties are provided. By doing so, you can successfully import multiple contacts and keep your contact database up-to-date and organized.
This image is property of images.pexels.com.
