Symbol + Stacked Bar - States on X axis are not grouping together.
Hello, I have a chart where I want to be able to group together the different series by state but it keeps separating them out on the x axis. Not sure if it has to do with the separate beastmodes on the series.
I have 4 separate beastmodes written where it looks for the average days in each scenario and have added all 4 of them to my series. I also look for a median days in my y axis.
Any information on how I can group my States together? Please let me know if you need more details.
Thanks!
Comments
-
Hard to say what's going on without seeing a data sample. It's normally due to the way the data is structured or the settings on the chart configuration.
1. Check your formulas. Make sure you are aggregating data based on the states. Since you calculate average days and median days, each beast mode should properly structures to aggregate these by state.Average days:
AVG(`Days`)
In your chart configurations make sure the state field is set as the x-axis. On series, add your beast modes as separate series. Each series should represent different metrics (average days, median days, etc). But they should all plot against the same x-axis.
** Was this post helpful? Click Agree or Like below. **
** Did this solve your problem? Accept it as a solution! **0 -
My set up:
Sample of one of the beastmodes on my series. (They are all the same.)
CASE WHEN
PRODUCTIONBY
<> 'NPS' ANDSLAStatusAverage
<> 'Within SLA' THEN AVG(DAYS_CUSTOMERVIEW
) ENDExample: FL is shown twice and not grouped together.
I am not sure if this is enough detail for you to help but thanks!
0 -
I would guess that the issue is because you are only aggregating on one part of your case statement. Try putting AVG() around your 'Within SLA' field in your case statement and see if that helps. You could also try it like this:
AVG(CASE WHEN PRODUCTIONBY <> 'NPS' AND SLAStatusAverage <> 'Within SLA' THEN DAYS_CUSTOMERVIEW END)
Finally, I would try removing your fields and adding them back one at a time and see if one field is the problem field.
**Check out my Domo Tips & Tricks Videos
**Make sure to any users posts that helped you.
**Please mark as accepted the ones who solved your issue.0 -
That was some great feedback. Unfortunately, neither solution worked. Averaging around the case statement just lead to an error in the beast mode. Apparently there's an issue with Averaging a beast mode that has any reference to an average within it.
In the end, what we need to do is look to see if the average of Value 1 is > the average of Value 2. If that's true, then we need to see value 3.
0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 295 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 608 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 710 Beast Mode
- 50 App Studio
- 39 Variables
- 668 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 45 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 116 Manage
- 113 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