CSV problems - missing short descriptions, headers too big

[alwayspaws]

You know all the good modules! You don't use it any more for TB? If you do, please tell me the name. Thank you!

[Havouza]

I think you have it

[Havouza]

I use xml now for the dropship

[alwayspaws]

The little module that says something about "bo" in the filename? I'm not on my desktop. I'm on the laptop now.

[Havouza]

ba

[jnsgioia]

@alwayspaws I use libreoffice and save as csv. I use | for delimiter and ~ for multiple separator for categories, products and combinations and it works.

[alwayspaws]

@Havouza that must be it! tnx! :)

[alwayspaws]

@jnsgioia said in CSV problems - missing short descriptions, headers too big:

Hi! I remember that discussion about using the pipe as a separator but I don't want to do all my spreadsheets over and over again.

I'm waiting for @Traumflug updates! :)

[alwayspaws]

I clicked to quote you and don't see your message, @jnsgioia

[jnsgioia]

@alwayspaws said in CSV problems - missing short descriptions, headers too big:

I clicked to quote you and don't see your message, @jnsgioia

I don't know, it is there...

[alwayspaws]

@mdekker said in CSV problems - missing short descriptions, headers too big:

Ohh it it supposed to support .ods (Open Office) files as well. I have never tested that.

It's what I use but then I convert to csv because the csv importer refuses to accept .ods files

[alwayspaws]

Yes, I can, when I get back to desktop or just take the above csv and convert to ods. Good?

[alwayspaws]

BTW, the missing short descriptions are only in the BO, not the FO, when I upload a spreadsheet.

[alwayspaws]

please bc i dont have that s/w on this laptop. tnx!

[alwayspaws]

So shorten it! :) U can wait for me to go on the desktop in a few hours.

[alwayspaws]

I just tried to import after renaming it. Will continue when back on desktop.

[alwayspaws]

@mdekker I don't have any suppliers listed.

[alwayspaws]

Phew!

[alwayspaws]

@mdekker Where or how do we get @Traumflug 's standardization?

[Havouza]

Does that mean that commas in description fields must be inside quotes also?

[Havouza]

good solution then

[alwayspaws]

So my combination values of size and color get separated by a comma and that's all. Is that correct?

example: size,color

What are the separators supposed to be on the import page when we upload the file?

Is the update @Traumflug created available now? Or when the ticket gets closed?

[alwayspaws]

Wonderful! Thanks!

[Traumflug]

Hmmz, xlsx, ods, odt, xls, you name it

That's the problem, there are so many different formats.

If you want a comma in the value itself, make sure you enclose it in quotes.

I fear it's difficult to change how a given spreadsheet exports CSV. There is no clear standardization: https://en.wikipedia.org/wiki/Comma-separated_values#Standardization

Quote:

Reliance on the standard documented by RFC 4180 can simplify CSV exchange. However, this standard only specifies handling of text-based fields. Interpretation of the text of each field is still application-specific.

Personally I tend to put emphasis on one format, only, and support that in all observed flavors. A .xls written by Excel, then converted by PHPExcel might give different results than a .xls written by OpenOffice or GNUmeric, then interpreted by PHPexcel. All of these desktop applications support exporting to CSV, so it's (almost) no extra work for merchants to do this export.

[alwayspaws]

What would be viewed as the "standard" spreadsheet format that will work with thirtybees imports?

The way I do it is I create a spreadsheet with OpenOffice calc and use the ".ods" file extension so that I can copy and paste and manipulate the data any way I want. Then I convert it to ".csv" but it looks like I won't have to do that any more! Yay! (I hope!)