none
CSV files and schema.ini RRS feed

Answers

  • That is correct: it does not, and we currently have no plans to add this functionality. If at some point Power Query is able to use arbitrary ODBC or OLEDB drivers -- and this is not a commitment to shipping that feature :) -- then you'd be able to use an external driver that does understand schema.ini.

    It would be good, however, to understand the cases where you think this would be useful.

    Thursday, February 6, 2014 2:33 PM
  • Correct. We either detect the delimiters automatically and return a multi-column table or return a single-column table if we couldn't detect it. At which point, the user can leverage Split Columns and any other Editor operation.

    Thanks,
    M.

    Friday, February 7, 2014 8:34 PM

All replies

  • That is correct: it does not, and we currently have no plans to add this functionality. If at some point Power Query is able to use arbitrary ODBC or OLEDB drivers -- and this is not a commitment to shipping that feature :) -- then you'd be able to use an external driver that does understand schema.ini.

    It would be good, however, to understand the cases where you think this would be useful.

    Thursday, February 6, 2014 2:33 PM
  • Thanks for the information Curt. I don't have a specific use case for this, I was just testing to see whether it worked.

    As far as I can see in the January release Power Query always applies its own smarts to understand the format of a csv file. Is this correct? I don't seem to be able to specify the delimiter etc manually any more. I don't mind this happening, and it seems to do a great job with the few files I've tested it with.

    Chris



    Check out my MS BI blog I also do SSAS, PowerPivot, MDX and DAX consultancy and run public SQL Server and BI training courses in the UK

    Thursday, February 6, 2014 2:46 PM
  • Yes, we've improved the detection being done by the UI so that it should be quite good at detecting at least the commonly-used delimiters. The underlying Csv.Document function still takes an explicit delimiter argument, and the inference is all happening in the front-end and not the library.

    Thursday, February 6, 2014 2:56 PM
  • Great, thanks. So to be clear - there are no circumstances where the user will be asked to supply details like the delimiter during the initial import? I understand that these things can be altered inside the Query Editor later on.

    Chris

     

    Check out my MS BI blog I also do SSAS, PowerPivot, MDX and DAX consultancy and run public SQL Server and BI training courses in the UK

    Thursday, February 6, 2014 3:05 PM
  • Correct. We either detect the delimiters automatically and return a multi-column table or return a single-column table if we couldn't detect it. At which point, the user can leverage Split Columns and any other Editor operation.

    Thanks,
    M.

    Friday, February 7, 2014 8:34 PM