MarkSnodgrass Coach

I would look at use case #3 in this article as a way to solve your problem https://domo-support.domo.com/s/article/4408174643607?language=en_US

This video should walk you through how to do this:

You might need to provide more detail, but if you are wondering if you can do this, the answer is yes. The syntax would look like this: CASE WHEN fieldname NOT IN ('Georgia','Alabama','Texas') THEN 'exclude' ELSE 'include' END

I would check to see what you have in your sorting properties. This can throw off how Domo groups your data which will affect the MAX.

Your syntax needs to be like this: CASE WHEN column A = 'xyz' THEN 'abc' ELSE column B END When referencing the columns in your dataset, make use of the autocomplete when starting to type out your column so that you know it is being referenced properly. When comparing it to a string, put single quotes around the string.…

It also seems like you have some slashes before and after your date. I would try adding a REPLACE function to remove those and then convert to date. REPLACE(fieldname,'/','')

In addition to @GrantSmith 's suggestion of moving the SUM to the outside, you can simplify your current year evaluation by doing something like this: YEAR(invoicedate) = YEAR(CURRENT_DATE()) AND invoicedate < = CURRENT_DATE() For the previous year you can again just use the YEAR function like this: YEAR(invoicedate) =…

Hi @BigWave , Saw your comment on my YouTube video. Glad you are finding them helpful. You can do what you want by creating two beast modes. One for the Male % and one for the Female %. They would look like this: Male % SUM(Male) / (SUM(Male) + SUM(Female)) Female % SUM(Female) / (SUM(Male) + SUM(Female)) You would then…

You need to move your closed span tag to be after your numbers. Should look like this: CONCAT('<span style="color: ##004387; font-size: 32px; font-weight: bold;">$', ROUND(SUM(Cost) / SUM(Leads), 0), '</span>')

You might try just comparing the months and not the month and year because the line is showing last year which would be less than zero in this case. Also, I find the period over period charts to be particularly difficult to work with. That could also be the issue.

That sounds like a potential bug that you would need to notify support about. You might try leveraging more of the tooltips and other fields available in the hover text macros so that you don't need to build a beast mode with line breaks. You can mix and match text and macros in the hover text and just hit enter to put…

I do have a video about incomplete months as well if you want to watch it, but the short answer is to change your date range filter to 13 months and then create a beast mode that checks to see if the data is in the current month and exclude it, otherwise include it. Drag that into your filters and filter to include. Here…

@NathanDorsch this video may help you where I show how to move dates from different years into the current year so that you can do a year over year comparison.

In the date range filter, change your Graph By to Day instead of Year.

yes. you can do this a couple different ways. Option 1: You can drag the quantity into your filters and filter to less than a number you think would exclude outliers. Option 2: You could add a case statement to your beast mode that only will do the math if the quantity is less than a certain amount. i.e. CASE WHEN qty <…

You can create a beast mode that multiplies cost * qty and then put this in the y-axis of your card and choose sum. Put your date in x-axis and choose last 5 days in your date range filter.

Yes, a Domo Webform is a common way to do this. If you tie the form responses to an ETL, then you will see the results once the ETL has run. You can also use the ETL to join it to other data to incorporate into your visualization if needed. Form Builder is another option, but that is a premium feature.

I think the solution is to build a card that would meet that criteria and then set an alert when the summary number is greater than 1. For example, if you set your date range filter to last 2 weeks and then add a filter that is a count of your isLate column that is greater than or equal to 10 than your employee should show…

You can use the pivot tile to pivot your engagement type values into individual columns. This KB article will be helpful for you. https://domo-support.domo.com/s/article/360044951294?language=en_US

@M_Gonzalez I apologize. After thinking about your situation more, I realized my last suggestion would not get you what you want. I did come up with a way to do it, though, and have created a video to walk you (and anyone else) through how to do it.

I use the Dataset Copy Connector to copy the DomoStats datasets from my "child" instances to my "main" instance and then append them together in an ETL in my main instance. That might be a solution for you in the meantime.

@M_Gonzalez glad you are enjoying my videos. I think my "Filling in Date Gaps in Domo" would walk you through some of this. As far the the IFNULL, starting with your rank & window, the name you are assigning for your lag value is what you would be using in your IFNULL along with your main status column. With rank & window…

Here's a rough outline of how you would construct your ETL to do what you want. Bring in the calendar dataset. I suggest filtering it a bit as it has about 30 years of dates in it. You can use a formula in your filter rule to make it dynamic and not hard-code dates in there. Get a distinct list of products. I used the…

You might want to look into the faceted bar chart. https://domo-support.domo.com/s/article/7508982399767?language=en_US

You could create a beast mode that creates an include/exclude output and then drag this beast mode into your filters and filter to include. CASE WHEN DAYNAME(CURRENT_DATE()) = 'daycolumn' THEN 'Include' ELSE 'Exclude' END

Are you using ds_update? That allows you to update an existing dataset. Data sets - This set of functions is designed to transfer data in and out of Domo. ds_get - downloads data from Domo ds_create - creates a new data set ds_update - updates an existing data set, only data sets created by the API can be updated ds_meta -…

Here's a re-worked case statement: CASE WHEN Date of Death is NULL THEN FLOOR(DATEDIFF(CURRENT_DATE(), Date of Birth)/365) WHEN FLOOR(DATEDIFF(Date of Death, Date of Birth)/365) < 1 THEN '<1' WHEN FLOOR(DATEDIFF(Date of Death, Date of Birth)/365) < 3 THEN '1-3' WHEN FLOOR(DATEDIFF(Date of Death, Date of Birth)/365) < 6…

Yes, you can't create a "variable" in a beast mode and try and reference it later in your beast mode. Domo is working on functionality to allow you to nest beast modes, so you could create a beast mode called age and then in your age range beast mode you could reference the age beast mode. Your workaround right now would…

Agree with @trafalger . Here is a video on how to do it:

Have you tried the pivot table card? That would allow you re-orient your columns.