by RetailEdge Moderator » Sat Dec 31, 2011 4:25 pm
Most likely you are running into an issue caused by saving the REDI file as a CSV file from Excel. The structure of the REDI file looks something like what you see below.
<REDI_Invent>
Inv_Sku,Inv_Desc,Inv_ItemID,Loc_Settings_LocID,Inv_Quan,Inv_DepartID,Inv_VendorID,etc .........
000045,"OIL SOAP",103482,Main,0,"SOAP WORKS",.......
</REDI_Invent>
<REDI_Depart>
Dept_DepartID,Dept_Desc,Dept_Margin
"SOAP WORKS","SOAP WORKS",50
</REDI_Depart>
<REDI_Vendor>
Vend_VendorID,Vend_Desc,Vend_Contact,Vend_AccountNum,Vend_Street1,Vend_Street2,etc ..........
MISC,MISC,,,,,,,,,,,
</REDI_Vendor>
The REDI (RetailEdge Deta Interchange) file format was created to allow RetailEdge Users to take a laptop on the road and create new data in the laptop and then import this data back at the store. There are different sections of the file broken up by other starting and ending tags (e.g, Starting Tag:<REDI_Invent>, Ending Tag:</REDI_Invent>). These different sections are setup so that if on the laptop a new inventory item is created that has a new vendor, class, or department, that the information about this department can also be brought over.
This format although it is meant to import/export data between copies of RetailEdge has been used for importing data for new users who have already created data in another program. The problem is that most people create this data in Excel or another spreadsheet program and then export it as a CSV file. A spreadsheet will not know anything about the REDI file format and so will do something like the following:
<REDI_Invent>,,,,,,,,,,
Inv_Sku,Inv_Desc,Inv_ItemID,Loc_Settings_LocID,Inv_Quan,Inv_DepartID,Inv_VendorID,etc .........
000045,"OIL SOAP",103482,Main,0,"SOAP WORKS",.......
</REDI_Invent>,,,,,,,,,
<REDI_Depart>,,,,,,,,,
Dept_DepartID,Dept_Desc,Dept_Margin,,,,,,,
"SOAP WORKS","SOAP WORKS",50,,,,,,,,
</REDI_Depart>
<REDI_Vendor>,,,,,,,
Vend_VendorID,Vend_Desc,Vend_Contact,Vend_AccountNum,Vend_Street1,Vend_Street2,etc ..........
MISC,MISC,,,,,,,,,,,
</REDI_Vendor>,,,,,,,
This is because the Excel export will take the longest number of fields (Usually the second row in the REDI file with the column names) and then place commas where it thinks there should be data on the other lines. CSV just stands for Comma Separated Values and so if Excel thinks there should be 14 columns and only finds one filled out (like with the start tags <Redi_Invent>), then it will put 12 commas after the start tag.
RetailEdge is only expecting the start tag and not the commas. So these commas must be stripped off manually. You can do this in a couple of ways. Either open the file in a text editor like Notepad and delete the commas. Or RetailEdge has a text editor built into the import function and so when you get the error you can view the file as text and then edit it there.
One other quirk in some versions of Excel is that after about the 14th row of the file if Excel does not find data in all the columns (say only the first 10 of 20) then Excel will not add the proper amount of commas and actually strip the commas. RetailEdge will not allow this in the import file. So the best thing to do is in your Excel spreadsheet put a value like a dash (-) in the last column (in the redi invent file Inv_Loc_BinShelf). This will make sure that the commas continue to be filled in properly.
Hope this helps.