Comments
-
Period over Period charts are a bit limiting in their configuration, but you can remove the line by choosing Symbols Only in the Chart Properties → General → Line Style.
-
It seems as though when the BETWEEN date range is selected, it does act differently. This is what I am used to seeing. I would try using the Previous → Last and choose last 6 years (which should get you back to 2018 that I saw in your between range) and choose the Graph By Quarter and Compare to 1 quarter. You can then use…
-
Have you tried the Variance Bar Line chart in the Period over Period Charts? It shows the variance as a line for you. You can add data labels to make the values easier to see.
-
If your start and end dates are in the same row, then it is pretty straightforward as @ColemenWilson points out. If your start and end dates are in the same column, but different rows, then you will need to use Magic ETL to get it consolidated so that the start and end dates are in the same row and separate columns.
-
Here's a video walkthrough on setting it up. https://youtu.be/hfIUQqeRVkM
-
I would look into the Trellis Categories property on a bar chart. You can create a look like this with the categories, subcategories and attributes.
-
Yes, you can. It all depends on your datasets. If those 3 cards are all built on the same dataset and are just looking at different fields, you can create a beast mode that looks at all 3 fields and sums them up. If those 3 cards are based off of 3 different datasets, you would need to use Magic ETL and append those 3…
-
The subtotal and total row values are based on the aggregation type that is selected for that column. I'm guessing you have the aggregation type of your % Spent column set to Sum. If you change it to average, it will take the average of those values.
-
Ahh… I see what you mean. When I select my beast mode, I am not given the next option to select which values I want like you do with regular fields. I would start by reaching out to support and see if they determine if this is a bug. If they say it isn't then I would suggest adding this ability to the Ideas Exchange.
-
For Period over Period cards, any time you change the date range, you will need to re-select what you want to compare it to. It should give you the ability to do it, but it won't automatically do it for you.
-
I see beast mode columns show up in the columns to filter when creating a segment. When you created the beast mode, did you select "save this beast mode to the dataset"? I didn't think it was required, but it could be. Also, when selecting the columns, make sure you are looking in the correct data type. They are sorted by…
-
Yes, workflows would be the best solution for this and easier to maintain compared to the potential # of cards you might need to create if you went with card alerts.
-
There is a new feature called Workflows that could do this for you. I believe it is still in Beta, so you would need to ask your CSM if you can have access to it. Here is a link to the KB article. https://domo-support.domo.com/s/article/000005108?language=en_US If that isn't possible, you could set up multiple cards that…
-
The partition feature in Workbench should help you accomplish it. Here is a link to the KB article. https://domo-support.domo.com/s/article/360062446514?language=en_US
-
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.…
-
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. https://domo-support.domo.com/s/article/000005149?language=en_US
-
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 
 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⇩ as one string, when you need the concat to result in %21 ⇩.
-
You would need to convert the image to actual shapes. This doc may help you do it. https://inkscape-manuals.readthedocs.io/en/latest/tracing-an-image.html
-
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. https://youtu.be/sLAy-9pu0VM