Change Columns Based on Filter
Dojo Community,
I am trying to rebuild a Tableau function that our organization uses quite frequently. We have a series of tables in Tableau that we use to steer our marketing. We are slowly moving away from needing and using those tables throughout out organization, but for the time being I need to get people in Domo.
The function in Tableau allow a Filter (Example a Page Filter) to change the values in a single column.
I have attached a few screen shots of how this is done. Essentiallly the first view of the table that someone sees has a "Date Column" generally Year-Month. Then on the page there is a "Weekly Filter" that will then change the "Date Column" to Year-Week and then the same for date it will then change the "Date Column" to Year-Month-Date.
I hve not found a possible way to do this in Domo, but I thought there might be someone out there who has solved this either through a Stored Procedure, or other custom Beast Mode calculations.
Comments
-
This can be accomplished with filters depending on how your data is structured.
My guess is that the Tableau data set is essentially stacking the data tables on top of each other with one column called `Date` that has values ('Daily', 'Weekly', 'Monthly', 'Quarterly', 'Yearly') and another column called `Date Channel` that provides the values you are seeing in the visualization.
If the data is not set up this way, then you will need to do some data engineering via a dataflow prior to getting an output like this.
I have found that the best way to get people into Domo is not to try to copy their existing reports, but to really try to understand what is being done with the report. What question do they want to use this data to answer and how can Domo provide that anser. I have found that we typically end up dramatically changing the output that end users are consuming, but they are getting to their answers quicker so they prefer it.
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman0 -
ST_Superman
Thanks for the insight here. I was trying to avoid stacking the data just to accomplish this requirement. It is one that is pretty straight forward in Tableau.
I do however agree with you statement on user adoption. And for the most part we have implemented over 140 people in less than 2 months with very little rebuild. There are as you know some issues and requirements that are specific in nature and that unfortunately need to be rebuilt in order to get further adoption.
I will look at stacking the data and see how this does for us. I hate the idea of a dataset that size, but I understand the limitation.
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 738 Beast Mode
- 56 App Studio
- 40 Variables
- 684 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 46 Workflows
- 10 DomoAI
- 35 Predict
- 14 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 123 Manage
- 120 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive