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.
Can we have an option to save a workflow in a prior version for backward compatibility? I think Tableau offers this functionality.
If I have 2019.4.8 and a colleague has 2019.1.x, I cannot share my workflows because my colleague will receive a notice that the workflow was built in a newer version. I want to be able to save my workflow in 2019.1.x and send to my colleague.
This is predicated on the workflow not containing any tools/features not present in the older version. In that case, give me a warning about the specific tools/features that are not backward compatible. Thank you.
I love using the YXI installer for distributing custom macros; I have even used to install an entire palette of macros. However, when installing to a new, user-defined palette, I still need to instruct users to copy custom_palette.png into C:\Program Files\Alteryx\bin\RuntimeData\icons\categories.
It would be nifty keen if we could add custom_palette,png into the config.xml file and have the YXI installer place the file into the \icons\categories directory.
I imagine that some checks would need to be added, to ensure we weren't overwriting icons for the built in palettes.
Currently when you add an event to notify you of workflow failure / success - you have to enter the SMTP settings every time. It would be more efficient to set this up as a user setting which can be used for the default across all canvasses that this user creates.
I rarely use the Group By tab on batch macros, but it's unfortunately always the first tab that pops up. When I have a questions tab on a batch macro, it would be great if it appeared first (ie I should see the questions tab when I click on my batch macro.) Thanks!
It would be useful to be able to select a single container (containing a data input) or multiple containers using Shift, and run those and only those.
When building a new element to a larger workflow, I often enter a new Input in a new container, the ability to run just that container without having to turn off all my other containers would be really useful in speeding up the start of joining things together.
On shared collection , users have access to the collection shared by other team members. When users copy the ‘Publish to Tableau Server ‘ tool from one workflow to another it copies with the credentials embedded in the tool as well.
As user John Doe’s workflow publishes data on to tableau server with Peter’s credentials as the publish to dashboard tool was copied from Peter’s workflow.
The concern really is Users copying tools from one workflow can really copy the credentials as well. Enhancement to the publish to Tableau tool would be much appreciated.
Could you please change the order of workflow names in the 'Active Documents' button to be ordered in the same order as the workflow tabs and not alphabetically as it currently is?
When you have more than 5 workflows open (or less if they have long names) it's so tricky to quickly and easily cycle through them to find the ones you need. This is especially important when demoing, training and presenting to others!
Please enhance the dynamic select to allow for dynamic change data type too. The use case can be by formula or update in an action for a macro. If you've ever wanted to mass change or take precision action in a macro, you're forced to use a multi-field formula. It would be rather helpful and appreciated.
I love the new right click and duplicate workflow feature, but I think the duplicated workflow that opens, should open next to the original workflow and not at the end of all of your already open workflow tabs...
When writing a good amount of code, it is easy to get lost in a sea of parentheses. Just when you think you're all done, you get an error that can force you to scour through your code to find the missing, extra, or misplaced parenthesis.
A common feature today is to highlight a parenthesis when its partner is clicked on. This instantly lets you know if you have the wrong number of them and where.
I didn't think this was that important early on in Alteryx, at least for me. Formulas were meant to be short and easily readable at a glance. Now as I dig deeper, there's R, Python, SQL and other text-heavy inputs.
I don't need a full-fledged text editor in Alteryx, but I would love some quality of life features like parentheses matching.
When building custom tools for Alteryx using the Python SDK, there is no current way to test these outside of the Alteryx Designer.
This means that your development process is:
- write some code (no code-sense; intellisense; auto-complete because Jupyter; VSCode; Visual Studio; etc cannot access AlteryxEngine or any of the other imports)
- copy that .py module into your C:\Users\<username>\AppData\roaming\Alteryx\Tools\<toolname>
- fire up Alteryx
- drop this new custom tool on a canvas
- run it to see if you get any errors
- then copy these errors out of Alteryx result window into Notepad to be able to read them
- then go back into your development environment to make changes
This is very painful, and this will directly scare most people away from learning how to create custom tools since it's not only inefficient - but also scary and frustrating for beginners.
Could we instead create mock python libraries; and a development harness (like Google does with Android development in Eclipse) in this SDK where:
- you have full code intelligence (intellisense, autocomplete)
- you can simulate engine events in a test harness (for example in the Android SDK; you can simulate the user rotating their phone, turning off GPS, hitting a volume button, etc).
- you can also write test cases which can run automatically
- then once you know that your tool will work - only then you drop it into the Alteryx Designer environment.
NOTE: This IDE way of thinking also allows you to bring the configuration pieces (like number of inputs; etc) out of raw code and into configuration options.
Although you may be able to do remote debugging by using platforms like PyCharm - that really does not give you the full ability to check in the code of your tool; along with all the test cases; in a harness that allows you to automatically check different events; or to make sure that your tool works in the test harness before deploying.
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?
It would be great if there was an output option for excel files where you could overwrite the data in the sheet, but keep the formatting in the sheet. Similar to how the Paste Values option works in Excel. This would allow me to create a template with data validation, conditional formatting, column widths, cell fill colors, etc and set a workflow to run on a schedule and just paste the data into the existing template.
To get around this right now I have to output it to a separate tab and then paste the columns as values over the existing template. This is fine unless I am out of the office and need to bother someone else to do it. I know there have been many times where i wish this was an option outside of the report I am currently building. I am honestly surprised I couldn't find an idea already submitted about this!
At present, Alteryx allows for users to run 2 versions of Alteryx at once - one installed using the "Admin Installer" and one via the "non-admin installer"
However, in corporate environments, only the Admin Installer can be used (all installers are repackaged for corporate environment / endpoint management)
This leads to a situation were we cannot run two or more different versions of Alteryx on one machine (like you can with Visual Studio or other platforms). This also prevents us from participating in the BETA program because the BETA version would overwrite the users's current version. Finally - this also makes version upgrades more risky since we cannot run the new version in parallel for a period to evaluate and identify any issues.
Request: Please can you change the installer for Alteryx to default to parallel install per version - so that a user can run 2019.1; 2019.2; and 2019.2 BETA on one machine in a way that is fully isolated (i.e. no shared components - have to be able to uninstall one instance cleanly and leave the others in a fully functional state).