ColemenWilson Coach

Yes, but it would require some ETL work. The way I have done this in the past is create 2 new fields: Max value and Min value . Then plot those on your line chart the same way you have plotted the HIGH LIMIT and LOW LIMIT.

These are currently the options for where to show data labels: This is a great idea and I would recommend putting it in the ideas exchange: https://community-forums.domo.com/main/categories/ideas You can of course see the max and min values by making sure these are uncheck in the chart properties:

Hi Larry, It will work when the conditions are met, when they are not it will be completely null. The solution here is to account for when the holds do not = 'Y' by adding ELSE to your case statement: CONCAT( CASE WHEN New Logo Hold = 'Y' THEN 'New Logo Hold' ELSE '' END, CASE WHEN My Product Customization Hold = 'Y' THEN…

So per 100 is the same as a % (25 per 100 = 25%). So basically all you need is a count of readmissions divided by a count of discharges on a bar chart with provider on the other axis. Then display this as a percentage. Is this what you were thinking?

Hmm it is validating for me when I replicate it in my instance. Can you share a screenshot of your beastmode?

Should work if you remove the then 'Refined' part at the end and move the session_id . See below: COUNT(DISTINCT CASE WHEN event_name NOT LIKE '%select_item%' and event_name LIKE '%search%' THEN session_id END ) Keep in mind that you are using wildcard characters around select_item and search which will return values that…

This is possible and something we have implemented. Using Domostats and Domogov datasets you can create tables that show all the card, pages, datasets, etc… in the instance with the relevant descriptions, update schedules, owners, etc… For example, here is our dataset glossary:

True there is no group ownership, but there is a way to lock beastmodes so only the owner and administrator can edit them.

Ah yes from a dashboard view you would need to change the interaction to "Drill in place" as you mentioned. For others viewing this, this only works if a drill path has been created for the selected card, if it has not then you will not be able to select this option as shown below:

You can create a custom drill down. Follow the images below for the steps: In your custom drill view create a table card with the fields you listed.

If I were needing to do this, I would use a SQL dataflow. Something like this: SELECT `date` , `incident id`, `date` as `date 2`, COUNT(DISTINCT CASE WHEN `date` < = `date2` THEN `incident id` END) as 'Running Total' FROM 'Dataset' WHERE `status` <> 'Closed' GROUP BY `date 2`

You'll want to use the Line + Grouped Bar chart type and then go to chart properties > General > Number of Running Total Lines. See below: Configure the chart so that Backlog is a running total

Hi Dheeraj, it seems like you have built the card. What are you having trouble with?

Hi Ganesh, this is currently possible using pfilters. Here is some documentation on how to use them: https://domo-support.domo.com/s/article/360042933114?language=en_US

This can be done a few different ways. "DataSets History" report in Domostats. Has the full history for all connectors including: Run status Execution Type Number of API calls Updated Rows Even Bytes inserted If you don't need that much detail or a full history, you can use the "Datasets report" in Domostats which will…

@marcel_luthi agreed on the complexity. That is why I was thinking ETL over beastmode(s) - especially for #5.

Wow I'm honored! Thanks @GrantStowell ! I don't get to dig into the weeds as much in my current role as I used to, so the forums are a great way for me to stay sharp and also keep learning new things. I've been having a great time solving users issues. Next milestone: coach status!

@marcel_luthi Nice catch! Yes your additional logic is needed.

I was able to do this in magic ETL. First, use the group by tile to get the max skill score for each product: Second, join that data back to your input data on product: Third, use the formula tile to calculate the normalized score: Then, in a card you can create a beastmode to get your average normalized score: I am a bit…

Okay is the total engagements field populated every day during the duration of the campaign? If so, this is how I did it: ETL overview: Step 1: Add Quarter and Year if not already in your data Step 2: Use 2 group by tiles to get the minimum date and maximum date for each campaign within each quarter. Minimum is shown…

Could you clarify what you mean by full and partial quarters? In your beastmode you only use a single date which would always fall in a "full quarter". Do you need to use a range of dates, meaning your campaign started on one date and ran through to another date and you wanted to only count those that ran from the very…

My voice has been heard! Thank you Grant!

As you mentioned, the only default way to show the data last updated in smart text is to show "7 hours ago" for example. You could show the day and time a dataset last updated using a single value card on the top of a dashboard. You can get the exact time the dataset last updated in the Domostats "Datasets" dataset.

This is best done in a dataflow. There is a free dataset called "Calendar" that you can find in the appstore by searching "Domo Dimensions" and then selecting "Calendar.csv" from the available options: Next, you will want to bring this into your ETL and apply a filter to only return wednesday values. Then, use a group by…

COUNT(DISTINCT(CASE WHEN `credit score` < 660 THEN `loan id` END)) / COUNT(DISTINCT(`loan id`)) Keep date as x-axis and then drag this to y-axis.

Not sure if you'd already tried this, but you could just use the 100% stacked bar chart type.

No because you will break out the group by into a separate line in the dataflow. So from you input dataset there will be two lines: 1. All rows of data 2. 1 unique row for each ID. Then you will left join the unique rows for each ID with the original input that has all rows of data. No rows of data will be lost.

This is best accomplished in a dataflow. Using magicETL you can use the group by tile and group by ID for the field Email and select the first non-null value option, then, with 1 email per id from the output of that tile, you can join that with you data on the ID field. Let me know if you have any questions!

There is no way to ignore these rows in the connector itself, the best solution is to remove those rows in an ETL as @MichelleH suggests.

I would do it in a dataflow. In Magic you would use the formula tile to get the flag on rows with a 100 in them and then use the group by tile to group on SO # and then join on SO # back to your granular data. Then you'd have a flag for each SO # that has an order product in it with 100 as shown in my last screenshot…