Forum Discussion
Not all rows imported by Power Query from a fixed-width text file
Anonymous looks like positions in fixed-width text. But this parameter should be
delimitercan be a single character, a list of characters, or the value"", which indicates rows should be split by consecutive whitespace characters. Default:",".
LucAppelmans i would try to use Lines.FromBinary instead of Csv.Document and then split text by positions. Just my 2 cents.
What's that list of numbers after the columns parameter (77)? Is that a list of column names, or delimiters or something? Seems wrong.
--Nate
Anonymous looks like positions in fixed-width text. But this parameter should be
delimitercan be a single character, a list of characters, or the value"", which indicates rows should be split by consecutive whitespace characters. Default:",".
LucAppelmans i would try to use Lines.FromBinary instead of Csv.Document and then split text by positions. Just my 2 cents.
Hi AlienSx,
I tried your suggestion to use Lines.FromBinary, and later split the column.
I got all my rows. Great thanks.
Do you have any explanation why this did work?
Anyway Great ThanksHello, LucAppelmans to be honest I don't know why Csv.Document failed in your case. I can't find split by positions option here however PQ interface does allow to enter positions (smth new to me). Anyway I am glad Lines.FromBinary solved your problem. It worked because it is desined to "convert a binary value to a list of text values split at lines breaks". At least you get all your lines. 🥂
