MarkSnodgrass Coach

You would use the pivot tile in Magic ETL to do this. However, it requires you to manually name the columns and doesn't dynamically name the column based on the data. For example, the Pivot tile converts data in this format... ... to data in this format... ... using this configuration: Here's the KB article about it. This…

Here is your case statement with the DAY parameter added: SELECT DATEDIFF(DAY,"date","published_date") df, CASE When DATEDIFF(DAY,"date","published_date") >0 and DATEDIFF(DAY,"date","published_date") <=29 then '01 Month' when DATEDIFF(DAY,"date","published_date") >29 and DATEDIFF(DAY,"date","published_date") <=59 then '02…

I would check your syntax because I tested it in Redshift and it worked.

I would check to see if any of your column names changed recently. I also wonder if you really want the NULLIF in there or not. Do you want to potentially divide NULL by 12? Or even 0 divided by 12? You may want to re-visit that portion of your logic.

@PJG Glad it worked for you. If you can accept any answers that helped you, that would help others in the community.

You need to add the day parameter as the first part. Like this: DATEDIFF(DAY, "Date", CURRENT_DATE) You could also simplify your case statement if you used the month parameter instead, like this: CASE WHEN DATEDIFF(MONTH, "Date", CURRENT_DATE) <= 12 THEN LPAD(DATEDIFF(MONTH, "Date", CURRENT_DATE),2,'0') + ' Months' ELSE '>…

Here's the KB article about Company dashboard settings that may help you as well.

The Manage Dashboards section only applies to you. To create a dashboard order that applies to all users, you need to order them through the Admin section in Company Settings - Company Dashboard Settings.

Are you using a Domo brick to render this AG Grid? I wonder if you would need to do the replace in the JavaScript section of the brick in order for this to work. It may be that Domo is encapsulating the data returned to avoid certain injection attacks.

Have you tried &#013; as another way to force a line break?

I haven't made it out of the United States very much, so I don't have as exotic photos as some may end up posting. I did just get back from Disney World and Universal Studios and that was a great time. I even spotted a Domo reference while at Epcot! Our "go-to" vacation spot is Cannon Beach in Oregon, which is just about…

The way it is written, you are trying to SUM the string '12 month'. That won't work very well. With these types of case statements that are giving me a problem, I try to break it into smaller chunks and make sure that it is returning a value that I expect, and then paste that statement into the larger one. Try making a…

I think you need to add a space between your metric impression and your utf code. It's viewing the %21&#8681 as one string, when you need the concat to result in %21 &#8681.

You would need to convert the image to actual shapes. This doc may help you do it.

I think you are going to want to pivot your data further in your ETL so that you have one row per date with the following columns: Actual Hours, Budget Hours, Actual Revenue, Budget Revenue, Date. This will allow you to do the math for the ratio very easily.

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.

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:

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.

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.