For details about each issue, see below.
Error in uploaded data
The error message "Error in uploaded data" almost always means that there is at least one record in the CSV file that has too many or too few fields compared to the fieldname record at the top of the CSV file.
The most common cause of this problem (wrong number of fields in a given record) is that you have forgotten commas at the end of lines where the last field is blank. The next most common cause of this problem is improper use (or non-use) of quotation marks.
Fields that contain commas, embedded linefeed or carriage return characters, or quotation marks must be surrounded entirely by a set of quotation marks.
Quotation marks embedded within a field must be doubled up.
Every record in the CSV file must have exactly the same number of fields as the first record where the fieldnames are defined. Empty fields still require commas -- it's the commas that occur outside of quotation marks before the first carriage return/linefeed outside of quotation marks that determines how many fields are present in any given record.
Browser times out during upload
If the browser times out during the upload of the CSV, then the CSV is too big. You need to break it up into multiple CSV files as best you can and try to upload smaller chunks.
Browser times out during Add/Rebuild
If the browser times out during the Add or Rebuild phase, it means the browser timed out, but the process is still running on the server side.
You should leave the editor for a while and log in again later.
How long you will need to wait to log in again depends on the time of day and how many items you had on deck in the editor to add or rebuild into the store.
For example, 14,000 items at 3:30 pm Pacific time could take a few hours to finish adding or rebuilding into the store.
On the other hand, 1,000 items at 1:00 am Pacific time shouldn't take more than 5-10 minutes at most.
Do not kill the editor in this case unless you explain to the merchant what's going on, and that you don't know how long it will take to complete, and that if you do kill the editor for them, they'll have to do it all over again, and there's no guarantee their browser won't time out again.
Unexpected results based on the PATH used for items
Problems with determining the proper PATH to use to get items exactly where you want them are editor-related, and we can't change the way the software works at this point in time. All we can do is tell you how it currently works, and treat any pushback as feature requests.
Here's some useful info about how the PATH field is used:
The software will traverse the PATH you provide, creating sections and subsections if they don't exist. This traversal always results in the ID of each section being the entire path to that particular point, with all special characters, spaces, and colons converted to hyphens. The colons are used to determine each section/subsection level.
For example, a PATH of books:cooking:italian will result in:
This behavior cannot be avoided. If you are having problems because of this behavior, you should submit the problems as feature requests. You will need to change your data file or manually perform edits until things come out the way you want them to. You might also want to use the information below as a work-around.
PATH is always treated as the whole pageID of the section that contains the item being created by that record. You can set PATH to be the ID of an existing section (without the additional colons and other parent-path info), and the item will be created within that section. However, that section will also have its ID automatically placed into the Contents of the home page. It will still exist in its original location, though, so all that's necessary is to manually edit the Contents property of the home page to remove that ID, if you don't want that section in the Contents of the home page.
For example, a PATH of cooking for an item would:
Troubleshooting CSV problems:
Please note that we can really only help you by looking at your file when you're experiencing the "Error in uploaded data" error message. The other problems described above aren't anything we can troubleshoot. We can only make the suggestions listed in the information above.
To troubleshoot a CSV file, you first need to make sure that your CSV file meets the requirements regarding number of fields, quotation marks, commas, and line breaks.
If you feel that it does and you still get the "Error in uploaded Data" error when you upload that file, upload the exact CSV file you're having problems with to your Files area. You need to upload/add the file to your site in the same way your have been trying that results in the error. You then need to check the file yourself in both Excel and Notepad.
Netscape sometimes adds an extra carriage-return/linefeed to each line when you view a CSV file in Netscape.
If you're downloading someone else's CSV from their files area, do so by right-clicking on the link and saving the file to your computer that way.
Be sure to save it as a CSV file and open it directly with Excel. This will allow you to see at-a-glance if there are any broken fields (Caption is usually the culprit here) or if they've left the last field blank for any of their records.
You should also open the file in Notepad when checking individual records to see if the proper number of commas are used or to see if quotation marks are used properly.
Notepad will let you see the individual record in question the exact way the Yahoo! Store software sees it. This is especially helpful when you're looking to see if there is the correct number of commas in any given record where the last field(s) is blank or if the quotation marks are used correctly for fields that require quotation marks.
If your check reveals that the file appears to be correct, try uploading it to your store.
If it still doesn't work, and you're certain that the file is correctly formatted according to the CSV format requirements, escalate through the yrt-store-init queue using the guidelines for escalations. In addition to the basic required information, also include where the exact CSV file can be found, as well as whether we have permission to upload the file to the store in question.
Other notes about CSV files:
Please also note that a single upload cannot include items and accessories. Accessories are items without pages of their own. You can't upload a single CSV that creates pages for some objects and not for other objects in that file.