MichelleH Coach

@Harganz01 If the dataset has been run in Domo, then the History tab should not be blank. I'd suggest reaching out to support with a link to your dataset to look into it further.

@ColinHaze You can also try using the %_PERCENT_OF_CATEGORY macro in the Hover Text. There is also a an option for percent of total.

@Patrick_Cruz You can choose which columns you want to have centered by clicking the pencil icon on the pill for that column. The setting is under Format > Justification

@Alex_K You can do this by adding HTML to your metric in a beast mode like this: case when `Sales` > 0 then concat('<div style="color: #f00">',`Sales`,'</div>') else concat(`Sales`,'') end Here is a knowledge base article on how that works:

@lbg3222 Here are a couple things I can think of: Verify that your connector is set up to look for a CSV file type Verify that you included the "\.csv" in the attachment name expression

@lbg3222 You can use regex in the Attachment Name Expression field to specify which file you want to import. If you want to keep the file that ends in "Statement.csv" then you can use this: .*Statement\.csv The ".*" at the beginning acts as a wildcard to allow any date prefix.

@nmizzell @MarkSnodgrass I've noticed that hitting "Enter" to autocomplete still works as expected. Does it work the same for you?

@Marie_Serrano That's odd. I'd suggest rebuilding the alert to see if that resolves the issue. Otherwise you may need to reach out to Domo support to look into it further.

Agreed, I have been encountering the same issue in both instances using Chrome/Windows 10. I will have to test whether it works as expected on other browsers or operating systems.

@Marie_Serrano When did you create the alert? If you created it after 9:10 EST today, then it has not checked whether the summary number meets the threshold. You can test this by changing the time to later today to see if it triggers the alert.

@SayyedHussain If you want to prevent new members from being added to groups, change the group from an Open Group to a Closed Group so that new members can only be added by the owners.

@ColinHaze There are a couple different options you could use: You can reach out to your CSM about enabling a fiscal calendar in your instance. Here is a knowledge base article about how they work: You can upload a file to Domo with a row for every date and its corresponding month. Then you can join your data to that…

@damen I agree with what the others have said. If you have a numerical field with the actual housing price in your dataset, you could also sort by the average of that field.

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