ColemenWilson Coach

The best way to do this is using the activity log. The activity log records almost every action a user makes inside Domo including card and page views. You can count the total occurences of `Action` = 'VIEWED' and Object_Type = 'CARD' or 'PAGE' depending on what exactly you are looking for. Here is an article with more…

Is page performance your only concern? If so, have you tested the performance with all 600 rows? We have pages with table cards with that many rows and performance doesn't seem to be an issue at all. If you really don't want to have the 600 row table card on the page, you could change the interaction of the card at the…

Hi Leon, You would create a new beastmode using the following: CASE WHEN `StatusId` = 60 THEN `TotalPrice` - `EstimatedTax` ELSE `TotalPrice` END Here is a reference for questions around Beast Modes:

This is not currently possible. I would recommend submitting this as an idea in the

You could use a beastmode that is something like this: CASE WHEN `Date field` >= `date` - INTERVAL 365 DAY THEN 'In' ELSE 'Out' END When users adjust the date filter then this beastmode will dynamically show data that is within the last 365 days.

I'd suggest using a beastmode as a filter with 2 conditions: Is an email is false That way, non-email rows that are false will remain. It would look something like this: CASE WHEN `type` = 'email' AND `engagement_bodypreviewistruncated` = 'false' THEN 'out' ELSE 'in' END Then drag the beastmode into the filter section in…

One other approach would be to have a few common, preselected date ranges that will be used and then you can use Magic ETL to produce the groupings based on those date ranges. Users wouldn't be able to select any date range, but they'd at least have some options.

Easiest way I can think of would be to create new calculated fields in a dataflow that flag for the conditions you want to set. This way you can use multiple conditions including "not in" to create a value in the column and then use that field in a PDP policy.

Gotcha! It is not currently. I would suggest submitting this to the

Are you referring to Scheduled Reports? Or dataset updates? Scheduled Reports can be sent daily, weekly or monthly. Standard datasets (connectors) can be updated as often as every 15 minutes. Federated data or dataset views are an exception and the data is updated in real-time. Lastly, you could have duplicate datasets…

You can use: '<strong>' & '</strong>' in your beastmode around the part of the summary number you'd like to be more pronounced. You can also use: '<font size="+3">'

This is what I would use: ROUND(DATEDIFF(CURRENT_DATE(),`INFANT'S DETAILS:\nDate of Birth`)/ 30.437) Note that I've also swapped the order of Infants details and Current date in the DATEDIFF() function to avoid a negative number.

Ahhhhhh okay. So what you'll do is split out the associated IDs column using the split column tile in Magic ETL. Then join the last modified dates to each of the new associated id's columns. Then use the GREATEST() function to find the most recent date across the columns for each row: GREATEST(`Associated ID Date 1`,…

Add a new beastmode to put into your sorting: when DATEDIFF(date,published_date) >0 and DATEDIFF(date,published_date) <=29 then 1 when DATEDIFF(date,published_date) >29 and DATEDIFF(date,published_date) <=59 then 2 etc…

Sure thing! You are on the right track, you just need to partition by ID, as shown below: You'll be left with a ranking by date for each ID. So where there are duplicate ID's, lets say 3 duplicates, you'll have ranks 1,2,3 for the corresponding IDs. Then you can use a filter tile to remove anything that isn't ranked 1 -…

You can use a rank and window tile in Magic ETL to rank the rows partitioned by the ID. Then you can use a filter tile to only keep those ranked 1 (most recent).

@JasonNgaiGPT were you able to get this working?

I've gotten close, but I can't get 100% there. I am using a count of the donation_id field and then this beastmode: (COUNT(DISTINCT donor_id) OVER (PARTITION BY COUNT(donation_id))) I can't seem to figure out why that extra row is there at the bottom of the table: I am guessing it has to do with the fact that there are 4…

You could use FIXED BY function(s) that ignores filters: See "Applying Filter Logic" section, use case #1.

What are you trying to group by? It is not clear in your screenshot example. Is it donation procedure? If so just add that field to the table card next to your 2 beastmode fields.

You would create 2 beastmodes and then bring them into your table card: 1. COUNT(DISTINCT donor_id) 2. COUNT(DISTINCT donation_id)

For me I start with KB articles. If I am still stuck I go to the Domo Community forums. And lastly I go to my CSM and/or AE.

The only way is by deleting the achievement itself, which isn’t possible if it is a system default achievement. I’ve requested this before but it would be good to post in the ideas exchange.

You still need to use the filter tile, not the formula tile. However, within the filter tile there are 2 options for filtering: Formula or Filter rule. The filter tile allows for multiple conditions and even a combination of both formula and filter rules. Remove any other conditions/rules and just leave the: `Marketing…

Filter tiles allow for multiple conditions. Have you removed your other filter rule from the filter tile?

That is odd, you can convert it back using the Alter Columns tile.

Using a formula rule in the filter tile would be: `Marketing Category` != 'Total'

If there is some way to uniquely identify that row, then you can do as you suggested and use the filter tile in Magic ETL. There are two ways to filter rows using the tile, with a formula rule or with a filter rule. Here is a knowledge base article that walks you through how to use it: If you still can't get it, please…

Hi Jason, Apologies on the delayed response - I have been out of office. I would be happy to jump on a quick call with you to troubleshoot why this isn't working for you. If you'd like to, you can schedule a time here:

Yep, so basically you would join your data 1=1 so that it looks like this: Then in your card you have your two values: `data` and `comparison data` Users select a year and a comparison year and the data for each will be displayed. I would suggest setting default values for each, for example: 2022 vs 2023 and then from…