Scenario: I need to create missions in Alteryx Auto Insights for each account manager and head of department. Each account manager needs to insights from accounts relevant to them, while the head of department needs insights from all accounts both separately and as a whole.
Question: Should I create a separate dataset to create each user's relevant mission?
Solution: Here are 2 options + their pros and cons for you to consider when designing a dataset to be loaded into Alteryx Auto Insights.
Option 1 - Consolidated dataset. One source for all users
Sample dataset design
Pros | Cons |
- Standarised data and reporting - Each account manager and head of department can use the same dataset
- You only need to maintain 1 dataset for this scenario
- Works well if the datasets for each account manager are similar and can be consolidated (e.g. same measures and segments, columns can be easily renamed and appended)
- You can create a template mission, duplicate this, and add a filter to show only the relevant account for each manager without needing to re-create a new mission from scratch for each manager
| - Not suitable if there’s data restrictions in place for what data each account manager can view
- Not suitable if the dataset designs are very different for each account manager
|
Option 2 - Multiple datasets. Different datasets for each user type
Sample dataset design
Pros | Cons |
- Suitable if there’s data restrictions where account managers can only view and use data relevant to their own account
- Suitable if the dataset design for each account manager is very different (e.g. different columns in each dataset that cannot be easily mapped and appended)
| - Every time there’s a change to the dataset design, you will have to maintain this across multiple datasets
- Effort required to create each account manager’s mission from scratch
|
