- Wireless tool connections: You can right-click on any tool and select “Make outgoing connections wireless.” This will reduce the visual clutter caused by a tool where the outgoing data branches out to many other tools.
2. Package Workflows Before Sharing
Packaging a workflow is very simple, and it could save the recipient of the workflow a headache too. In Alteryx, simply go to Options → Export Workflow. This will create an Alteryx Package file (.yxzp) which behaves like a zipped file. The great thing about the packaged workflow is that it includes all of the input files needed to run a workflow, so users do not have to search for files or re-do all of the input paths. The zipped folder also includes any supporting macros that are used in the workflow.
3. Use the Record ID and Unique Tools When Joining Data
This may be the most important tip I have learned over the past year of using Alteryx. Essentially, data joins can get messy. If you are pulling together a variety of data sources, it can be easy to get lost in the joins, and then all of the sudden you have an issue with duplicate records. Or, if you are working with a dataset for the first time, this technique can help you understand the primary keys of your tables and figure out how you should join them together.
The technique is simple: place a RecordID tool on the left side of the data, and then place a unique tool, with the RecordID field selected, right after the inner join output (J). This will ensure that none of the records in the original data stream (the left side) are duplicated. If you do see records coming out of the duplicate (D) output of the unique tool, it’s important that you understand why this is occurring. It could be that you have not structured your join correctly for your two tables.
4. Make Macros to Simplify Repetitive Processes
If you find yourself duplicating a process in a workflow by copying tools over and over, you likely have an opportunity to simplify your workflow by turning these processes into a batch macro. To learn more about batch macros, take a look at Alteryx’s “Getting Started with Batch Macros” post:
5. Save Your Workflow Before Running the First Time
This was an insight I learned from my manager: if you run a workflow without saving first (i.e. it will show as NewWorkflow1), it uses the processing power of the temp drive. If you save and then run, it uses the processing power on your C drive. I have seen this take a 10 minute run time…
Continue reading: https://towardsdatascience.com/7-alteryx-best-practices-to-simplify-your-life-b7155cdee56a?source=rss—-7f60cf5620c9—4