Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Problem : Input tool has limited varieties of code pages.

JunePark
8 - Asteroid

Hi,

 

I'm trying to input data via a specific code which reads in my language properly.

But it seems that the input tool provides only a specific variety of code pages.

JunePark_0-1587527049054.png

 

The code converting related functions provide much more various codes, but why does the input tool provide only the listed above?? (code list : https://help.alteryx.com/current/CodePages.htm)

 

Is there a way to input data via codes not listed in the capture above?

Inputting all data in wrong code(which I "have to" choose from the list above), and converting all the data via a formula tool is very time consuming and ineffective.

 

 

 

3 REPLIES 3
NeoInfiniTech
8 - Asteroid

It seems to be possible using the Interface tools (such as Text box, drop down etc.) to specify a code page present in https://help.alteryx.com/current/CodePages.htm and not in Alteryx Designer. I have tested reading from and writing to a code page not normally listed by Designer and it was a success, though it would be very nice if all the encoding options were listed in Designer. With analytic apps, you would need to run the workflow from app interface to successfully read all the characters properly with specified code page. Attached is an example workflow I built with dropdown encoding list, it only includes standard code pages. You can modify it to add the desired code page.

JunePark
8 - Asteroid

Thank you, it worked perfectly.

Guess I'll have to build a simple macro or so.

There are some difficulties using minor languages, hope Alteryx keeps on updating.

NeoInfiniTech
8 - Asteroid

The workflow attached also contains (probably) all encoding options supported by Alteryx Designer, sorted both by system and by language. It can be used to input/output files with code pages that are not listed as an option in the Input/Output tools.

 

The ideal solution to this in my opinion would be if an optionally extended encoding list was provided in the Designer.

Labels