community
cancel
Showing results for 
Search instead for 
Did you mean: 

Alteryx Designer Ideas

Share your Designer product ideas - we're listening!
Upgrade Alteryx Designer in 10 Steps

Debating whether or not to upgrade to the latest version of Alteryx Designer?

LEARN MORE

1 Review

Our submission guidelines & status definitions before getting started

2 Search

The community for a solution or existing idea before posting

3 Vote

By clicking the star in the top left corner of an idea you support

4 Submit

A new idea to suggest a product enhancement or new feature


Suggest an idea

Microsoft Access 2000-2003 does not access big integer

 

Integer — For integers that range from -32,768 to +32,767. Storage requirement is two bytes.


You can find MS documentation here : https://support.office.com/en-us/article/set-the-field-size-ba65e5a7-2e6f-4737-8e72-36b93f966a33


So when you use Alteryx with big integer (e.g Int64 ), it won't work the way you expected and the field will be converted into Double.

So what I propose :

-a change in documentation about this behaviour
-a warning message on the output box when you use Access and you have Int64

-ability to select Access 2016 in order to use Long integer format

Best regards,

Simon

Problem:

When searching for Alteryx help on Google the search results rarely return the current version of the Help documentation from the Alteryx website. Instead, what often happens is that an old version of the Help documentation is returned.

 

For example, a search for 'Run Commend Tool Alteryx' returns links for the 2018.3 and 11.3 instances of the help page:

 

Screenshot 2019-05-15 at 16.30.00.png

 

These relate to prior versions of Alteryx and a better result would be to link to the /current/ version of the page (the URL for which never changes).

 

https://help.alteryx.com/current/RunCommand.htm

 

The problem above can be replicated for almost any tool or variant of search terms.

 

Since Google is such a crucial resource for troubleshooting, there is a risk that (a) users will inadvertently access out of date documentation and (b) users will be confused by the presence of multiple search results.

 

Solution:

By adding a 'robots.txt' file to web pages for prior versions of the tool these results can be suppressed from Google search results.

 

https://support.google.com/webmasters/answer/6062608?hl=en

 

This should result in the /current/ documentation pages rising in search results and being more prominent when users search for help on Alteryx using Google.

 

I spoke to an Alteryx Product Manager, Alex Polly and pitched an idea about having workflows bookmarked for weekly or monthly runs. 

 

I run weekly workflows together one after the one, from different folders and I have to open file location every single time. So here's a thought, how about if we can bookmark workflows as a set/folder itself and one click and all workflows open up. 

 

Chrome has this feature storing the links in a bookmark folder. 

 

Please find the link for your reference. 

 

https://lifehacker.com/save-sets-of-multiple-tabs-to-launch-later-in-the-bookm-1453967463

 

Thanks, 

Jai Katariya

 

 

Hello,

As I mentioned in this previous idea : https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Generic-In-database-connection-please-stop-i...

 

field mapping in generic in-db connection is based on Microsoft Sql Server. Given the specificity of MSQL Server field types, I would like to change that in order to at least be able to use another database. Without that, this feature has no sense at all.

Best regards,

Simon

When you drag a comment box into a workflow it should sit underneath all other data tools by default.

 

Currently, the order of tools is set by the order of placement (that is, tools placed in the workflow first are placed below subsequently placed tools).

 

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! Smiley Happy

 

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

 

idea.gif

The "Manage Data Connections" tool is fantastic to save credentials alongside the connection without having to worry when you save the workflow that you've embedded a password. 

 

Imagine if - there were a similar utility to handle credentials/environment variables. 

 

  • I could create an entry, give it a description, a username, and an encrypted password stored in my options, then refer to that for configurations/values throughout my workflows. 
    • Tableau credentials in the publish to tableau macro
    • Sharepoint Credentials in the sharepoint list connector
  • When my password changes I only have to change it in one place
  • If I handoff the workflow to another user I don't have to worry about scanning the xml to make sure I'm not passing them my password
  • When a user opens my workflow that doesn't have a corresponding entry in their credentials manager they would be prompted using my description to add it.
  • Entries could be exported and shared as well (with passwords scrubbed)

Example Entry Tableau:

AliasTableau Prod
DescriptionTableau Production Server
UserIDJPhillips
Password*********
+ 

Then when configuring a tool you could put in something like [Tableau Prod].[Password] and it would read in the value.

 

Or maybe for Sharepoint:

 

AliasTeamSP
DescriptionTeam sharepoint location
UserIDJPhillips
Password*********
URL http://sharepoint.com/myteam
+ 

 

Or perhaps for a team file location:

AliasTeamFiles
DescriptionRoot directory for team files
Path\\server.net\myteam\filesgohere
+ 

 

Any of these values could be referenced in tool configurations, formulas, macro inputs by specifying the Alias and field.

1-3-2019 12-43-52 PM.png

When we have too many steps in a workflow, it is mandatory to use container to represent better business flow. It can collapse many steps to represent one business flow.

But, when we open collapsed tool container, workflow canvas not resizing to give space for tool container, it overlap on existing tools.

 

It is better to resize workflow canvas when we collapse or resize tool containers. 

Hello,

As of today, the in db connexion window is divided into :
-write tab

-read tab

However, writing means two different thing : inserting and in-db writing. Alteryx has already 2 different tools (Data Stream In and Write Data).

Si what I propose is to divide the window into :
-read
-write
-insert

Best regards,

Simon

 

 

Other applications I work in reguarly utilize right-click menus.  Sometimes those menus seem annoying, but in working with Alteryx, I realize it’s actually quite smart because it eliminates unnecessary wrist movement.  In the screenshot below, I have highlighted a bunch of fields.  alteryx.pngThe boxes were previously unchecked and I wanted to check them to bring them into my workflow.  I highlight them, and if I were in a different application, I would just right click and get access to everything that is in the options menu, but in Alteryx, I have to actually move the mouse to the options menu.  This might seem super nitpicky, but as someone who is currently suffering from overuse injuries in my wrists and hands, I really appreciate minimal wrist movement.

I think I'm liking the new UI, but I think it's necessary to bring back save, undo and re-do buttons....

 

1. Frequent saving of workflows is crucial and not everyone uses keyboard shortcuts

2. The ability to undo (lots) of changes is a key part of iterating and rapidly building workflows in Alteryx and again not everyone uses keyboard shortcuts to do this.

 

Looks like there's potentially space to add this to the right of 'help' (I suspect this might be technically quiet difficult) or to the left of 'run', 'schedule' and 'active documents' as seen in the image below.

 

Out of interest, where has the 'documents' terminology come from?

 

2018-11-14 22_12_14-Alteryx Designer x64 - PureGym Log In.yxmd_.png

 

 

 

 

So it takes while to download data from in-db (say oracle table) and load it to another...

https://community.alteryx.com/t5/Alteryx-Knowledge-Base/How-To-Migrate-Entire-Databases-Using-Altery...

 

Why not build an additional in-db tool to migrate data without downloading to local...

Oracle has this capability and here is the Syntax;

 

COPY Command Syntax

 

COPY {FROM database | TO database | FROM database TO database} {APPEND|CREATE|INSERT|REPLACE} destination_table [(column, column, column, ...)]
USING query

 

where database has the following syntax:

username[/password]@connect_identifier

 

Copies data from a query to a table in a local or remote database. COPY supports the following datatypes:

CHAR DATE LONG NUMBER VARCHAR2

Example;

COPY FROM HR/your_password@BOSTONDB -
TO TODD/your_password@CHICAGODB -
CREATE NEWDEPT (DEPARTMENT_ID, DEPARTMENT_NAME, CITY) -
USING SELECT * FROM EMP_DETAILS_VIEW

Often as I am scraping web sites, some clever developer has put an invisible character (ASCII or Unicode) in the data which causes terrible trouble.

I've identified 89 instances of zero-width or non-zero-width glyphs that are not visible and/or Alteryx does not classify as whitespace. There are probably more, but Unicode is big y'all.

Unfortunately, the Trim() string function only removes 4 of these characters (Tab, Newline, Carriage Feed, and Space).
REGEX_REPLACE with the \s option (which is what the Cleanse macro uses) is a little better but still only removes 20. And it removes all instances, not just leading and trailing.

I've attached a workflow which proves this issue.


@APolly: this is what I mentioned at GKO.

And I did see this post (https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Elegantly-remove-all-ASCII-characters-...), but it's too brute force. Especially as Alteryx is localized and more users need those Unicode characters.

Screen Shots.JPG

I’m writing about a short-coming I see in the Publish to Tableau Server Tool v2.0 (PTTS).  I work in a development environment where we use different Tableau servers (i.e. development, test, production) to support product development.  One of the shortcomings of PTTS is that once the Tableau server information you are connecting to is entered, validated, and the tool is configured, you can no longer ‘see’ which Tableau server/site the tool is publishing to.  I think this piece of information is quite important.  I know I can always us the “Disconnect” button in the tool and re-enter the information so I know which server it is pointing to, but this defeats the purpose of entering that information in the tool in the first place.

 

Please consider an enhancement to the tool so we developers know at a glance where (server/site) the tool is publishing.  Project and Data source names are helpful, but in a development cycle, all Tableau servers may have the same Project and Data source names across all environments.

 

I've attached examples of the tool options when being defined and once the tool is configured – notice server URL and Site are aren’t displayed in the tool once it has been configured.

 

Please update the Publish to Tableau Server connector tool to support Tableau's Ask Data feature. The data source must be recognized as an extract on Tableau Server in order for the Ask Data feature to work. Currently, all data source published using version 2.0 of the connector tool are recognized as a live data source. The work around is cumbersome and requires multiple copies of data sources to be created and managed.

At our Customer we are using SAP HANA as our main database. in the moment we can only use the ODBC Client to connect against SAP HANA. In this scenario it is only possible to establish a connection with Username and Password. It would be very good if every Alteryx Designer user can connect via SSO to the HANA Database. It would be perfect to have this as standard feature and not through an add-on.

Hello,

It appears that Alteryx does not accept .svg (or other vector image format) for icons (I think to custom macro icons), image in comment, etc...

I think that would be a great idea, especially to manage web integration and support of different resolutions.
here an example of a svg logo I made :
Logo_BD_Market_vectoriel.svg

As you can see you can zoom in/out without loose quality.

 

For reference, here is long blog post about why SVG is great : https://bumpsetcreative.com/10-reasons-the-image-format-svg-is-rocking-the-internet/

 

To sum it up :

1) SVGs are widely supported

 

2) SVGs are speedy

 

3) SVGs scale perfectly

 

 

4) SVGs are high resolution

 

5) SVGs can be styled through CSS

 

6) SVGs can be animated

 

7) SVGs can be rearranged easily

 

8) SVGs support transparency

 

9) SVGs are great for readability

 

10) SVGs stand out

When working with R code and errors occur, the application needs to show which line the error happened on.

Who needs a 1073741823 sized string anyways?  No one, or close enough to no one.  But, if you are creating some fancy new properties in the formula tool and just cranking along and then you see that your **bleep** data stream is 9G for nine rows of data you find yourself wondering what the hell is going on.  And then, you walk your way way down the workflow for a while finding slots where the default 1073741823 value got set, changing them to non-insane sized strings, and the your data flow is more like 64kb and your workflow runs in 3 seconds instead of 30 seconds.  

 

Please set the default value for formula tools to a non-insane value that won't be changed by default by 99.99999% of use cases.  Thank you.

 

 

When you add a tool in the canvas, the annotation is automatically set (for example the formula, or connection configuration etc). You can then customize the annotation text in the "Annotation" tool's tab. But sometimes it can be useful to revert to the "automatic" annotation, and it doesn't seem possible once you set it to something different.

 

Apparently there is currently no way to reset a tool's annotation text to the automatic value.

 

I've found a way to do it by editing the xml content of the file : as far as I know you just have to delete the <AnnotationText>[...]</AnnotationText> tag and reload the file, and the annotation gets back to the default "automatic" value, which is still present in the <DefaultAnnotationText> tag.

 

I think a simple button in the tool's annotation tab to reset it would be nice.

 

Thank you!

Top Starred Authors