MichelleH Coach

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

@neilprobst Do you have an aggregation set on the Spend filter in analyzer?

@LeonN Can you please share some more information about the data you already have in Domo? The solution will be different depending on how inventory is measured in your data

@renee12345 Yes, you can use the "Card Fields with Beast Modes" report from the Domo Governance connector. It will tell you which fields are used on each card.

@cmarino The reason it's sorting like that is because the beast mode is being sorted as text and not a number. You could either add a leading 0 to your labels (i.e. 01 Month, 02 Month, etc.) or create a second beast mode with a formula of DATEDIFF(date,published_date) to use as your sort field.

@ColinHaze You can accomplish this using case statements inside your sums. The LAST_DAY function can be used to transform dates to the last day of the month so you can compare months. Current Month CPL sum(case when LAST_DAY(`Date`) = LAST_DAY(CURRENT_DATE()) then `carrier pay` else 0 end) / sum(case when LAST_DAY(`Date`)…

@hunter_brown Unless you want to set up a variable, you will have to select Between December 1, 2021 and December 31, 2022 in the date filters. The rolling date ranges only work relative to the current date.

@hunter_brown You can filter to the last 13 months by selecting Choose Date > Previous > Last and it will give you the option to choose a rolling date range.

@Anna_Yu Try this instead: Y-Axis: Category X-Axis: Year 1 (Beast Mode) Series: Year 2 (Beast Mode)

@Anna_Yu Is the `current_year` field actively used in your chart? Color rules only apply to fields that are also displayed in the chart.

@Anna_Yu You can leave the "is always" condition and the color will apply regardless of the value

@Anna_Yu You will also need to create beast modes for each year selected, like the ones in my original post. Those beast modes are what the color rules will be based off of, so if you named them differently that is what you will need to look for in the drop-downs

@Anna_Yu Do you always want the values to be red and black? If so, you can create two color rules so Year 1 is always red and Year 2 is always black. Here is a KB article on how to set up color rules:

@JasonNgaiGPT The MAX around your beast mode is only returning the option that is last in the alphabet, in this case "Out". Try removing the max to see if that gives you the "In" option.

@Anna_Yu This sounds like a good use case for Variables. I'd suggest creating two variables to select the years you want to compare. Here are some sample beast modes you could use with these variables: Year 1 Total: sum(case when YEAR(`Date`) = `Year 1` then `Amount` else 0 end) Year 2 Total: sum(case when YEAR(`Date`) =…

@ScottLeeds Is there actually a column called id in your dataset? If not, you can change those portions of the beast mode to a different field, as long as it does not contain nulls.