Troubleshooting: Import errors
Error: Too many fields to import
If you encounter this error, it means you have exceeded the limit of 700 fields for import. While we cannot increase this limit, you can resolve the issue by setting fields to Do not import. Once the total number of imported fields is below 700, the import will run successfully.
To resolve this, adjust your import mapping by setting fields to Do not import.
Go to Setup > [select the relevant import] > Edit mapping.
In the Edit mapping screen, find the field that you do not want to import.
From the drop-down menu for the field, select Do not import.
Click Save & import at the bottom left of the page.
Selecting multiple fields at once
To save time, you can select multiple fields and set them all to Do not import at the same time.
Select fieldsIn the Edit mapping section, check the boxes next to the fields you want to exclude.Apply Do not import to selectedAt the bottom of the list, click Do not import selected fields.ConfirmationThis will apply the setting to all the selected fields at once.Save and run importClick Save & import at the bottom left of the page.
This feature simplifies adjusting your import settings by eliminating the need to configure each field manually, helping you stay within the 700-field limit.
Error: Quality errors
In the quality check any errors that the import contains are shown alongside the number of items for which the error occurs. In order to check out the errors, you have to select the field within your import you want to check. In your project, navigate to Setup > Setup import > Project settings. Here you can select a field for which you want to check if there are any errors by clicking on the dropdown menu under “Unique ID per item” and clicking the “Save” button. After saving, navigate to the Import quality tab to see if your imports contain any errors.
Types of errors
There are a number of different errors that the Quality check will show. You will mostly encounter the following error messages:
'id'/'description'/'brand' is empty
'id'/'gtin'/'ean' contains values that are not unique
There were missing values in import <name> at field <name>, default values were used
'id'/'description'/'brand' is empty
What does the error mean? If the error is shown it means that the field you linked in the "Import settings" is empty for a number of products. You can click on the error to see for which items the field is empty.
How do I solve this error? How to solve this error depends on the missing information and if the information is available in another field of your items. For example, if the size is missing for some products but you have always included the size in your titles, you can use a search for value rule in your export channels to fill in the missing sizes. However, if the information is not available in another you will have to add the information in your import file.
'id'/'gtin'/'ean' contains values that are not unique
What does the error mean? Identifiers such as id, gtin, and ean codes should be unique for every item, meaning that there should not be multiple items that have the same identifier. If it does happen that one of these identifiers is shared between items you will see this error.
How do I solve this error? There are two ways to solve the error. If the items that share the identifier are the same item, you can use a deduplicate items rule in every export channel. Consider using our master rule groups feature to save time. However, if you want to keep both items because they are two different variants of the same product you need to change the identifiers in your import file.
There were missing values in import <name> at field <name>, default values were used
What does the error mean? When this error shows up, it means there is information missing in the named field, which is imported in the named import. The default value most likely ends up being empty, which causes this error to show up.
How do I solve this error? Check the import and the field that is mentioned. Make sure the relevant product data is added to this field.
Error: Missing field "field_name"
What does this error mean?
This error occurs when you're using a project field that no longer exists. The field is still used in the Categories, Rules, Mapping or Build steps but Channable can no longer find it in your import.
How can I solve this error?
Option 1: Add the project field again
You can add the field in Setup > Project fields or you can add it in the Rules step.
Option 2: Change the field with the error to a different field in the Rules, Mapping or Build steps
Map/select a different project field to use instead of the field that's missing. You can also select a different field to use in the Rules step.
Option 3: Pause or delete the rule
If you aren't using the rule with the missing field, you can pause or delete the rule if you're sure you don't need it in your setup.
Error: Circular dependency fields "field a" -> "field b"
What does it mean?
The circular dependency error tells you that you are creating a circular dependency by using the same field names for two different fields in the import mapping of your project. The image below shows an example of this.
How can I fix it?
In this case you should rename one of your fields in your import mapping. Following the example above, it would make sense to rename the "content" to "content" and the "description" to "description". However, you can type in any field name that does not exist yet.
You can edit the import mapping via "Setup" in the left menu, and then clicking "Setup project fields" and clicking on the name of the field:
After changing the field name, do not forget to click "Save & import" at the bottom of the page.
Error: We could not download (a part of) your Magento products
Step 1 - Check the preview of the Channable feed plugin
Log in to your Magento, go to "System > Configuration" and scroll down until you see the "Channable feed" plugin.
Once you click the "Channable feed" plugin, you should see a screen that's comparable to the following screen. Make sure the "Enabled Feed" option says "Yes".
Next, scroll all the way to the bottom of the Channable Feed plugin. You should see a list of your Magento Store views, with a "Preview" link next to it. Find the store view that you want to import into Channable and click the "Preview" link next to it.
If clicking this link opens a new page that contains information that looks similar to the following screenshot, it means your plugin is working correctly. If so, continue to step 2. If it doesn't open a page like the page below, first update the plugin to the newest version. If that does not solve the issue please contact Magmodules and ask them to check your plugin.
Step 2 - Auto connect with Channable
If the preview link above works, Channable should be able to import your products. When there is no import, most of the time this means that the connection with Channable wasn't created correctly. Make sure you use the "Click to auto connect with Channable" url of the image below to connect with Channable. You will be redirected to Channable and will be shown a pop-up in which you have to click "Add connection".
Step 3 - Try the new connection
Now that you've created a new connection using the official auto connection option, let's try and see if the new connection works. Go to Setup and click Setup import. In the next screen choose the newly created Magento connection.
If the import still fails after this point while the preview link in step 1 did work, contact support to investigate a bit further on how to get your import working.
How can I whitelist Channable's IP addresses?
If your import link added successfully yet fails to function, ensure you can access the link in your browser. If it displays correctly but fails in our tool, a firewall or server setting might be blocking access. To resolve, whitelist our office IP addresses. Send an email to [email protected] containing the following:
Subject: Whitelisting Channable office IP's
To be mentioned: Company ID and all concerned projects and imports
We will provide you with a list of our IPs that need to be whitelisted. Please let us know when you successfully whitelisted our IP addresses, so we can make sure the settings are correct on our side and the import works.
Last updated
Was this helpful?