Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip some (number) columns #17

Open
demoj1 opened this issue Aug 16, 2019 · 6 comments
Open

Skip some (number) columns #17

demoj1 opened this issue Aug 16, 2019 · 6 comments

Comments

@demoj1
Copy link

demoj1 commented Aug 16, 2019

Parser skips some columns in the file. Presumably these are columns with only numbers.
Example content file:

Компания ID ФИО Е-мейл ИНН Телефон
Наименование компании 1 123 Отдел продаж *@mail.ru 123456789 123456789
Наименование компании 2   Отдел продаж *@mail.ru    
Наименование компании 3   Отдел продаж *@mail.ru    
Наименование компании 4   Отдел продаж [email protected]    

Output after parsing:

iex(4)> {:ok, pid, parser} = Exoffice.parse("./test/test_data/template.xls", 0)
{:ok, #Reference<0.1040318736.556138510.157986>, Exoffice.Parser.Excel2003}
iex(5)> Exoffice.get_rows(pid, parser) |> Enum.to_list()                       
[
  ["Компания", "ID", "ФИО", "Е-мейл", "ИНН",
   "Телефон"],
  ["Наименование компании 1", nil,
   "Отдел продаж", "*@mail.ru"],
  ["Наименование компании 2", nil,
   "Отдел продаж", "*@mail.ru"],
  ["Наименование компании 3", nil,
   "Отдел продаж", "*@mail.ru"]
]

Columns ID, ИНН, Телефон skipped

File for reproduce it: https://yadi.sk/i/ZHR9wKq7AW5Aig

@AlexKovalevych
Copy link
Owner

@dmitrydprog thank you for your ticket, unfortunately i can't download the example file since that domain is not available from my country, please upload it to different storage (e.g. dropbox)

@rockneurotiko
Copy link
Contributor

@AlexKovalevych there you go https://www.dropbox.com/s/xwdfh97uwe6w4yj/template.xls?dl=0

@babrovka
Copy link

Facing the same issue
@AlexKovalevych do you have any updates on this matter?

@AlexKovalevych
Copy link
Owner

Well, i could reproduce it recently, but it doesn't look like a quick fix (unless you're very familiar with parsing algorithm). So i need to check the whole parsing process to understand the problem here, can't promise it will be resolved soon, but i'll try to figure it out.

@babrovka
Copy link

thanks for prompt reply! Is there any workarounds?

@alex-strizhakov
Copy link

Hey!
Are there any updates on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants