using Azure Data Lake File Output v2.5.0 on Alteryx Designer 2023.1 I'm trying to write a csv file without quote characters and comma as delimiter, reading from an Excel file; for the delimiter I get the comma as I want, but I'm not able to generate the csv without quote characters because I always get the csv with double quotes. Here are the options setting in the Azure Data Lake Output node
Below what I get
and here what I would like to get
Using Azure Data Lake File Output v2.5.0 on Alteryx Designer 2022.1 I get the csv without quote characters as I want.
Any hint? Thank you in advance.
Hi @EDPReda,
Could you not get the data in the structure you are looking for before writing it out? Then unticking write headers in the Azure Data Lake output tool? I've attached an example.
Kind regards,
Jonathan
it worked on 22.1 but doesn't work on 23.1? and you can confirm it's the same system and quotes are set up the same in any driver? And there are no quotes in your datastream which would mandate quotes? (ie quote mode never and underlyng data with quotes can be a problem) Can you confirm the behavior is the same on create new table vs overwrite?
this sounds like a bug. talk to your rep.
Hi Jonathan,
thank you for the hint but with your solution I have got double quotes at the beginning and end of each row and no headers
Unfortunately I need the result without any double quotes and with headers, like this
Hi,
I confirm "yes" to all your questions.
I've already opened an incident for this bug, but it seems the fix highlighted below works only for the Alteryx version before the 2023 (excluded 2023)
I will recontact the Alteryx Support.
Thank you very much for your help,
Irene
@Ir3n3_-_M4n - my advice would be to downgrade to the working version... If a version is working - I stick with it as along as I can.
Hi,
I agree with you but the reason why we were trying to work with the latest version of Alteryx is that with the version 2020.2 and the ones before we were not able to use a ODBC connection for Synapse Azure DB (with the possibility to use also an alias for the connection) and we were forced to use a OleDb one (with no alias connection).
I have just tried and with the 2022.3 we are able to use an ODBC connection for Synapse Azure DB, so with the 2022.3 we obtained the correct csv output on the Azure Data Lake and the ODBC connection to Synapse.
Thank you,
Irene
O.k. - you should mark a message as a solution if you can. There's a wide universe between 2020.X and 2023.X. I stick with 2021.4 or 2022.1 personally - although I'm warming up to 2022.3.