marcel_luthi Coach

Is doable, but it'll be tricky and depending on the card type used it might not be possible to get exactly what you need. The closer I could think of that would yield a similar result is the grouped lolipop chart or grouped bar chart, using a constant as your X axis. It'd look something like one of the following:

In this case, there are 2 possible paths you can take: If drill down capabilities are needed, then you'll need to transform your data using ETL and create a beast mode that have copies of each persons entries for each tenure year in which they should be counted for. This required a bit more set up but reduces the number of…

You can make your vertical card look more like a histogram by changing the bar width in the properties, that might be more visually pleasant for your use case.

Can you share an image (even if is a mock table in a spreadsheet) of what your ideal outcome would look like? Most likely, based on your description you'll need to use 1 formula per tenure year. If I'm following properly, lets say there have been 100 employees in the company all time and the current count by tenure are:…

@shreeyab if we zoom on only the row you highlighted, if I'm understanding properly, and assuming your Orders number is right (I just find it odd it has decimals), are you expecting to see the following? If this is the case, then you'll need to use the FIXED function, so that each day can look at more than the values for…

There are a couple of things that could be going on, a couple of things I'd suggest you to check first: When you click on the zip on your card, is the zip code added to the list of filters at the top? Is the ZIP code column name present with the exact same name on all the datasets used in the dashboard? Remember that what…

What is the error message you are getting? Can you share mock data with the columns you have and what the calculation would be if you perform it manually? The reason I'm asking is that you have nested aggregation functions (SUM of a SUM) without any window clause (OVER or FIXED) which is odd, so perhaps the formula could…

Agree with @ArborRose, you'll need Beast Modes for each quarter and then compare between them. Just be aware that the QUARTER formula will work for the Gregorian Calendar, if you need to use a fiscal calendar that does not goes from January → December, then you'll need to adjust to account for that.

Any reason why you're using FIXED (add field) ? If you would explain what you're trying to calculate in words that could help but if the idea is to do the total of the Billable Orders divided the total sum of Attempted__txns plus Voucher_txns and calculating this at whatever level your card is displaying using just:…

Good job and looking forward to all you'll be sharing in the future!

@DataMaven glad to see more coaches as part of the community. Looking forward to all the great contributions and creative solutions you all share.

Hi @SamanthaC, it depends on the card you're using. Two things might control how the dates are displayed. If you're using that date field to graph by it, then check the Graph By option and make sure you have it at the granularity you want. If this is just a column on a table or similar, you can control how to format it,…

You can have a column to the far right by selecting to show the Total Row (since this table is transposed, then it'll look as a column). As for having it be the Average, that would depend on how your individual calculations are being performed, sometimes it could be as easy as changing the Aggregation type to be Average,…

This case you might want to try using either a Heat map or Heatmap Table (sorry couldn't locate the official documentation).

Really glad this is now available as a default option in the tile!

If you want to append row you wouldn't do a JOIN but use the APPEND tile instead, just make sure you format your data to include any datapoints you want and any possible combinations by which your users might need to be able to filter on, otherwise, as soon as a filter gets applied to the dataset, your FILLED rows will…

@MichelleH approach seems like the more reliable option, clearly you'll need to tweak it a bit, since if for example your user provides 1013 as the Id to look for, this would match accounts Ids 10, 101 and 13 as well, if you know that the list of IDs will always be separated by spaces, then you could do something like:…

What is the card type you selected, there are several that look the same but behave differently, make sure you' re using line + Stacked Also make sure the option for number of running total bars is set to none: Hope this helps

So how do you identify when something is a "duplicate"? If there is a set criteria then you can do a group by in ETL that does a count on how many times the "uniqueness" criteria shows in the dataset, then JOIN that back into the dataset and filter to leave only those were the count is 1. This if you want to go via the ETL…

Agree with @ST_-Superman-_ , we need to know the part you're currently struggling with. Also on the sample that you shared I see not all members have entries for every month (like Pear that has one for August and then none until December) you'd need to define how that should be handled and what to do when things go from…

Since what you have is a UTC timestamp, you'll need to apply your FIXED function on the date not the exact timestamp, you can do this by Simple wrapping the DATE function around it, like: AVG(COUNT(`description`) FIXED (BY DATE(`EventStampUTC`))) This assumes that all your entries will have a description field, if that…

@ArborRose my suggestion is to create a Beast Mode at the card level as a formula, not as a Tile in ETL since one of your goals was to be able to do this without touching your ETL. While the LISTAGG is not listed is a formula that works and basically just concatenates all entries using a comma by default (hence why I use…

If you want to show the individual entries then you'd need to modify the BeastModes to use a Fixed function: LISTAGG(LISTAGG(DISTINCT CASE WHEN Year = 2022 THEN Store END) FIXED BY(Customer Name)) LISTAGG(LISTAGG(DISTINCT CASE WHEN Year = 2023 THEN Store END) FIXED BY (Customer Name)) If you do this, then you can apply the…

Should be doable if you don't limit your card by Time Range. To not overcomplicate the BeastMode, I'd use 2, one to determine the 2022 stores and one for the 2023 ones. LISTAGG(DISTINCT CASE WHEN Year = 2022 THEN Store END) LISTAGG(DISTINCT CASE WHEN Year = 2023 THEN Store END) Displaying this in a table will yield the…

There are a couple of questions there that will change how things are calculated. You can do this with a beast mode something like: AVG(COUNT(`AlertId`) FIXED (BY `AlertDay`)) This supposing that your dataset has individual entries per alert, but without knowing how your data is structured is a bit hard to provide more…

I just noticed that for the first case you're using SEC_TO_TIME but on all of the others you are not, this is likely why it's not being displayed the right way as that conversion is not happening, try adding that as a wrapper to your ROUND functions.

First your Denominator is not really the same as your Beta formula, the main difference is that in the Beta formula, when LOCID is N you are not doing any sort of aggregation, but you do this on the others. First I'd update the Beta formula to match exactly what you have in the denominator, applying the SUM outside the…

As @MichelleH explained this is the default behavior and often what you want, specially as this will be responsive and dynamic to any level of aggregation you need to have in place. If for some reason you do not want the Total Rollup to be the COUNT DISTINCT for the full data table, then you'll need to change your…

As @Ashleigh mentioned, going with the FIXED function is likely the simplest thing. Something along the lines of: SUM(AVG(`VALUE`) FIXED (BY `Coutry`)) Could do the trick, this tells the system to average at the country level, and SUM for anything after, so if your card you do a group by country it should show you what I…