MichelleH Coach

@verytiredgirl FIXED functions have the ability to aggregate while ignoring certain fields when filtered using FILTER NONE, FILTER DENY, and FILTER ALLOW, which you can read about here: In your specific case, if you wanted the denominator of your calculation to ignore all filters, you could set it up like this:…

@_DanielB_ FIXED functions have the ability to aggregate while ignoring certain fields when filtered using FILTER NONE, FILTER DENY, and FILTER ALLOW, which you can read about here: https://domo-support.domo.com/s/article/4408174643607?language=en_US In your specific case, if you wanted the denominator of your calculation…

@Kwainscott You can use HTML to add hyperlinks to table cards or summary numbers! Here is a KB article on how that works: https://domo-support.domo.com/s/article/360043430033?language=en_US

@SPD I've run into the same thing with macro-enabled workbooks and have been able to resolve this by saving a copy in .xlsx format to upload to Domo.

@art_in_sky You can also try sorting each category by "Ascending" or "Descending" under Chart Properties General

@helenwei Yes, I recommend saving the date picker as "Month to Date" in Analyzer so it defaults to the dates available so far in the current month

Awesome! I'm glad it worked for you!

That's not something I've done before, but I'm sure other members of the community can help you with that

I've been able to create users without the invite email by creating them in the CLI tool rather than the Domo UI. If you use the create-user command without the -i true parameter it will not send the email.

@yawkeyway11 Are you able to share your SQL code or a screenshot?

I recommend reaching out to your instance admin to verify that you have the correct role/grants to use MagicETL

@calvert_schaefer It looks like the leading zero check box isn't available for that connector, but it is for the default uploader on the File tab if you're able to use that instead. Otherwise, if your Store ID field is always 4 characters you can create a beast mode to add the leading zero back like this: case when…

@calvert_schaefer There is an option in the file upload connector that you can check to keep leading zeros like this:

I agree with @Data_Devon about the dates being sorted alphabetically. If you remove the sorting altogether, the card will automatically be sorted chronologically by the date in the X Axis.

Great idea! In line with the Pareto Principle, I would also love to be able to dynamically limit the number of bars based on the cumulative percentage (i.e. only display named bars that make up the top 80% and group everything else into "Other").

@Anna_Otake This is a simple enough use case that I'd suggest creating a scheduled report off of a card that's powered by the People DomoStats dataset, rather than using Workflows.

@verytiredgirl You will no longer need the date drop down filter if you are using the filter view, but the reason I recommended the filter view is that it's better at handling relative dates.

@CK_16 The error can be resolved by rearranging the calculation so that the numerator and denominator of your beast mode each contain a single case statement within a sum like below. sum(case when year(`trx_date`) = 2025 then `extended_amount` else 0 end) / sum( case when `Product Category` like 'Product 1%' and…

@verytiredgirl Instead of using a specific card for your date filtering, I suggest using a filter view to default all cards to Previous Month. To prevent the bar graph from filtering to just last month, you can uncheck the "Allow global date" box under that card's filter exceptions.

@user082291 It sounds like you may be exporting a dashboard where all the cards are in the Appendix if they are all showing on one slide out of order. I second @MarkSnodgrass's input about arranging the cards in layouts to determine where they appear in slides.

@andyhicken If you don't have buzz I'd suggest directing the user to the "Forgot Password?" button on the log in screen to retrigger the email. Alternatively, admins have the ability to change users' passwords from the admin page.

@s_f_OTT If the value of your date field is on a Saturday, then the WEEKDAY function will return 7, not 0. So if you change the 0 in the first condition of your case statement it will apply the correct number of days to subtract.

@holodude Are all your beast modes the same? The rounding in the Productivity field looks suspicious, and if the ProdMinusTarget references that calculation it could also be impacted.

@holodude Cards should automatically update when the underlying dataset refreshes. Here are a few things to check if it's not working as expected: Are there any filter exceptions applied to the original cards on your dashboard that would not apply to test card you just created? Are there duplicate datasets with the same…

This would be a really nice quality of life enhancement. The lack of real estate is especially challenging when working from a laptop screen.

@James_Lord I'd suggest sharing the alert with the same groups used to grant access to the relevant dashboards. You should be able to accomplish this without a workflow, and hopefully saving you some credits.

@Utz I generally recommend aggregating the numerator and denominator when using division in Beast Mode like this: sum(`DeliveredMarginDefine`) / sum(`QtyMarketingForecast`) Otherwise, the card is dividing each dataset row first before then summing them, resulting in unexpected outputs.

I wouldn't play anything. I'd prompt my agent for the sound I want.

@qzqzqzqzqz Different systems may have different settings. Snowflake may be storing your datetime fields with a time zone, while Salesforce does not.

@qzqzqzqzqz Domo will attempt to convert your datetime fields into the time zone in your instance's Company Settings, so it's likely trying to convert to the default UTC. If you decide to change this setting, do so with caution to avoid disruption to your existing content. Otherwise, there are options in Magic ETL to…