marcel_luthi Coach

DISCLAIMER Please be aware that Bulk Deleting is dangerous and if not done with utmost care, might end up having unexpected behaviors, specially as the same card might be placed in multiple dashboards and deleting it will cause it to be deleted from all of them. With that being said, you can go to the Admin Section and use…

I just got time to try things out a bit, and while at the DATA TABLE level the calculation seems to be working as expected, returning only 5 rows, the visualization is creating additional rows not in the Data Table, might be worth bringing this up to Domo Support.

So it works so that every entry on each period shows the same value, which the previous approach wouldn't do, but it's still generating one entry per row even if the values are the same. I recall seeing a similar behavior on another question no long ago, but think no solution for that was provided 😓. I might play with…

That is correct @calvert_schaefer, so instead of using the Date field in your graph axis, you'll use a beast mode instead, and then in your rolling calculation in the OVER clause you'll use the same or a slight variation of the beast mode instead. Something along the lines of: CASE WHEN `granularity` = 'day' THEN `Review…

The problem is with the granularity, sadly the Beast Mode function will work with the data the way that comes from the Dataset, in this case daily granularity and will return a different calculation per day. Since these values are different, even when you ask to graph by week you'll get an entry for each day of that week.…

Perhaps not the best way, but to your ETL that builds that DataSet, I'd add a calculated column that tells you the difference between the 2 values and another one that would just flag if the date is older than your threshold (in this case 7 days). You'll have a formula tile in your ETL that will do both calculations,…

You can do that with SQL as suggested or with Magic ETL (somehow I always end up visiting @MarkSnodgrass video on how to build a Word Cloud whenever it comes to a request like this), the logic would remain the same, you just change what the delimiter is that you're splitting by (and might want to add a trim after splitting…

Sadly (or at least AFAIK), while the icon for the Slider control icon depicts two dots, which would make you think you can select a range with it, this is not currently the case and you need to create a different variable for the lower and higher end of the range individually. Perhaps something worth sharing in Ideas…

While this solves the particular case keep in mind that this solution is not easy to scale. I'd recommend using a Webform datasource to track Team changes with start and End Date, and then do some ETL to determine the team that person should be in for each entry based on it. Is more work, but that would allow you to have…

You should be able to use %e instead of %d for the day part to account for the day not being provided in the 2 digits format, and remember to use STR_TO_DATE and not the DATE_FORMAT function, as what you have is a string you want to turn into a date and not displaying a date in a specific string format. I just tested my…

Based on the error in red, it seems your date string includes a comma after the day number and this one is using a single digit version when below day 10, this could be the reason it fails. Try updating your date format to: STR_TO_DATE(`Year Day Month (text)`,'%b %e, %y')

I would guess you're creating a beast mode that then is being used as a Tooltip to be displayed as the hover text, is this the case? If so, make sure you're entering line breaks as HTML so your beast mode would look like: CONCAT('Total: ',SUM(`value`),'<br>','Count: ',COUNT(`Id`)) This is just an example since we don't…

You should be able to achieve this by using a Variable (most likely 2) to enter the range start and end, and then building a BeastMode which you'll use for filtering. If your Variables are called RangeStart and RangeEnd, then your BeastMode would look something like: CASE WHEN SUM(`Spend`) >= `RangeStart` AND SUM(`Spend`)…

Another approach would be to use the PERIOD_DIFF function, something like: period_diff(date_format(CURRENT_DATE(), '%Y%m'),date_format(`INFANT'S DETAILS:\nDate of Birth`, '%Y%m')) I'd advise you to try both, put them side by side and then compare a few examples to what your expected number would be, so you can get the one…

To provide more clarity on my answer, your flow will end up looking something like: Which after running provides the following output: The modifications to the original one is on the number of days we take from the calendar, so we no longer limit it to a calendar year but to a set number of days, this happens in the filter…

I would need to test this out, but ideally, you could solve this with a variation on @MarkSnodgrass word cloud example (YouTube link), and after exploding to have one row per each associated ID, plus one row for the unassociated version, where you'll Join the data from the associated IDs (only the field you care for), then…

Congrats!!! A well deserved title and glad to see more coaches as the community grows 🤩

Sadly the documentation about this feature seems to be outdated and does not include information on this option. Based on your screenshots my best assumption is that it looks at which periods have data up to the end of the period and then selecting this box or not determines whether to any actual for the current period…

It depends on what I'm looking for, if it's generic information I'd go to the KB articles first, but when it comes to specific scenarios, I'll lurk the forums for similar questions or YouTube if I recall seeing a video somewhere on the topic by one of the many amazing contributors here in the forum (their channels are an…

Filtering pivot tables is often tricky, specially if you're expecting the data displayed to be responsive to filters on the page or dashboard level, and even more if you want to limit to a specific top "X". If a less restrictive approach is acceptable, you can build a BeastMode that tells you the actual total for each row…

As Michelle says, I used Id since it's a column present on most of my tables that I know will never be null, so you can either replace that with a column name that is always provided or if you don't have one, you can update to use the literal number 1 instead of a column name, it'll yield the same result (supposing your…

Agree with @MarkSnodgrass, pivoting the data is the way to go, and doing it via ETL when you foresee this being needed for other calculations is preferable. If this is only used for this you can go with Beast Modes, so your Score formula would become something like: 0.5*COUNT(CASE WHEN `engagement_type` = 'OUTGOING_EMAIL'…

Congratulations everyone! Thanks for making this an awesome community.

Great idea, this would certainly allow us to reuse cards more rather than having to create copies just because on X dashboard the legend makes more sense to be displayed in a different position.

I guess it all depends on your specific needs, if showing the average lines is optional, you could go with the default Period Over Period Running Total chart, selecting Month To Date and comparing against 1 Year ago, which would give you something really similar to the image you shared, and has the flexibility that you…

Agree with @trafalger , also keep in mind that whether this will display as an hyperlink or not will depend on the kind of card you're using. One quick thing I would recommend, just to keep things following HTML standards, is that if the idea is to show the name as the text displayed for the link, to put that in between…

The thing there is that you have 2 rows, Level and Spend, and I'd guess each level is tied to only a single Spend based from your screenshot, if that is not always the case then you want to keep it the way it is, as the numbers will not always be "duplicated". As a workaround, you could display only one or a single one…

While having the feature would be awesome, a workaround is to add a JoinKey on both tables (constant), join on that key (basically doing a Cartesian product for the tables) and then apply filters that would replicate what you'd have specified in the regular ON clause of a SQL JOIN, you can Drop the Join Key as part of the…

While it sounds simple, this question does have additional complexity to it, specially since you're trying to contemplate that if an EditHistory entry with date prior to the PeriodEndDate does not exists you'll take the old value of the first EditHistory entry after the PeriodEndDate, this might be achievable via ETL using…

@Juliann_Potter if you already have an ETL that returns you the rank of each user each week like this: then you can achieve what you want with a pivot table, but instead of using one of the predefined aggregations, you'll need to create a beast mode and use that as your value, something like MAX(`Person`) would do the…