Comments
-
Unfortunately, color rules require a fixed number and can't be based off of another value. You could use a table card and then use HTML to color the text by creating a beast mode to look at another value, but it is certainly not the same visual as a line+bar chart.
-
@NathanDorsch glad I was able to help. If you can accept any answers that helped you, that will help others in the community.
-
@matty123Kn glad I was able to help. If you can accept any answers that helped you, that will help others in the community.
-
@NathanDorsch with your concatenation: Date(concat( case when Month(`Date`) > 1 then Year(`Date`) when Month(`Date`) = 1 then Year(Date) - 1 end, '1', case when Month(`Date`) > 1 then Month(`Date`) - 1 when Month(`Date`) = 1 then 12 end )) A date of today would return 202213. The date() function is going to have a hard…
-
You can use the DATE_SUB function to subtract different intervals at a time, such as month. DATE_SUB Subtracts date or datetime values (as intervals) to date values in a date column. DATE_SUB('DateCol', interval 1 month) In this example, if the value for DateCol was 2/27/2022, it would subtract 1 month and result in…
-
If you are using the Heatmap Table card under the Tables and Textboxes, you can set the heatmap to be on an individual column basis. Under Chart Properties, go to Scale and select Independent Column Ranges.
-
On the cards where you want to show only data from prior months you could create a beast mode that you would put in your filters. It might look like this: CASE WHEN `dt` < DATE_SUB(CURRENT_DATE(), INTERVAL (DAYOFMONTH(CURRENT_DATE()) - 1) DAY) THEN 'Prior' ELSE 'Current' END Replace dt with your fieldname that has the…
-
Domo calls combo charts Line + Bar charts. In a standard implementation, the value put in the y-axis becomes the line and then the series becomes the bar. You can have multiple lines by entering a value in the General chart properties "series on left scale". It will then use the y-axis and the first item in the series if…
-
Putting something in the series will allow you to drill down more specifically. In your case, it sounds like you would want the hours in there. It will cause a lot of color variation, so it may not result in the look you are going for. Hope this helps.
-
@Canioagain sorry I wasn't clear. You are applying PDP based on values in column, which will hide that entire row. I was suggesting creating a column called "ShowRevenue", for example and it would contain values Yes and No. In your ETL, duplicate the data, but in one set of the duplicate zero out the revenue column and…
-
I would suggest using Magic ETL to clean your data. You can use the Remove Duplicates tile to remove duplicates very easily. Here's the KB article: https://domohelp.domo.com/hc/en-us/articles/360044876614-New-Magic-ETL-Tiles-Filter#4. within a beast mode, you do have options like COUNT(DISTINCT fieldname) that may help…
-
@NathanDorsch in the Limit Rows box, set that to 1.
-
If you go into the analyzer for each card (or slider), click on the date range in the top right. This will tell you which field the card is using for the date and you can change it to what you want the card to use. This may be your issue.
-
You might need to give some examples of your filters, but you can add multiple fields into the quick filters, which may accomplish what you need. Another idea that may help you is to create a beast mode for a date. For example: IFNULL(date1,date2) This would use date2 for the date field if date1 was null. Hope this helps.
-
You might try watching the network traffic in your browser when you go the scheduled reports section and edit the list of users to see what APIs it calls. This site might be of some help as well: https://datacrew.circle.so/c/developerdomocom-community-edition/ It's not free, but you may want to talk to your CSM about Domo…
-
Domo can't plot anything for something that isn't there. It would be nice if there was something you could do in Analyzer, but you will need to go to your ETL and join it to a date table, such as the Domo Dimensions Calendar to create entries for every date. You can then replace nulls with zeros in your ETL for those dates…
-
I believe the solution to this is to append your data. For example if you had two groups, one that could see revenue and one that couldn't, you would just append your data to itself once, and zero out the revenue values in the appended data. You would also have an additional column that would distinguish which is which and…
-
You can use the formula tile and use the replace function like this: REPLACE(fielname,'.0','') This would replace .0 with nothing which would then make it read how you want.
-
There is not something out of the box that would do this. You can easily build a card that would show your inactive users. If you have the Domo Stats dashboard, there is already a card built that shows you inactive users. However, the tricky part is removing them. You would need to build some API calls in order to delete…
-
A basic way to accomplish this in a beast mode is to use sum distinct like this: SUM(DISTINCT `Row Count`) However, this is not a perfect solution if you have names with the same row count. I'm not sure it is doable in a beast mode that is perfect, but you could do this in Magic ETL by doing a group by statement to get the…
-
@Katie_Forrest_2022 glad it helped. If you can mark any answers as accepted that helped you, that will help others in the community. Have a great weekend as well!
-
Are you running the install as administrator by right-clicking and choosing Run As Administrator on the setup file? That would be the most likely cause. Are you able to see the log file that it references? That might provide additional details to help troubleshoot.
-
If you wanted to do it in a beast mode, it is quite a bit more involved, but you could do this: CASE WHEN `Start Date` = `End Date` THEN 0 ELSE DATEDIFF( CASE WHEN DAYOFWEEK(`End Date`) = 7 THEN SUBDATE(`End Date`, INTERVAL 1 DAY) WHEN DAYOFWEEK(`End Date`) = 1 THEN SUBDATE(`End Date`, INTERVAL 2 DAY) ELSE `End Date` END ,…
-
If you are able to do it in Magic ETL, the date operations tile makes it quite easy to do. Magic ETL Connect your Input DatSet tile to a Date Operations tile. Configure the tile as shown here: Note: In Step 4, you will want to make sure to choose your end date first and then your start date as this function subtracts the…
-
That looks correct. Are you looking at the newly named column for your result as it won't affect the original column. A better option might be to use the Formula tile and use the date function to extract the date from your field. It would look like this: DATE(`drentlastchanged`) This will not only produce just the date,…
-
Ahh.... I would say the Domo University materials are out of date. That screenshot you just added is how it used to work, but they changed the look and function a while back. Show Formatting Options replaces Show More Options.
-
Seems like a browser issue or something. I would try a different browser or a different card and see if happens. I found a summary number like yours and I can click Show Formatting Options and it worked. Also, you keep saying "show more options". Are you referring to something different than "show formatting options"?
-
Here's the format I used in my sample dataset and it worked. Keep in mind, the preview window may not be pulling in all of the rows to accurately determine if your filter is working properly. You might need to run the full ETL, depending on the size of your input dataset. DATE(`datereported`) >= DATE('1/1/2022') AND…
-
There wouldn't be any applicable formatting options if you are not wanting to display a summary number which is why you don't see the option when you choose No Summary Number. You need to select Use All Values or Use Current Value and then you could choose how you want those values formatted.
-
I have seen this before. I would take what @GrantSmith is suggesting and wrap the date function around your field as well in the formula. DATE(`TicketCreatedDate`) I think it is a bug in the ETL and have found that wrapping the date function around both works around the bug.