This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
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?
Before 2019.3, you could edit the default annotation that Alteryx generated, but now if you go to change the annotation it's either 100% your own annotation or 100% the default annotation left by Alteryx.
I found it useful to retain a portion of Alteryx's default annotation (e.g., a long table name when setting up a database connection) while being able to cull the superfluous portions (e.g., didn't want to see the Source / Catalog). Now, if I want to retain the Table name I have to type it out.
Now that we have a Snowflake Bulk Loader option, it would be great to utilize the built-in Snowflake internal staging. This eliminates the need for an end-user to have the technical know-how or access to IT resources to utilize a separate S3 bucket and generally reduces friction in the process.
Where it stands now, only a file input tool can be used to pull data from Google BigQuery tables. The issue here is that the data is streamed and processed locally, meaning the power of BigQuery processing isn't actually being leveraged.
Adding BigQuery In-Database as a connection option would appeal to a wide audience. BigQuery is also standard SQL compliant with the SQL 2011 standard, so this may make for an even easier integration.
When you do a search for a tool, don't zoom to a blank area of the canvas (because that's where the tool would have been with an enabled container). So when a container is disabled, zoom to the actual container instead containing the tool you're looking for or temporarily enable the container so we can see the tool?