Chaining Analytic Apps in Alteryx

Hello! Welcome back to your Alteryx advanced training.

In our last lesson, we introduced the concept of Chained Analytic Apps. You learned that they are a series of apps run in sequence, designed to create multi-step user workflows. We discussed the core logic of a "hand-off" (writing a temporary file), a "pickup" (reading that file), and a "trigger" (launching the next app). This conceptual understanding is the foundation for today's practical work.

Today, we'll move from "what" to "how." Our learning outcome is to configure a workflow to chain two analytic apps together. We will walk through the entire process of building and linking two apps to create a dynamic, cascading filter—one of the most common and powerful uses for this technique.

A Quick Refresher: Analytic App Components

Before we start building, let's briefly revisit what makes a workflow an Analytic App. Unlike a standard workflow, an Analytic App has a user interface. This is created using Interface Tools (like Drop Downs, Text Boxes, etc.) that allow a user to make selections or enter values. These user inputs are then used to modify the workflow at runtime via Action Tools.

Alteryx Designer Interface with an Analytic App Workflow — This image shows a workflow being configured as an Analytic App. Notice the Interface tools (Drop Down, Check Box) on the canvas, which create the user-facing questions, and the Action tools (lightning bolts) that connect those questions to the workflow logic.

Our chained application will consist of two separate Analytic App workflows that we'll build and then link together.

The Project: State and City Selector

Our goal is to create a two-step "wizard":

App 1: The user selects a State from a dropdown list.
App 2: The user is presented with a second dropdown list containing only the cities within the state they selected in App 1. The final output will be the data for the chosen city.

This requires chaining because the options in App 2 are entirely dependent on the user's choice in App 1.

Part 1: Building the First App (The Hand-off)

The first app's job is to take the user's state selection, filter the main dataset, and then create a unique list of cities from that filtered data. This list will be saved to a temporary file for the second app to use.

The workflow will look something like this:

Input Data: The complete list of states and cities.
Drop Down (Interface Tool): To present the user with a list of states.
Action Tool: To connect the user's selection from the Drop Down to a Filter tool.
Filter Tool: To keep only the data for the selected state.
Summarize Tool: To create a unique list of cities from the filtered data.
Output Data: To save this unique list of cities to a temporary Alteryx Database file (.yxdb).

To understand the core steps for creating this first part of the chain, let's turn to a guide.

How to create a chained App in Alteryx? - The Data School

The following article, 'How to create a chained App in Alteryx?', provides the exact steps for preparing the output file that will feed the next app's dropdown menu.

Please read the section titled 'Step 1 (a) in preceding app: Setting up the NAME & VALUE using summarize tool and output the file to Alteryx database.' This details a critical step: you must name the fields in your temporary output file 'NAME' and 'VALUE' for the next app's Drop Down tool to read them correctly.

As the article emphasizes, the output of your first app that is intended for the second app's dropdown must contain NAME and VALUE fields.

NAME: The text the user will see in the dropdown (e.g., "Los Angeles").
VALUE: The value that is passed into the workflow when the user selects that name (this is often the same as the name).

After building this workflow, save it as an Analytic App (e.g., Chained_App_1.yxwz).

Part 2: Building the Second App (The Pickup)

The second app's job is to read the temporary city list created by the first app, present it to the user, and then filter the main dataset to show the final result.

The workflow will be similar but with a key difference in the Drop Down configuration:

Input Data: The same complete list of states and cities.
Drop Down (Interface Tool): This time, it will be configured to read its list of options from an external source—the .yxdb file created by App 1.
Action Tool: Connects the user's city selection to a Filter tool.
Filter Tool: To keep only the data for the selected city.
Browse Tool: To display the final, filtered results to the user.

Let's refer back to our guide to see how to configure this "pickup" step.

How to create a chained App in Alteryx? - The Data School

The same article also shows how to configure the second app's Drop Down tool.

Now, focus on the section titled 'Step 1 (b) in succeeding app: Connect the output file from preceding app in the dropdown tool'. This shows exactly how to set the Drop Down tool to populate its list from an external source.

After building this second workflow, save it as another Analytic App (e.g., Chained_App_2.yxwz). At this point, you have two separate, functional apps. The final step is to link them.

Part 3: Making the Connection (The Trigger)

The "chain" is created within the configuration of the first app. You need to tell App 1 to automatically run App 2 when it finishes successfully.

This is done in the Interface Designer window (Ctrl+Alt+D or View > Interface Designer).

Chaining apps in Alteryx - The Data School

The following article, 'Chaining apps in Alteryx', provides a clear visual and explanation for this final, crucial configuration.

Read this short section starting from 'To link the apps...'. Pay close attention to the screenshot and the two options it points out: 'On Success – Run Another Analytic App' and 'On Success – Show Results To User'.

To summarize the steps from the article:

Open the first Analytic App (Chained_App_1.yxwz).
Open the Interface Designer (Ctrl+Alt+D).
Go to the Properties tab (the gear icon on the left).
Check the box for On Success - Run Another Analytic App.
Click the folder icon and browse to your second app (Chained_App_2.yxwz).
Crucially, uncheck the box for On Success - Show Results To User. This ensures the user isn't shown the temporary file from App 1, creating a seamless transition directly to App 2.
Save your changes to App 1.

Now, when you run Chained_App_1.yxwz as an Analytic App, it will ask you to pick a state, run in the background, and then immediately launch the interface for Chained_App_2.yxwz, which will be populated with the correct list of cities. You have successfully configured a chained app!

Conclusion

Today, you have moved from theory to practice by building a complete, functional chained Analytic App. This is a significant step in mastering advanced Alteryx workflows.

Key Takeaways:

Chaining requires creating at least two separate Analytic App workflows (.yxwz files).
The first app performs an action and outputs a temporary file (often a .yxdb) that will be used by the second app.
To populate a dropdown in the second app, the temporary file from the first app must contain fields named NAME and VALUE.
The link is created in the Interface Designer -> Properties of the first app, using the "On Success - Run Another Analytic App" setting.
For a smooth user experience, you should disable "Show Results To User" for the intermediate apps in the chain.

You've now had a hands-on introduction to building Analytic Apps. In our next module, we will dive much deeper into this topic. You'll learn about the full range of Interface tools available, how to design user-friendly interfaces, and how to add validation and error handling to create robust, professional-grade applications.