MichelleH Coach

@M_Gonzalez The Calendar dataset from the Domo Dimensions Connector contains a list of all possible dates. I suggest joining Table A to the Calendar dataset then filtering to remove duplicate statuses

@Seth Just to make sure I understand what you're trying to accomplish, what are the % change values you're expecting based on the example data you shared?

@Dheeraj_1996 I agree with using the chart types the others have suggested. Here is a KB article with more details on how to structure your data: You may also want to consider the nested bar chart, which will calculate the total without having to restructure your data:

@Trumpetbob Rather than adding a zero, I would follow @GrantSmith's suggestion and wrap each option in a COALESCE function to force null values to zero: COALESCE( -- B2 (SUM(CASE WHEN LeadLevel Name = 'B2' AND Contacted LIKE '%Y%' THEN 1 ELSE 0 END) / SUM(CASE WHEN Contacted LIKE '%Y%' THEN 1 ELSE 0 END)) * (SUM(CASE…

+1 This is absolutely needed

@Pam1324 Since the only difference between the calculations for Month 10 calculation and all other months is the numerator, the grand total will work more cleanly with the case statement inside the first sum like below. Aggregations work best when they are outside of the case statement, rather than inside them. sum(case…

@Trumpetbob I'd recommend modifying the second portion of each calculation to move the lead level criteria to within each case statement since the case statement not wrapped in a sum is likely causing granularity issues. ( -- B2 (SUM(CASE WHEN LeadLevel Name = 'B2' AND Contacted LIKE '%Y%' THEN 1 ELSE 0 END) / SUM(CASE…

@Trumpetbob What do your calculation and result look like when you try to combine all 5 lead types? When you say it doesn't work, is it returning an error or an incorrect result?

@m_malecka I've run into that issue as well and have not found a way around it. I'd suggest contacting Domo Support about the "Hide Subtotals" option not working and posting to the Ideas Exchange to about enhancements to the subtotal functionality.

@hunter_brown Are there any null values in the credits and debits columns? If one of them is null and the other is not then subtracting will return null, so you may need to replace the nulls with zeros in each individual column.

@hunter_brown Do you have the beast mode filter from your original post applied to the card?

@hunter_brown It looks like you can actually simplify this calculation a bit. I've often found that errors can occur when nesting aggregates. Try something like this: ( sum(case when LAST_DAY(`Posted dt.`) = LAST_DAY(CURRENT_DATE() - 60) then `Credit` - `Debit` else 0 end) - sum(case when LAST_DAY(`Posted dt.`) =…

@hunter_brown In your second formula, try changing the NULLIF functions to IFNULL.

@user14170 I don't know of a shortcut for naming the columns off hand. Do the pivoted columns need to be coded into the dataflow or are you able to use a pivot table card? If you have a large amount of charge codes you need to pivot, then having them listed as individual rows may give you more flexibility downstream.

@soozalooz You can use the Domo Governance Cards and Pages dataset to join page views to the cards within a dataflow. Then group by Card ID to to find the maximum of Last View directly on the card or on an associated page.

@SaskiaV Your Regex appears to be correct when testing on regexr.com. I suggest creating a new dataset with the same rules to test whether it will accept the file. If that does not work, you may need to escalate to Domo Support

@SaskiaV Will it work if you remove the second attachment?

@SaskiaV Is there anything else different about the two emails, like sender or file type? Also what error message do you receive in the Dataset History when it fails?

@user01154 I'd suggest reaching out to Domo support about this one.

@damen Here is a KB article about Domo's embedding capabilities with a video:

@Mirnes, @trafalger is correct that pie charts can only display one value at a time. If you want to be able to switch back and forth between values, you can do that using Variables.

@Dheeraj_1996 Can you please share the beast mode you added?

I agree that this is needed! We often have table drills already set up in a desired format, and we don't need users to have to scroll through unnecessary columns in the data grid view if they accidentally click on a value.

@Sumant_Kumar707 According to this KB article, FIXED functions are not supported as filters. I'd suggest adding this as an enhancement request in the Ideas Exchange.

@Ganesh_Naren If your beast mode is an aggregate, the Group by is determined by whatever dimensions are used in your card. For example if you have a beast mode SUM(`Sales`) in the Y-axis of a bar chart the values will group by whatever dimension you have in the X-axis, whether that be Month, Customer, Sales Rep, etc. This…

@kav_100 Have you tried using a Slideshow?

@Dheeraj_1996 I've seen this most often when trying to save a beast mode that Domo cannot process. Do you have a new or changed beast mode on your card?

@deona720 Joins are the ETL equivalent of vlookup, with a few minor differences. You can read more about joins in this Knowledge Base article. In this case I would recommend creating a branch of your dataflow that filters your input dataset on Log Status = Leave so that you have one row per Member ID that includes the…

This would be helpful. The current work around is to create a beast mode that concatenates multiple fields together, but it would be easier to take advantage of native number/date format options in separate tool tips

@domoexpert Try putting the SUMs outside of the case statements like this: (sum(case when Date = '2023-03-01' then `test1` end ) - sum(case when Date='2022-03-01' then `test2` end)) / sum(case when Date='2022-03-01' then `test2` end)