MichelleH Coach

@Laf8991 The CONCAT function turns your summary number into text field, but alerts can only run off of number fields. What if you use a scheduled report instead of an alert?

@ssheffer77 Can you share the beast mode that you tried?

You may be running into issues because of aggregation within a case statement. You can also try the formula below to bypass the case statement. avg(AVG(ifnull(`Chat Duration`,`Call Duration`)) FIXED (BY ifnull(`Chat ID`,`Call ID`)))

@TimLudwigsen The approach generally depends on what fields are in your data and how you want to display it. If you are using a Period Over Period chart, then you need to have a date field in the x-axis in order to set up a comparison to prior year and dynamically change the date groupings. You will also have to select a…

@Laura_M1 Shared beast modes are immediately available once the card has been saved (not just clicking "Save Calculated Field"). Try re-saving the card if you don't see it. Also, shared beast modes are not available in cards using different datasets.

@lawiti Domo does not summarize the changes from each version, but it does save each version so you can revert back to a previous one whenever you need.

@A_Benincasa The formula should work if you remove THEN `Actual Goal` from each line. In case statements WHEN identifies which rows to consider and THEN specifies what value to assign to those rows, so the formula will not work if there are multiple THENs for each WHEN.

@lawiti The version description comes from what the users enter each time the dataflow is saved. You would need to add the description yourself for it to appear in the versions list

@shreeyab Have you checked that there are no typos in the user's email address on their Domo account? If that's correct, then it is likely an issue with their email settings. You may need to have notifications@domo.com added to their safe senders list and make sure the emails are not being caught in an inbox rule

@Yadhuveer Have you verified the interaction settings on both cards, or just one? Otherwise, are both filters powered by the same dataset? If they are using different datasets and the dataset powering Filter1 does not have the same field with 1,2,3… values then Filter1 will not interact.

@Stucker This looks like a datatype error. If I'm interpreting this correctly, you have a time field (`AVG Answer`) that you are trying to convert into a number of seconds/milliseconds. You are on the right track with the TIME_TO_SEC portion of the formula, but the problem is with the second part where you are looking for…

@genchevd That's correct, it would break the card. If you want to change the field name, I would recommend first duplicating the original column in MagicETL with the new name. Once the new field is added, change all cards using that field to the new one (the Card Fields & Beast Modes report from the Domo Governance…

@froghunter If I understand correctly, you want the drill to be filtered by both Group and Status. Mega table cards are set up to only filter the drill based on the value that the user clicks (i.e. if you click on the word "Open", it will include all rows where Status = 'Open'), but if you switch to a Pivot Table card it…

@lawiti Be sure to remove `Hires` from the Y-axis and `Segment` from the series. Line charts are set up to expect either one measure in the Y-Axis and one dimension in the Series OR multiple measures (one in the Y-axis and the others in Series). If you still have your segment in the series spot, it will not allow you to…

@Yadhuveer Can you share an example of how the interaction is behaving vs how you want it to behave?

@lawiti You will need to make a separate beast mode for each segment, otherwise it will function the same as using just the `Hires` field. The reason you need individual beast modes is so that the formula evaluates every single row of data and return a result of 0 if the segment does not match the one you want, which then…

@lawiti If you are using a dimension field in the series, then your lines will be null instead of zero whenever there are no rows that meet that criteria. Instead of using Hires in the Y axis and a dimension in the series, try using a beast mode for each line like this: sum(case when `Segment` = 'X' then `Hires` else 0 end)

@Ankur If you are joining on Country List and still getting more output rows than expected, then the Country List field is not unique. You will need to remove duplicates by the Country List field.

@carthur On your second formula, you are getting an error because the logic needs to be within a case statement. I'd suggest doing this instead: case when YEAR(`ORDER_DATE`) = YEAR(DATE_SUB(CURDATE(),interval 1 year)) and ORDER_DATE <= DATE_SUB(CURDATE(),interval 1 year) then 'Include' else 'Exclude' end

@Ankur You will want to do a left join in MagicETL with Employee Headcount as your left table so that you keep all employee headcount rows but not all country mapping rows. If your output still returns more rows than what exist in the Employee headcount, then there are likely duplicates in your country mapping table. You…

@nmizzell You can enable a secondary y-axis for the cart under Value Scale (Right) > Show Right Scale. Then you can use the Lines on Left Scale to specify which series will appear on which scale

@Dheeraj_1996 If you only want to keep positive variances across multiple rows, then you'll need to restructure your data to include a column to include the previous days' records value. You can do this by using the LAG function in the MagicETL Rank & Window tile. Once you have added this column you can use a single…

@Dheeraj_1996 I see. Based on the example in your original post it sounded like you wanted to simply add them. In that case, the issue has to do with the ELSE 0 your outer case statements. I'd suggest changing your formulas to be structured like this: Today: SUM(CASE WHEN event_date = CURDATE() then records else 0 END) -…

@Dheeraj_1996 You should be able to use @nmizzell's logic if you change the aggregation from COUNT to SUM

@DavidChurchman I don't see anything in your beast mode that would be causing the issue. Have you changed anything under the Trellis settings?

@DavidChurchman I'd suggest removing your sorting for now and looking at the the beast mode in your Y-Axis. How are you aggregating your measures?

@kodonnellLT If you want to create calculations for the first 6 months an last 6 months of the year, you will only need to compare whether the month number is greater or less than 6 like below. Jan-Jun SUM(CASE WHEN MONTH(`Period`) <= 6 then `a_amount` else 0 end) July-Dec SUM(CASE WHEN MONTH(`Period`) >= 7 then `a_amount`…

@AFrancis0219 Since you have single quotes around your numbers, they are actually being read as text and being sorted alphabetically. If you remove the single quotes and the ELSE, then they will be read as numbers instead

@StuM To keep the text, just add ELSE `Certification` to your case statement for any rows without a URL

@StuM I'd suggest using a case statement to only include the HTML formatting if the Program Guide URL like below: case when `Program Guide URL` is not null then CONCAT('<a href="',`Program Guide URL`,'">',`Certification`,'</a>') else `Certification` end