Common problems with imports and how to solve them
Thousands of different files and pieces of data are uploaded to Plytix all the time. We've seen a lot of spreadsheets come through, so we've also noticed that there are common problems and errors when it comes to importing these into our system.
Corrupted File or Funky Characters
This means that something is off within the spreadsheet, and it may not be visually apparent to you (sometimes they are literally invisible). This usually happens with text fields.
If this happens it is likely that you will import your CSV and see this screen:
This means our importer tried to read it and failed. Sometimes this can be fixed by changing the Charset and the other file settings, but sometimes not. If your case is the latter try to do this:
Solution 1: Re-Export
- Import your spreadsheet into another system like Google Sheets*
- Download your CSV in CSV format
- Try to upload again to our system
*Don't use Excel for this. It is notorious for corrupting files with formulas and formatting styles
Usually this works because these systems are simply better at reading and cleaning up all kinds of corrupted files. We just haven't been around as long.
Also, this will tell you if your CSV is corrupted beyond repair. If those systems can't read it, then it is likely something else is going on.
Solution 2: Remove Rich Text or long text fields
This is mostly just to test and identify which columns are the ones messing up your import.
- Remove long text fields
- Try to import again
- If successful, review the text fields you removed for any characters or formatting issues that may have thrown things off
Solution 3: Re-Export in UTF-8
The most common and standard Charset is UTF-8.
For this reason it is probably the safest bet in terms of reading/parsing the majority of characters. Try to re-export your CSV using UTF-8 and import again.
Wrong File Settings
If you see that screen above, and you believe your data is not corrupted, check the file settings.
Make sure your Charset has been properly matched. Our system tries to guess this the best it can, but there are times when it doesn't guess right. You can also check your delimiters and separators by checking the properties of your CSV file.
My SKU is matched but the button is disabled
The reason this happens is because we allow you as a user to create an attribute called "SKU", but we need you to match a column to the SYSTEM attribute SKU.
To do this check your SKU column and click the red X that appears when you hover next to the attribute name.
Then select MATCH EXISTING
Then search for SKU and choose the one in the System Attributes group
System Attributes are identifiable by the purple SYS that appears after you have selected it. The green ATT denotes a user-created attribute.
Once that is done, the IMPORT button should be re-enabled.
If your import was successful, but certain things didn't appear, check your Import Logs.
If you cannot figure it out, reach out. Make sure to send over the CSV you are struggling with and we will see what we can do.