Resolved The filename ProductsAPI-13-06-2021.xls is not recognised as an OLE file

Hello,

There seems to be something wrong with the file. When I check the filetype I see this:

ProductsAPI-13-06-2021.xls: HTML document, Unicode text, UTF-8 text, with very long lines (3261), with CRLF, LF line terminators

Saving the file agian as XLS and checking the filetype again I see this:

ProductsAPI-13-06-2021-OO.xls: Composite Document File V2 Document, Little Endian, Os: Windows, Version 1.0, Code page: -535, Revision Number: 0

So I tried to import the file as HTML but that doesn´t work either. The only thing that works is to resave the file in Excel. I wonder if there is something specific about this one file which causes the Excel reader we use to not recognize it.

Do you get a different file every day? If so, can you post a newer file for me to check how it looks like?

the file is generated auto when you hit this link
http://www.dioptra.gr/Tools/Export/BooksXLS.php
i save the file me too and i import it correctly, the point is to auto the proccess

Hello,

I have requested the assistance of the people who build the XLS parser to see if they have any idea. I had another idea and that is to read your file as a normal XML file but that does not work because the Greek data is not enclosed in CDATA tags.

We have to wait and see if this type of file is supported. It says XLS but in reality it is just an XML file. I will let you know when I have an answer.

ok thanks
let me know

Hello,

I have an answer and the most important part of it is this:

The Xml Reader will not load it however, because it isn't valid Xml. Entities like ι as HTML Entities, but aren't Xml Entities. It would only be valid if those entities were actually defined in the file itself, or were used within CDATA blocks. And the file itself is UTF-8, so there is no need to use HTML Entities in the file at all. In practise, we disallow the definition of entities within the Xml that we load, because allowing Entity definition also allows XXE/XEE attacks.

As I figured as well, this is not a valid file just that Excel is more forgiving in reading the file. They are going to check if something can be done to fix the file while reading but no promises there.

They may supply this file to 200 other eshops, doesn't make it a valid file I am afraid

ok i will wait for the last response and i will the vendor now about this

Hello,

Just wanted to post an update that there has been no response received anymore. I doubt there is going to be any response any time soon as it is a faulty XML, as such not a high priority.

Did you get any response?