Alteryx Designer Desktop Ideas

I really like that I can scroll -- using my mouse -- between the tool groups in Alteryx. Can this UX be added to scroll through my workflows? I usually have a bunch open, and this functionality would be awesome to have there, too! 🙂

PS: Yes, I know I can do Ctrl+Tab...but mouse scrolling is more efficient.

Currently I find myself always wanting to replace the DateTime field with a string or visa verse.

It would be nice to have a radio button to pick whether to append the parsed field to replace the current field with the parsed field.

I understand that all you need is a select tool after, this would be a nice QoL change especially where the field may be dynamically updated.

Can we set our own Comment tool default preferences? - For me I want to set the text alignment to be "Center" by default, currently it's always "TopCenter" when I open it.

Would like to direclty query Hyperion Cube / Essbase data source directly - please propose functionality in next release or add a user macro to the gallery.  Thanks -cb

Hi there,

Just got a new 4k UHD monitor, and found that Alteryx Designer doesn't scale well in default settings in Windows.    Fonts are blurry but icons are the right size.

If instead you change compatabilty mode to allow the application to force scaling, then the fonts and icons end up all different sizes.

Could you change the fonts and icons to scale gracefully in Windows 10 to full 4k UHD HDR - especially on the large size monitors (30 inch plus)?

Shot 1: default mode - blurry text - badly scaled by Windows 10.    It's not easy to see here because the image is small - but all the text is blurry like a badly blown up BMP file.

Shot 2: Override Windows 10 DPI scaling and set to "Application" mode

You can see in the picture below that text is now super-sharp but the the play button; save button are all tiny; the fonts are different sizes (look in the properties tab on the left) etc.

Sometimes I need to connect to the data in my Database after doing some filtering and modeling with CTEs. To ensure that the connection runs quicker than by using the regular input tool, I would like to use the in DB tool. But is doesn't working because the in DB input tool doesn't support CTEs. CTEs are helpful for everyday life and it would be terribly tedious to replicate all my SQL logic into Alteryx additionally to what I'm already doing inside the tool. 

I found a lot of people having the same issue, it would be great if we can have that feature added to the tool. 

I think it would be nice to be able to more easily reorder fields that you're joining by in the Join tool.

For example, I have already joined by CASS_Address and CASS_City. After I did this, I realized I wanted to go back and join on Name, too, and I want that to be first. How the tool is configured now, if I want Name to be first, I must redo all of the drop downs. I would like to be able to add Name to the next set of open drop downs then use some arrow buttons to be able to move them up in the order (similar to the Summarize tool).

When using the formula tool -- one of the nice features is that when you start typing in a function or variable -- the tool will show formulas/variables that begin with that letter and keep changing as you type in more letters. I believe this is called predictive typing.

However, this does not happen in tools like multi-row or multi-field where a user would have to search for functions and variables if they weren't sure what they are.

Can predictive typing be added to the multi-row and multi-field tools? If I want to take it further, any tool that allows a user to use the formula functionality should be able to see predictive typing. 

Thanks,

Seth Moskowitz

I understand the need for "exclusive rights" when using an input tool.  Unfortunately, due to the nature of some corporate data, getting write access to a file is not always possible.  I would like to have the ability to configure an input tool to open a file in "Read Only" mode while producing a warning message that the file was processed in that mode and may not contain the lastest version pf the data.  I envision this as a checkbox option in the tool configuration panel.

Hi there,

When creating a database connection - Alteryx's default behaviour is to create an ODBC DSN-linked connection.

However DSN-linked connections do not work on a large server env - because this would require administrators to create these DSNs on every worker node and on every disaster recovery node, and update them all every time a canvas changes.

they are also not fully safe becuase part of the configuration of your canvas is held in the DSN - and so you cannot just rely on the code that's under version control.

So:

Could we add a feature to Alteryx Designer that allows a user to expand a DSN into a fully-declared conneciton string?

In other words - if the connection string is listed as 

- odbc:DSN=DSNSnowFlakeTest;UID=Username;PWD=__EncPwd1__|||NEWTESTDB.PUBLIC.MYTESTTABLE

Then offer the user the ability to expand this out by interrogating the ODBC Connection manager to instead have the fully described connection string like this:
odbc:DRIVER={SnowflakeDSIIDriver};UID=Username;pwd=__EncPwd1__;authenticator=Snowflake;WAREHOUSE=compute_wh;SERVER=xnb27844.us-east-1.snowflakecomputing.com;SCHEMA=PUBLIC;DATABASE=NewTestDB;Staging=local;Method=user

NOTE: This is exactly what users need to do manually today anyway to get to a DSN-less conneciton string - they have to craete a file DSN to figure out all the attributes (by opening it up in Notepad) and then paste these into the connection string manually.

Thanks all 

Sean

With the growing demand for data privacy and security, synthetic data generation is becoming an increasingly popular technique for generating datasets that can be shared without compromising sensitive information especially in the healthcare industry.

While Alteryx provides a range of tools, I believe that a custom tool could help meet the specific needs of a lot of healthcare organizations and customers.

Some potential features of a custom synthetic data generation tool for Alteryx could include:

Integration with other Alteryx tools: The tool could be seamlessly integrated with other Alteryx tools to provide a comprehensive data preparation and analysis platform.

Customizable data generation: Users could set parameters and define rules for generating synthetic data that accurately represents the statistical properties of the original dataset.

Data visualization and exploration: The tool could include features for visualizing and exploring the generated data to help users understand and validate the results.

I believe that a custom synthetic data generation tool could help our organization and customers generate high-quality synthetic datasets for testing, model training, and other purposes.

Due to different file formats whether it is .xlsb or any other formats, sometimes it requires end user to install additional drivers/engine.

Some of these driver installations require installations of outdated software e.g. Microsoft Access 2013 (Microsoft Access Database Engine 2013), which poses unnecessary security risk.

Therefore we recommend that in the future version should take note and incorporate such drivers into the installation package so that there is no need to install them separately.

When we edit formula tool, only first expression is expanded. I prefer all expressions are expanded as a default. When I want to shrink them, I want to 'expand all' icon like attached snap shot. This icon is toggled same as each expression's expand icon('expand all' <-> 'shrink all')

Hello,

My issue is very easy to solve. I want to use the generic ODBC in memo for a specific base (monetdb here but it isn't important).

I try to ouput a flow in a MonetDB SQL database. As you can see, I only take very simple field types

However I get this error message :

Error: Output Data (3): Error creating table "exemplecomparetable.toto": [MonetDB][ODBC Driver 11.44.0][MONETDB_SAU]Type (datetime) unknown in: "create  table "exemplecomparetable"."toto" ("ID" int,"Libellé" char(50),"Date d"
syntax error in: ""Prix""
CREATE  TABLE "exemplecomparetable"."toto" ("ID" int,"Libellé" char(50),"Date de Maj" datetime,"Prix" float,"PMP" float)

Reminder : SQL is an ISO Norm. Default type should follow it, not the MS SQL configuration. Interoperability is key

Links to : for in-db
https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Generic-In-database-connection-please-stop-i...

Issues constated : MonetDB
https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Output-Data-date-is-now-datetime-makin...

Informix: https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Alteryx-date-data-type-error-trying-to...


Best regards,

Simon

I believe many have voiced out this as their pain point within the Community. Essentially, there is no straightforward method to import multiple Excel files which are password protected.

I understand that there is an R solution suggested by several users, however, that is not ideal as it can be difficult to obtain permission from internal Tech team to install the package on the users' computers. 

Re-saving them without password is not only a hassle, but also raises concerns for data protection and security.

This may have been raised before, but we would like to see the equivalent of PRICE and YIELD formulas from Excel in Alteryx's Formula tool. I believe many users in the finance industry are using formulas like these frequently and it would be helpful to be able to replicate the formula in Alteryx.

Manually building the formula is possible, however it is unnecessarily complicated especially if you are working on different calendar basis e.g. 30 /360 European.

Thank you!

Most databases treat null as "unknown" and as a result, null fails all comparisons in SQL.    For example, null does not match to null in a join, null will fail any > or < tests etc.    This is an ANSI and ISO standard behaviour.

Alteryx treats null differently - if you have 2 data sets going into a join, then a row with value null will match to a row with value null.

We've seen this creating confusion with our users who are becoming more fluent with SQL and who are using inDB tools - where the query layer treats null differently than the Alteryx layer.

Could we add a setting flag to Alteryx so that users can turn on ISO / ANSI standard processing of Null so that data works the same at all levels of the query stack?

Many thanks

Sean

In the community and in mixed teams - it's very common for people to be caught on the error that "This document was created in a more recent version".   Although there are several workarounds (e.g. this one from @WayneWooldridge  here https://community.alteryx.com/t5/Alteryx-Knowledge-Base/Adjusting-Alteryx-Files-for-Different-Versio...), this seems like it may be an easy problem to solve more permanently.

Could we add an option to Alteryx to save the file with the lowest compatible version number?

So - for example - if i'm only using components that shipped with version 10, then please mark the file as version 10.   If I've used a tool that shipped in 11.0.6 then that needs to be the version number.

This way - files will be back-compatible as far as is possible by default unless using newer components.

Many thanks

Sean