MichelleH Coach

@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)

@chetan_cricut The error is likely because of the COUNT(DISTINCT ) in your order by clause. I've often seen beast mode errors when using aggregates inside of other aggregate/window functions. Are you able to hard-code that count using ETL?

@gbrown I would suggest changing the format of the other dataset using the Dynamic Unpivot tile in MagicETL instead, if possible. You will have significantly more flexibility with the dataset when it is not already pivoted.

@gbrown You should be able to use your existing data as-is in a table card, and select the Transpose Columns option to put it in the desired format.

@hunter_brown To answer your question, what you are describing should work in beast mode. What are you getting instead?

@hunter_brown Is this data time-bound? If so, could you not link your datasets by month?

@hunter_brown Be sure to use ` around your column names instead of an apostrophe so that it knows you are referencing a column. They way you have it now, Domo thinks you are trying to perform a mathematical operation on strings

@zaclingen_zips This sounds like a mis-alignment with your instance time zone from your company settings. Does the dataflow produce any different results if you set the time zone in the Dataflow Transform settings instead? Here is a Knowledge base article about troubleshooting time zones in Domo:

@mroker This sounds like a timezone mismatch between your Domo instance and the source data. You will likely have to add a Timezone conversion transformation to your workbench job to match the timezone of your Domo instance.

@Pau I don't think a free-standing legend is an option, but I would suggest setting the same color rules on all 3 cards and hiding the legend on all but one of them so it doesn't have to repeat.

@jtrollinger What type of aggregation/subtotal are you using on that column in the card? It looks like it might be set to MAX instead of SUM. As @colemenwilson mentioned, I don't see anything obvious in your Group by tile that would cause it to display that way.

As others have mentioned, I definitely agree with going back to in person and showcasing the "How". It would also be helpful to have a session on how to solve the most frequently asked problems that users ask about in the Community Forum.

@ArborRose Instead of Value Mapper you could just put that exact case statement into a Formula tile to give you more flexibility.

This is great, thanks for sharing @AnnaYardley!

DONE