Comments
-
I think it is because of the SUM(SUM part. If you remove the extra SUM does it work? You could try: SUM(CASE WHEN `fieldsMonth Ending Date` > CURRENT_DATE() - INTERVAL 12 MONTH THEN `fieldsAccident Count` ELSE 0 END)
-
Hmm odd. 0/0 should return a null value not what you are seeing. Is there a reason you don't use the same logic from the WOW % as you do in the spend LW and spend 2LW columns? For example for Spend LW why don't you use: SUM(CASE WHEN Fiscal Week Index = Current Week Index - 1 THEN Amount_Cost END) I'm thinking perhaps the…
-
Can you try copying and pasting my beastmode into your card and seeing if that works?
-
Hi Anna, It still looks like the minus sign is missing. Along with extra parentheses.
-
It looks like you are missing a minus sign in your beastmode. Additionally, change % calculation is: (New Value - Initial Value) / Initial Value. So I would write your WOW spend calculation as follows: (SUM(CASE WHEN Fiscal Week Index = Current Week Index - 1 THEN Amount_Cost END) - (SUM(CASE WHEN Fiscal Week Index =…
-
Inline Editor is a premium Domo feature that may be of interest to you. https://domo-support.domo.com/s/article/360042933754?language=en_US
-
Annotations are not currently supported. Your best options are to take a screenshot and annotate elsewhere or to export as a powerpoint and annotate there.
-
It may also be helpful to switch to the Table View on the table card as shown below (orange arrow):
-
As bryce mentioned variables are a great way to do this if you want the axis values to change based on a filter. You could, however just group data together with a beastmode and then allow users to switch between that grouping as long as the aggregation remains constant (Sum, average, max, etc…) which it sounds like it is:…
-
One way you could do it is the beastmode below: SUM(CASE WHEN `YEAR` = YEAR(CURRENT_DATE()) THEN `Sessions` ELSE 0 END) - SUM(CASE WHEN `YEAR` = YEAR(CURRENT_DATE()) - INTERVAL 1 YEAR THEN `Sessions` ELSE 0 END) If this doesn't work let me know!
-
CASE WHEN FRANCHISEE NAME IN('Adam','Al','Leon','Brandon','Colemen') THEN 'Include' ELSE 'Exclude' END Then use it as a filter and select 'Include'. Also select "Share on Dataset" on the quick filter.
-
Have you checked the formatting (number, date, text) in that column in your excel source file? Has it changed? Are you seeing errors in your source file such as: #N/A, #DIV/0!, #NAME?, #NULL!, #NUM!, #REF!, #VALUE!, Etc…
-
Hi Dustin, You could use the split columns tile in magic etl and use the REGEX option with (?<=.{4}).+ as shown in the screenshots below, just change the 4 to be whatever number of characters you want to split on:
-
Grants solution for the second date is correct: YEAR(`ProductSale_Timestamp`) Is that still not working for you? For the first part try this: YEAR(FROM_UNIXTIME(`PRODUCT_KEY`))
-
Both great ideas! I ended up modifying Grant's code (using chatGPT) and using an email that creates a ticket in our ticketing system. That way for an end user it is 2 clicks: click the link in the table card and click send in the email client.
-
The closest thing I could find was in notifications settings. At the bottom where it says "Product Updates and Education" click "Manage". I am pretty sure this is just for email notifications. I would reach out to you CSM for further help.
-
There is a Domo Stats dataset called "Card Permissions". It has who the card has been shared with as 'entityId' You'd have to create a dataflow to join the People Domostats dataset to uncover who those people are. Additionally, if the card is shared with a group, the Group ID will be shown instead of each individual userId…
-
Agreed this is needed.
-
I think you could accomplish this using an HTML table DDX brick. Search "HTML Table Brick" in the Domo appstore.
-
Just commenting to boost this idea. This is a great idea and would be very helpful.
-
Interested in this as well
