Including quotes in a string from input file

[jenettd]

Hi,

I have data that is extracted from a database and save as a .yxdb file. The alteryx database file is used as an input file in my workflow. Some fields have strings that contain quotes, but instead of pulling the quotes in the input file tool, it's pulling in boxes where the quotes should be. Please see attached. The data type for the field is V_WString. I'm doing a comparison from this field to another field from a different input, an excel file, but the same data and it's erroring because the quotes are not included from the .yxdb input file. The data set in the input tool for the excel file is V_WString as well. What can I do to get the quotes included from the .yxdb file?

Thanks!

[abacon]

@jenettd If you open the YXDB file, do they appear as quotes or the boxes? Not when you run it but if you just open it from file explorer

[jenettd]

I'm not sure. The yxdb file has 175k rows and I can't filter or sort it.

[abacon]

I am trying to recreate the issue but my quotes are passing through fine. I am wondering if there is a problem in how it's writing to the YXDB file. If you right click the YXDB file, open with a text editor, and search for the value that is supposed to have quotes, what appears?

[jenettd]

I think my org must have open with other apps turned off because it wouldn't let me open in anything but Designer, but I was able to find the rows. In the .yxdb file it shows the blocks, but when I export the file to a .csv file it has the quotes. Is there a way to convert to .csv in the Input tool? Or would it be best to see if the code used to export the yxdb file can be modified to show quotes instead of blocks?

[abacon]

Try the solution in this thread, it has something to do with the encoding of the output data to the yxdb.

https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Discussions/File-path-saved-as-csv-but-out...

[jenettd]

From what I read in the referenced post, it seems like my only solution is to build another workflow to change the yxdb file to a .csv file and incorporate into the workflow. Would building a macro help with this? 

[abacon]

@jenettd That is what I would do. I would either try to fix the workflow that is creating the yxdb in the first place to ensure the correct encoding or I would use a macro to run this section within my workflow. It would be easier to fix the workflow that creates the yxdb in the long run but I don't know how possible that is for you.

[abacon]

@jenettd If this thread resolved your issue, please mark it as the solution so others may find it easier.