MarkSnodgrass Coach

Another option is to make it look like the line changes color when it goes past the current date by creating two lines. I have outlined how to do it in this video. You can ignore the part about rolling averages and just focus on how I develop two lines. https://youtu.be/sLAy-9pu0VM

If you have data for every day of the year, you could utilize the data label settings and the tooltip to make a label appear on the current date. First, create a beast mode that looks like this: CASE WHEN datefield = CURRENT_DATE() THEN datefield END Drag this beast mode into the Tooltip Field 1. In the Chart Properties,…

You will want to change your join since you are comparing it to the same data set. Here is how I typically do it to get a row for every combination. Use the add constants tile to create a column called JoinKey and set it to a value of 1. Do that twice. Connect them to the join tile and join on the JoinKey with an inner…

Here is a video walkthrough of how to do it: https://youtu.be/xzi-fhEmN-Y

Doing those types of calculations in a pivot table are tricky. I would try to get it working in a regular table by breaking out the individual components of this beast mode and verifying that you are getting what you expect on each row.

Try editing your beast mode to look like this: SUM(IFNULL(case when SourceCode = 'AP' then TransactionAmt end,0)) / SUM(IFNULL(ProjTotalCostEOJ 1,0))

Sorry, I should have been more clear. I was referring to your card configuration in Analyzer. In Analyzer, do you have any of those fields in your card set to Sum? Or is the aggregation set to None. In Analyzer, if you have fields set to aggregate, you need to make sure your beast modes are doing the same thing.

In your table, did you select an aggregation of sum for the Projected Cost and JTD columns? If so, you would need to incorporate SUM into your beast modes, you would need to do it outside each of your IFNULL statements.

Was this connector working previously and it is now producing this error? It could be bad data, or just a temporary glitch. I would try creating a new connection and see if the same error occurs. If it does, and it doesn't clear itself up in a few hours, I would suggest opening up a support ticket with Domo and they will…

I would click on Edit Dashboard and then on each card, click Edit Content and click on Change Filter Exceptions. Ensure that the Allow global date option is selected.

Here is a video that walks you through how to use deep link filtering (or pfilters) that might help you. https://youtu.be/zrNDxinOti0

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: https://youtu.be/9iNpzSL5V6U

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. https://youtu.be/mDwSQGAjIrs

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