MichelleH Coach

@Laura_M1 What you are describing should work regardless of whether you are using charts or tables. When you try to drill on that particular card, does it show you a particular message or does it simply not react at all?

@Laura_M1 It sounds like a granularity issue. Is your measure a dataset field or beast mode? Also, if you have any sort fields being used in your card I suggest removing those

@Laura_M1 Is the second level detail you're trying to see defined as a drill layer in Analyzer or the default "Data" view? If it's the latter, then drilling to it is only an option on from the card details view and not from the dashboard. In that case I suggest adding a Table chart drill layer so that it is visible when…

@user10570 Are you using beast mode or MagicETL to rank? Can you share the details?

@kenyayvette Yes, the Accounts section of the Data Center it will show how many datasets are associated with that account. If you hover over "DataSets" on the right side and click "Change Owner" you should see a new dialogue to either transfer the datasets to a new owner or new account.

@kenyayvette Do the users have the same database access? If so, is the user with the working account able to share the Domo account with the other?

@jroach The Dataset via Email connector includes a column for the input filename, so it may be worth trying that

@jtrollinger Is SourceCode = CO in the rows in question? It likely has to do with your last IFNULL forcing the output to zero

This would be nice to have to make tables a bit cleaner

@dmurgit1 Depending on your use case, you may be able to use two variable controls and a beast mode filter to accomplish this. You would have to set the values of each variable for all possible values of the corresponding field, so this would only be feasible if your fields have a fairly small and static list of values.…

@RayRay_H It looks like there may be a space after the date in the error message. Try replacing the spaces with an empty string before using the STR_TO_DATE function STR_TO_DATE(REPLACE(`Date`,' ',''),'%d-%b-%y')

@BigWave If you are using a Line Bar chart you can set a min and max value for the lines under Value Scale (Line). Since this chart type only sets the first series as a line, you can specify two lines using Series on Left Scale under General Properties

@jrudd Unfortunately, color rules only apply to fields that are actively used in the card. As a work-around, I suggest changing your card to an Overlay Bar chart and creating a separate beast mode measure for each Scoped Hours Progress value. Then you can create an "is always" color rule for each beast mode.

@ChrisGaffan How are you presenting this field in your card? Sometimes sorting can interfere with how the cards react

@ChrisGaffan How much bigger? Is it correct if you remove DISTINCT?

@user058901 It's likely inflating the value because it's adding 1344 to every row. Try using AVG(1344) so it does not get duplicated

@ljb18 Since you're trying to determine whether the value of the Library column exists within the Track Split column, you could also try using the INSTR function to return the position of the Library value. If there is a match then the position will be greater than 0. case when INSTR(`Track Split`,`Library`) > 0 then 'AZ'…

@donna_torrice I would suggest the Line + Grouped Bar chart type. By default cards only include one series as the line, but you can change that under Chart Properties > General > Series on Left Scale.

@TraceyRosado You can also use the Card Fields with Beast Modes report from the Domo Governance Connector to see which fields (measures) are being used in each card. Then you can join this to the Activity log as @colemenwilson suggestions to understand usage at the metric level

@Milton_Hernandez1977 Can you please share what you've tried so far?

@carthur Yes, you can use as many conditions (including variable selections) as you need into that case statement by using additional WHEN… THEN clauses

@carthur You don't actually need a GROUP BY clause in beast mode the same way that you would in SQL because your beast mode should group by whatever dimension is used in your card. If I'm interpreting your examples correctly, you are trying to sum the amount column for all locations and multiply the amount for ATL by 10.…

@carthur You don't actually need a GROUP BY clause in beast mode the same way that you would in SQL because your beast mode should group by whatever dimension is used in your card. If I'm interpreting your examples correctly, you are trying to sum the amount column for all locations and multiply the amount for ATL by 10.…

@BigWave Based on the data you provided, you should be able to use the beast modes below to without any additional manipulation: % Female sum(case when `Split answer` = 'Female' then `Value` else 0 end) / sum(`Value`) % Male sum(case when `Split answer` = 'Male' then `Value` else 0 end) / sum(`Value`) If you just want the…

@NathanDorsch You can have more control over projections by adding a second Beast Mode series to your bar chart instead of using the Last Value Projection in Analyzer. In your case, the formula should look something like this: sum(case when LAST_DAY(`Date`) = LAST_DAY(CURRENT_DATE()) then `Value` *…

@AshleySizemore Are both of your columns stored as date fields? If they aren't, then you will have to convert them to date. Otherwise I'd suggest closing out of Analyzer and trying again.

@LeonN The %d specifier in the DATE_FORMAT function is expecting a leading zero in the day, so it is expecting 'Jan 01, 23' instead of 'Jan 1, 23'. You may need to manipulate the field to include a leading zero before the day before using the DATE_FORMAT function. Alternatively you could try using the FUZZY_PARSE_DATE…

@LeonN What do the dates in your data look like?

@vibhusharma2210 How specifically are you running the report? Are you creating a card, running a dataflow, or something else?

@louiswatson You can use the STR_TO_DATE() function to convert those values to date like this: STR_TO_DATE(`DateField`,'%d/%b/%Y') The second argument of the function uses these date format specifiers to specify what format the existing field uses.