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.
Platform Product: Predictive Issues – Working with Alteryx Customer Support Engineers (CSEs)
(for use by CSEs and Alteryx Customers)
To EXPEDITE the resolution of your case, please include the below information.
Predictive - Requested Information
*** Suggestion: copy/paste the questions below and email the supporting documentation to firstname.lastname@example.org
1. Detailed Description of the Issue
2. Screenshot of Alteryx Version
3. Version of R
4. Version of Predictive Tool
5. Ensure not a data issue
6. Set to “Show All Macro Messages” on the Workflow Configuration, run workflow and send screen shot
7. Please send a copy of your workflow and macro (*.yxmd or *.yxzp)
8. For R Tool – work outside of Alteryx? Provide code
9. Engine Log (if applicable)
Predictive – Requested Information (Detailed Instructions):
1. Detailed Description of the Issue – What issues are you having? Has it worked in the past? When did the issue start? Are all users affected or just some? What are the steps to reproduce your issue? What have you tried to resolve the issue? Have you searched the Alteryx Community using the R label or the Predictive label?
2. Screenshot of Alteryx Version– Our CSEs need to know the precise version of Alteryx so we can replicate any issues. In Alteryx, click Help >> About and provide a screenshot.
The screenshot will include whether it is Server or Designer. In addition, whether it is “Running Elevated” Admin vs. Non-Admin.
3. Version of R – Go to C:\Program Files\Alteryx to find the Version number
4. Version of Predictive Tool – To find the version number, right click on the Predictive tool, and click Choose Tool Version.
5. Set to “Show All Macro Messages” in the Workflow Configuration, run your workflow and send a screen shot
Click the Workflow Configuration>Runtime tab and check “Show All Macro Messages”. Run the workflow, and send a screenshot of the error or exact text of error - Click CTRL-Print-Screen to capture the error and paste into your e-mail.
Note: You may wish to Google the error text research the issue, especially since the majority of the errors from the R macros are from R itself, and not Alteryx Designer or Engine. The Knowledgebase is also a great place to search the error text as well!
6. Ensure that it's not a data issue – Do you have NULL values in your data? Are there unique identifiers as predictor variables? Are the data types of variables appropriate? Do you have enough records? If we open your workflow and don't see a Field Summary tool, we're sending it back.
7. Please send a copy of your workflow (*.yxmd or *.yxzp) and sample data if possible. Either create a .yxzp and include macros and data by clicking Options>Export Workflow. Or, include the workflow *.yxmd and sample data if possible.
8. For R Tool – work outside of Alteryx? Does your R code work outside of Alteryx? What IDE are you using (RStudio, Microsoft R Client)? What is the version of the IDE? Are you using custom packages? Please provide the code.
9. Engine Log (if applicable) Engine Logs are a great way for us to get to the root of the problem. We look at errors and warnings. For the Alteryx Engine logs, please include the logs that reflect the time of the error/crash (the logs immediately before and after the error/crash). Before sending the logs, recreate the issue, and then send the latest logs.
Use Alteryx App - Server Logs the easy way! OR…
Default Paths: Engine Logs (\ProgramData\Alteryx\ErrorLogs)
If you have Server, and do not have logs in the pathways above, click Options >> User Settings >> System Settings, and note the paths that the logs are written to. Then locate and send the logs from that location. If the path is not yet set, pick a path, rerun the workflow to create the error, and then send the logs:
Locating the path of your Engine logs:
One Stop Shop for Predictive Resources
Sometimes, we don’t rely on an entire dataset to create an optimized solution. Sometimes, it can be as simple as solving a basic question. Consider the following problem that uses the optimization tool:
There is a clothing manufacturer has 750 sq. feet of cotton textile and 1,000 sq. feet of polyester. Every pair of pants needs 1 sq. feet of cotton and 2 sq. feet of polyester. Every jacket needs 1.5 sq. feet of cotton and 1 square feet of polyester. Due to manufacturing restrictions, no more than 400 jackets can be produced in a day, and a minimum of 200 pairs of pants are required to be manufactured. The price of the pants is fixed at $50 and the jacket, $40.
What is the number of pants and jackets that the manufacturer must give to the stores so that these items obtain a maximum sale?
Our job as analysts is to first identify 3 basic groupings to identify our optimization:
1) What our decision variables are and what our objective is
2) Any constraints with respect to decision variables
3) Any bounds and types (continuous, binary, integer) to consider for our decision variables
First, the decision we need to make is the number of pants and jackets the manufacturer should manufacture. Thus, the number of pants to make and the number of jackets to make are our decision variables. Let’s name our decision variables:
x=number of pants
y=number of jackets
1) Identify the Objective
Based on our problem above, we have to identify what our objective is – in this case we want to be able to maximize revenue. Revenue is nothing more than a function of the number of pant/shirts sold at their respective pricing. Therefore, our objective appears as:
Maximize Revenue = 50x + 40y
In the tool configuration, select the input mode "Enter the model manually," and based on the fact that we are looking to maximize profit, be sure to turn on the Maximize Objective toggle. Next, specify the variable list and select “+”. Now that we have an objective already sorted out, enter the objective using the same variables that we just specified.
2) Identify the Constraints
Sometimes a table is a great way to sort out what constraints may look like. Below, I have created a matrix which will help me identify and rules that may alter my objective.
1 sq. feet
1.5 sq. feet
750 sq. feet
2 sq. feet
1 sq. feet
1000 sq. feet
Based on this table, I can create my constraints. For the first row, I know that whatever number of jackets and pants I produce, I have the manufacturing constraint of only 750 sq. feet of cotton. This 750 sq. feet can be used for any number of jackets and pants, but I do know that they take different amounts of cotton to manufacture. Thus, I’ll specify the amount of cotton used as x+1.5y<=750. Similar logic for polyester will result in my second constraint of 2x+y<=1000.
Enter the constraints x+1.5y<=750 and 2x+y<=1000 into the constraints tab of the configuration window.
*The solver in R requires all variables to be on the left hand side of the equality/inequality sign. Although the mathematical equivalent of x+1.5y<=750 could be 1.5y<=750-x, it will fail with the error: R.exe exit code (3221225512) indicated an error.
3) Identify Bounds and Types
Finally, we need to identify the bounds – namely, manufacturing limits. By default, we know that we cannot negatively manufacture pants or jackets, so the lower boundaries should be 0. However, there was a requirement that at least 200 pairs of pants needed to be manufactured per day, so we will say that X needs to be greater than 200 with no upper boundary limit. Conversely, we have jackets with an upper limit of 400/day. The range of manufacturing jackets could be anywhere from 0 to 400!
Bounds: 200<=x<=+inf and 0<=y<=400
Enter the limits into the bounds & types tab in the configuration pane and run the tool.
4) Reviewing the Results
In the “S” (static) output, you can view the objective outcome and the values used for each variable to achieve the maximized objective. In this case, we can see that based on the material we have a manufacturing limits, we can have as much $28,750 in sales if we use the existing resources to manufacture 375 pairs of pants and 250 jackets. Also, feel free to view you interactive results that return from the "I" output!
First added to Alteryx Designer in version 10.6, the Optimization Tool is a member of the Prescriptive Tools (included with the Predictive Tools installation) and allows you to solve optimization problems. Mathematical Optimization is the selection of the best possible option(s), given a set of alternatives and a selection criterion. In this Tool Mastery, we will review the inputs, configuration, and outputs of the Optimization Tool.
With the release of 10.6 came awesome new features, and an upgrade in the underlying R version (from 3.1.3 code named "Smooth Sidewalk," to 3.2.3 code named "Wooden Christmas-Tree"). Using the incompatible R version will cause errors in your R macros.
Simply make sure that your Predictive Tools download is the version compatible with your Alteryx Designer version:
Users on 10.5 should continue to use the R3.1.3 version.
When using Alteryx and Microsoft Revolution R Enterprise, a separate predictive tools install is required (in green). For details, see the Alteryx and Revolution Analytics Integration Guide.
And remember to use the non-Admin Predictive version with non-Admin versions of Alteryx Designer.
To install Predictive Tools for Alteryx 10.0, go to Previous Releases. For Alteryx 9.5, within Designer, go to Help > Install Predictive Tools.
We love helping users be successful with Alteryx, and this means providing a ton of great resources for getting started, learning more, and keeping you up to date with all the amazing stuff we're doing here at Alteryx… and the most compelling is Predictive!
Check out the Predictive District on the Gallery. There are great macros, apps, and sample workflows to demonstrate some nifty new tools. This post by DrDan on the Analytics Blog gives an overview of what's currently available – stay tuned for additions!
One of my favorites is the Predictive Analytics Starter Kit Volume 1. It enables you to learn the fundamentals of key predictive models with an interactive guided experience. Examples include Linear Regression, Logistic Regression, and AB Testing, and demonstrates the steps necessary to develop the dataset needed for analysis, and then how to actually build these predictive models yourself.
With v10.6, we introduced the Prescriptive Tool Category, comprising the Optimization and Simulation tools, to assist with determining the best course of action or outcome for a particular situation or set of scenarios. The Engine Works Blog has an introduction to this toolset, plus an extensive use case demonstration.
If you need more Optimization and Simulation action, there are several sample workflows, including Fantasy Sports Lineups (hey, sports fans – blog post here!), a mixing problem, workforce scheduling, and more!
Speaking of use cases, the software itself contains a plethora of predictive sample workflows - and the installed Starter Kits show up here, too! Help > Sample Workflows > Predictive Analytics.
Of course, don't forget the Predictive Analytics help pages, for overviews and configuration tips.
Visit our Product Training page for On-Demand and Virtual webinars on everything Predictive – regression modelling, cluster analysis, time series… As always, please begin with Data Prep and Investigation! Can I mention the Field Summary Tool enough times?
Want to show off the interactive visualizations from the models you've built? This Knowledge Base post shows you how. Another Engine Works post outlines how to build your own Custom Interactive Visualizations (Part 1 and counting…)
For the most in-depth, resource-rich training on leveraging predictive analytics to answer your business questions, consider the Udacity Predictive Analytics for Business NanoDegree. It consists of seven courses focused on selecting the right methodology, data preparation, and data visualization as well as four courses that will equip you to use predictive analytics to answer your business problems.
But really, it all starts with the Community. Cruise the Knowledge Base posts, search for Predictive or other favorite keywords, follow the blogs… and for the love of Ned, just play with the software! It's how we learn 🙂