MarkSnodgrass Coach

I believe you need the Datasets from DomoStats and the Accounts dataset from DomoStats. You can then join the Datasets table to the Accounts table on AccountID.

It doesn't look like the DomoStats or Domo Governance datasets contain this information. I believe the comments option is a newer feature, so they may be available through one of these datasets in the future. I would start with asking your CSM about where that data is stored and see if they can arrange something for you.…

@user17774 Glad that worked for you. If you can accept any answers that helped you, that will help others in the community.

I would suggest adding another group by that aggregates by body part and then join it back to your initial group by. You can then use the formula tile to calculate the percentage. If you are unaware, you can have multiple lines go out from any tile so that you can perform different operations such as this and then join…

I have not heard of the Domo Advanced Builder before. My guess is that it is a premium product that costs money. It may also be deprecated as I don't see it in the Knowledgebase articles anywhere. I would suggest checking with your CSM to determine the status and availability of it. You may have come across this article in…

Have you tried using the first beast mode that I suggested that creates a new group name and then use the use the activity date field in the date range filter? The date range filter has a lot of great options like current month, last 30 days, etc... Seems like this is all you need.

What values does your 'Current_Date' field have in it? Based off your first screenshot, I thought you would be using 'Activity_Date'. Your beast mode would get you MTD since you are looking at the month and the year. If you need all rows with an activity date in the last 30 days, you might try: CASE WHEN…

@GrantSmith back to beating me by milliseconds again. 😁 You may be first, but what about better? Only @Golfoholic can answer that. 😉

You can create a new group name and then use this field in your visualization to do this. Your beast mode would look like this: CASE WHEN Description IN ('0_0-10_Period','0_11-30_Period') THEN '0-30' ELSE Description END You can then just drag in your value field and it will aggregate it based on what aggregation you…

Make sure when you are looking in the preview that you are looking for the new column you just created "Rent Last Changed". Don't look at dRentLastChanged as that will not be altered. Also, if your dRentLastChanged is a datetime or timestamp field, you could use a formula tile and just do this DATE(dRentLastChanged). This…

Unfortunately, that does not appear to be an option right now. You might try using one of the new DDX bricks apps where you will have more control of your table styling. If you search for DDX in the appstore, you will see the different options. You might try the DDX HTML Table app as a first option.

You can enter in the individual e-mail address into the scheduled reports, even if they aren't Domo users. Might not be a fun exercise if your list is a hundred people or so, but that would let the unsubscribe link function properly.

To "restart it", I would delete the schedule and create a new one and see if that works. To avoid future issues like this, I think you will need to create a Domo User Group and have all of the individual people in listed in there rather than using a company Google group. Domo can't tell that the e-mail address that you are…

I believe your issue is that you aren't actually using a date field in your x-axis, you are using an integer (even though it is the year of a date, I'm guessing). Try using the date that is being used in your date range filter as the x-axis and then set your date range filter to graph by year.

For your situation, I would recommend doing this in Magic ETL as it will be a lot easier to manage because you can break things down to into smaller chunks with multiple formulas. For example, I would created a formula called AdjustedStartDate that looks like this: /* check to see if the start hour is too early */ (CASE…

You might need to tweak this a little bit, but this is what I put together for someone else who had a similar question in the Dojo. /* check to see if the start hour is too late */ (CASE WHEN HOUR(`startdate`) >= 17 THEN ((UNIX_TIMESTAMP(`enddate`) - UNIX_TIMESTAMP( /*move it to the next day and start at 9 */…

Try adding a partition by if you want to be the percent of that business name sum(amount) / sum(sum(amount)) over (PARTITION BY `BusinessName`)

@mhouston assuming you have window functions in beast mode enabled in your instance, you should be able to use this to get the percent of total: sum(amount) / sum(sum(amount)) over ()

I just did a search for "svg global map with states" and it took me here https://morioh.com/p/1ed2ddd34690 and I downloaded the big map at the bottom. I have attached it for you. You'll have to look through and see everything is properly labeled. You can edit the svg with Inkscape, which is free, or Adobe Illustrator.

Are you entering the full path in the img src? I just tried it and it worked for me. <p>Hello World</p> <img src="https://www.nlcmutual.com/wp-content/uploads/2021/02/nlc-mutual.svg" width="" height="" alt="NLC Mutual">

That appears to be a limitation of the combo box card type. I would actually submit this as a bug, because it should at least match the width of the component when the text is that long. You can send an e-mail to support@domo.com to let them know of the issue.

If I am understanding you correctly, you could make a percentage beast mode for each type, like this: Easy Client Pct: Easy Clients / Easy Clients + Medium Clients + Hard Clients Medium Client Pct: Medium Clients / Easy Clients + Medium Clients + Hard Clients Hard Client Pct: Hard Clients / Easy Clients + Medium Clients +…

@AeyaiSaengkeo that's great to hear! If you can accept any answers that helped you, that will help others in the community.

Your AND statement is slightly off. You are also missing an END statement inside the count. You have to re-state what you are evaluating, like this: CASE WHEN COUNT(case when `FirstSetupApprovedDate` IS NOT NULL then `CaseID` END) >= -1 AND COUNT(case when `FirstSetupApprovedDate` IS NOT NULL then `CaseID` END) <= 10 then…

Have you tried breaking this down and start with a table card and then create a beast mode for each of the functions and see what they return in the table card and then building it up from there? That should reveal where the error in the calculation is. You might also want to look at a nice write-up @GrantSmith did on a…

I was suggesting re-writing total months on SaaS to this: CASE WHEN `Start Date` = '2050-01-01' THEN 0 ELSE DATEDIFF(DATE(`Payment Processing Month`),DATE(`Start Date`) END However, since you are wanting the total months and not the number of days, you will need to do it slightly different. You can use the Period_Diff…

I believe your error is coming using the date_format inside the datediff. Your format that you are changing it to is not a valid date date format. Is Payment Processing Month not an actual date? I would try wrapping the date function around payment processing month in your 2nd formula as well as start date and see if the…

It's probably not the detail drilled map you are wanting, but if you use the global map again as your drill path card and select auto zoom to data in the general properties, it will zoom to the country that was clicked on. However, it won't have the detail of every state or province of that country. You can look on the…

@keeeirs10 Domo's MySQL is currently on version 5.6, which doesn't support lag. I would suggest using Magic ETL and using the rank & window tile and use the lag function in there. It will run very fast and is easy to put together. Here's the KB article on the rank & window tile if you haven't seen it.…

I have found that to misleading at times. If you move your cursor to the first parentheses after the sum, you should see which closed parentheses it is linked to. Due to order of operations, it is going to try and evaluate your revenue field divided by the sum of your other revenue field. I'm pretty sure that is not what…