ST_Superman Domo Employee

You could get the total for each month as well as the overall total if you include a data table. This won't add the value to the legend, but will get the viewer a quick ability to see the total.

@user10986 You could try something like this: sum(case when `onboardingStatus` = 'did not start' then 1 else 0 end) / (sum(sum(case when `onboardingStatus` in ('started','did not start','future start') then 1 else 0 end)) over (partition by year(`signedOfferDate`), month(`signedOfferDate`)))

@user00344 that is a great idea to be able to set the default value with a function. Current_Date or Last 30 Days. Or you could even get creative with some case statements... @jaeW_at_Onyx Here is a quick and dirty video describing what I tried to explain in my post. In short, you had the right idea. Hopefully this…

... wow, you step away for a meeting and post when you get back and the issue is already solved. @NathanDorsch, I would be curious how you solved it, if you don't mind posting your solution as well.

Hi @NathanDorsch You can use the "Add Formula" tile to accomplish this. Just use this as your formula SUBSTRING(`address_field`, INSTR(`address_field`,'-sku-')+5)

@Airbear You may want to try adding an else statement to your beastmode then. Something like this: CASE WHEN `location_completed_timestamp` IS NOT NULL AND `count_id` = MAX(MAX(`count_id`)) OVER (PARTITION BY `cyclecountgroup_id`, `storagename`, `sap`) THEN `actual_quantity` ELSE 0 END

Are the "ghost" beastmode calcluations saved to the dataset or to separate cards? I've noticed that if I have a beastmode added on only a card and then I use the "save as" option for the card, it will "duplicate" that beastmode with the same name but saved as different calculations on different cards.

Beastmode Manager has a delay. The best fix is to just wait a few hours. I'm not sure what the exact delay is.

Did you verify that row "9" of your data has data for the primary key?

@Byboth - Great idea! This would make life so much easier for admins that have "unruly" card creators

@damen and @MichelleH - A quick note about using the "Save as..." option This will create a duplicate dashboard. However, it will also duplicate every single card on the dashboard to "Copy of CardName". This means that the copied cards are not "mirrors" of the original card. Meaning that if you change the original card,…

@mschallman - I agree with @Ashleigh . I think the best approach here is to use "filter views" to predefine the default view for your users (globally) and then allow them to change if they wish to. You would likely also want to utilize the smart text feature in your card titles so that they properly display CAD or USD…

It looks like you are building a pivot table. You want to make sure that you remove any fields not directly listed in your "rows", "columns", or "values" section from the Sort section of the card analyzer. Make sure that you only sort by fields that are also being shown on the card.

@newbee - You would want to make the field that contains the "Actual / forecast" status your series. Then I would take whatever you currently have as your series and make it a quick filter. However, this will only let you view a single line at a time. That being said, I'm not sure how one is supposed to understand the…

I would add that I think it would be nice if cards built off the same dataset could "share" a legend on a given dashboard. Meaning that, if it is on the same dataset, the dashboard would assign colors to a given series and that color would stay uniform across the dashboard without requiring me to set up color rules. For…

This can be done with "Trellis/Tiered Date Settings" in the chart properties section of a card. First you will need a field that defines the two (or more) categories. In your example, "Actuals" vs "Forecast". This could even be a beastmode: CASE WHEN `DATE_FIELD` < CURDATE() THEN 'Actuals' ELSE 'Forecast' END You would…

I feel like there might be a way to force the dataset ID to match the ID that the WB was using. If you did that and deleted the WB dataset, would that work? Kind of theory crafting here... but I thought the other ETLs, etc. pulled the dataset in by looking at the dataset ID. So, as long as your replacement dataset had the…

@a10hall - you should post this as an idea on the "Ideas Exchange" found here -> Ideas Exchange — Dojo Community (domo.com)

@damen - not a bad idea. Maybe a special section for content creators to link their channels and/or videos. If you are looking for some good content on Domo and how to manipulate data with the tools Domo provides, then you want to check out @jaeW_at_Onyx and his youtube channel: https://www.youtube.com/c/OnyxReporting_2

I'm struggling to understand what you are expecting to calculate. Is the desired calculation (from the screenshot above) to find the value of the change from 4031 to 4039? So for HH AA% you would want to see 1.52-1.92 or "-0.40%"? and for P2+AA% .75-.97 or "-.22%"? In that case, you may want to think about utilizing a flex…

INSTR() will return the location of the first instance of a string

Do you actually have a row of data in your dataset for August? With a null or blank value? Or is the issue that there is no data at all for August?

You can manage this in the Admin section:

AVG(SUM(`headcount`)) FIXED (BY `date`) That will give you the average daily headcount. You would want to put Date field as your x axis and select the "min" aggregation. Then sort the data by WEEK(`date`) Or you could use your "graph by" option to change it to week. I prefer using the MIN of the Date field though because…

@GrantSmith - Thank you! FIXED (FILTER NONE) is exactly what I was looking for. I do think it is odd that FIXED (REMOVE `specific field`) didn't work but FILTER NONE did. Either way, thanks for the suggestion, this is working for me now

The other option would be to group them, but to group them by each field that you want to be able to filter by... so you would get 1 row for each day and each combination of facility, gender, age, etc. This should reduce the row count a bit. In your example of 572, you might end up with 20 rows of data that add up to 572,…

@datamatt I think that I am following this question correctly. I have taken a dataset that looks like this: And converted it so that I get one row of data for each date between the DateAdmitted and DateDischarged for each ClientID. For example, my output dataset (filtered for Client "B") has 5 rows of data. Each row…

@Joe_M The option to control date ranges in multiple places can be very confusing and result in some strange behavior on a dashboard. My general rule of thumb is to try to only control the dates in one place. If your end users are comfortable making those changes at the dashboard level, then I would avoid adding any…

@zcameron I would like to see more training around some of the newer features. For Example, when you release a new chart type, it should come with a training. Not only a training to help users understand how to build the chart, what options are available in the properties, etc... but also a training about why and when this…

Would you need to create groupings based on elapsed time then? Something like, if it's within 5 seconds of the initial time then keep it in the same group? Is it also per ID? What if you had data like this? Would you expect one group for that time frame? or 2?