Best Of

Filter out happy people

So, that's a strange title… Here's the deal:

We have survey data about support tickets. It's pretty basic— just Good, Neutral, and Bad as responses. A person can be interviewed more than once. So, I've been creating a visual of "Sentiment by user". It's a stacked bar graph with the following:

X axis: The user's name
Y axis: Count of user sentiment
Series: User sentiment

So, with a little formatting and sorting, we end up with Bob on the X axis with a tall blue bar since he's always happy but needs lots of help. Jane has a shorter blue bar with a little red top bar since 1 support ticket went badly but the rest were good. Joe has just a tall red bar since he's never happy. And so on…

So, I'd like to include only the people that have at least one non-happy (that is, neutral or bad) response. This would, using the examples, exclude Bob. How could I do that? Thank you.

Name	Date	Disposition
Bob	8/25/2024	Good
Jane	8/21/2024	Good
Joe	8/22/2024	Bad
Bob	8/10/2024	Good
Bob	8/12/2024	Good
Joe	8/9/2024	Bad
Jane	8/8/2024	Bad
Joe	8/26/2024	Bad
Bob	8/26/2024	Good
Bob	8/16/2024	Good
Joe	8/26/2024	Bad
Jane	8/17/2024	Good
Jane	8/11/2024	Good
Bob	8/14/2024	Good
Bob	8/18/2024	Good

froghunter

2

Dataset Beast Modes and Sandbox

From a sandbox perspective, I know that it doesnt actually promote/copy datasets from one instance (dev) to another instance (prod). However, we have some Dremio federated datasets currently in dev with a bunch of dataset calculations on them and we're trying to avoid having to re-create all the beast modes everytime we're ready to link/move in federated dataset into prod. I know you can duplicate/copy beast modes via the Beast Mode manager, but it seems that only targets datasets in the same instance.

Does anyone have any insights or ideas on how sandbox works with calculations on the datasets as far as the schema that does get mapped as part of the promotion process? I know beast modes are promoted with cards, but I cant find much information on dataset level calculations.

Or, is there some other non-convoluted that won't need us to create some custom programmatic API way to copy dataset beast modes between instances?

Thanks!

DomoDork

1

Re: YOY % Change

Hi @TanyaB I'd suggest taking a look at this page for more detail on how to do Period over Period transforms:

Sample Beast Mode Calculations: Period-over-Period Transforms (domo.com)

I think what you're asking about here is in the section: Variance % ((CY - PY)/PY)

JasonAltenburg

1

Re: Mass Deploy Drill Paths

Please product team pick either of these options up! This would be a massive quality of life improvement! Either Mass deploy or choose an existing card to insert are both great solutions to this issue. I'm so sick of building the same drill table over and over again!

lhrogersiv

2

Re: NUMBER_FORMAT function

please do this, major upvote, much needed…

katdoesIT

2

Re: Beast mode 'Case when' for if a date exists

CASE WHEN `Lead Stage` IN ('Move In', 'Moved In', 'Deposit') THEN 1
WHEN `MOVE_IN_DATE` IS NOT NULL THEN 1
ELSE 0
END

You can use IN to check for multiple values

GrantSmith

1

Re: Percent of Series?

@Data_Devon I'd suggest using a tooltip for your data label instead of the default macros. Then you can create the percentage in a beast mode and add that to the tooltip1 field in analyzer.

MichelleH

1

Re: Stacked Bar from this dataset config?

If you transform your dataset

Category	Value	Type
Budget	343	planned
Budget	3432	carry-over
Budget	123	unplanned
Forecast	444	planned
Forecast	4432	carry-over
Forecast	145	unplanned
Actuals	200	planned
Actuals	3302	carry-over
Actuals	80	unplanned

Then create a stacked bar using category on the xaxis, value on the yaxis, and type in series, you get this:

ArborRose

2

Re: Stacked Bar from this dataset config?

Ideally, your data would look like this:

Category Type Value

Budget Planned 343

Budget Carry-over 3432

…

The easiest way to get it in that format is with MagicETL. There's probably a more elegant way to do it with a dynamic unpivot, but to me, the easiest to understand is to just select the two columns, add a category column and stack the results on top of each other:

Once it's in that format, the stacked bar is easy:

DavidChurchman

2

Re: Python Scripting in Magic ETL | Iterating through close dates to get unique account id values

Wait, I forgot to write back my data frame!

cmoreno

1