Alteryx, like any tool, has some best practices to follow so you get the best output. We will look at 5, but if you want to find out more, look for the PDF with 24 Best Practices that was shared in the Alteryx community.
1. Eliminate any browse tools:
The browse tool is beneficial during the development phase as it helps the user to see/review the entire dataset extracted from a connected tool. However, once the workflow is completed, the browse tools offer no value for two reasons:
1. They are distorting the view of the workflow
2. They are creating a temporary yxdb (Alteryx database) which makes the processing longer.
2. Use the most appropriate variable names & data types By applying this practice, you will have a much clearer view of your variables and subsequently save time as you would not be attempting useless transformations, e.g., trying to perform a numeric operation on a string.
3. Documenting with Descriptive Titles:
There are many good reasons to document your workflows with descriptive titles, including making it easier to hand-over to another client or colleague, and returning to your previous work at a later date.If workflows happen to be dependent, there is also value in numbering them. By using numbered titles, it will be much easier to decipher the workflow dependency by simply looking at the titles and having a good idea of what it does without opening each workflow.
4. Address errors and warnings right away:
Addressing errors and warnings as soon as they arise is an Alteryx best practice. It’s important to correct errors early, so you don’t implant logic errors into your workflow.Alteryx highlights errors by placing an exclamation mark below the tool in which the error occurred. However, conversion errors and warnings can be found by looking at the tool reference (in parentheses after the tool name) in the results pane.
5. Explore data using subsamples:
When you're first developing your workflow limit the number of records you read in. This allows faster processing - which will save you time - especially when working with a big dataset.To limit the number of records navigate the the Configuration window in the "Input Data" tool and define a limit.
1. Eliminate any browse tools:
The browse tool is beneficial during the development phase as it helps the user to see/review the entire dataset extracted from a connected tool. However, once the workflow is completed, the browse tools offer no value for two reasons:
1. They are distorting the view of the workflow
2. They are creating a temporary yxdb (Alteryx database) which makes the processing longer.
2. Use the most appropriate variable names & data types By applying this practice, you will have a much clearer view of your variables and subsequently save time as you would not be attempting useless transformations, e.g., trying to perform a numeric operation on a string.
3. Documenting with Descriptive Titles:
There are many good reasons to document your workflows with descriptive titles, including making it easier to hand-over to another client or colleague, and returning to your previous work at a later date.If workflows happen to be dependent, there is also value in numbering them. By using numbered titles, it will be much easier to decipher the workflow dependency by simply looking at the titles and having a good idea of what it does without opening each workflow.
4. Address errors and warnings right away:
Addressing errors and warnings as soon as they arise is an Alteryx best practice. It’s important to correct errors early, so you don’t implant logic errors into your workflow.Alteryx highlights errors by placing an exclamation mark below the tool in which the error occurred. However, conversion errors and warnings can be found by looking at the tool reference (in parentheses after the tool name) in the results pane.
5. Explore data using subsamples:
When you're first developing your workflow limit the number of records you read in. This allows faster processing - which will save you time - especially when working with a big dataset.To limit the number of records navigate the the Configuration window in the "Input Data" tool and define a limit.