Duplicates : counting them, not removing them?
Whats the best way to count duplicates in a table using ETL and or Beast mode on a card? Lets say I have a table of data that shows me how many times each class uses a specific tool so I end up with a table with a list of classes who have used the tool. And, each class can have multiple entries showing each time they included that tool.
I want to add a column to the table that counts how many times each unique class uses the tool so in the card to visually show the data, I want to show a list of unique classes that used the tool and then the extra column showing the number count of how many times that class used the tool.
Thanks!
Answers
-
Hi @nicolac
Can you just do a Count(`field`) in a beast mode or do a count in a group by tile (grouping by the class) in an ETL to get the number of times each class used the tool?
Alternatively you could just select Count from the aggregation option on your field in analyzer.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
You should be able to get the results that you are looking for with @GrantSmith 's suggestion.
I have done something similar to measure page, or card views within Domo. I use COUNT(DISTINCT `UserID`) to show many how many different users view the page, and then COUNT(`UserID`) to measure how many page views those users have had.
I can also show this information over time in a graph to pick up on trends. By combining count distinct and count values, I can see not only which page had the most total views, but also which page is being used by the most users (which won't always be the same)
For example, I can see that I've had 179 users hitting these pages this year, but only 164 have used the main landing page. This means that at least 15 users have bookmarked our subpages and are not viewing the main page at all this year. If this number were to continue growing, it would cause me to rethink placing announcements on the main landing page as not all of our users have been using it.
Either way, this is easily handled by a beast mode. I would actually recommend it so that your numbers will adjust as you add filters or change the timeframe that the card is looking at.
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman1
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 294 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 607 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 707 Beast Mode
- 49 App Studio
- 39 Variables
- 667 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 44 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 115 Manage
- 112 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive