GrantSmith Coach

This is because how your Beast Mode is written, it aggregates everything first and then just subtracts an hour. What you'll want is (assuming you're filtering for records where the duration is already > 1 hour: SEC_TO_TIME(SUM(`End Time` - `Start Time` - 3600))

Filters work on a per column basis so you couldn't have an individual filter for all of the dates. What you may be able to do is utilize a Date Dropdown variable, write a beast mode to determine if any of the dates are between the start date variable and the end date variable and return 1 if they are or 0 if they are not…

You can use a beast mode to define a custom sort value to use in the sorting section of your chart CASE WHEN `field` = 'Ro' THEN 1 WHEN `field` = 'Ac' THEN 2 WHEN `field` = 'Tr' THEN 3 END

You'll need to make sure your app is sending out the filter request to the container. You can use the domo.filterContainer() method outlined here:

The last time I utilized the backup and import backup, it created new jobs with the same definition but with new datasets and job IDs, which caused a lot of issues and duplicated datasets. What I recommend doing is doing a registry migration where it treats the new server as the existing server and Domo will restore all…

Have you reached out to your Domo Account Team to have them help you get this embedded into your embeds? They'd need to do it as they control the embed code. The process is outlined here: Follow these steps to enable FullStory tracking for your embedded content. Contact your Domo account team and request to enable embedded…

Have you tried using the TBA connector with a custom saved search?

when would the order be defined? Based on the 2019 data point or 2024?

On your top condition you are returning `Total referrals `=0. If you want it to be 0 in this condition then just return 0 case when `Parent OR AgencyName` = 'Aspire Home Healthcare' and `Date` >= '10/23/2024' then 0 ELSE `Total referrals` end

You should be able to just use the REPLACE function like you mentioned: REPLACE(`Client Name`, '"', '.') How is your beast mode not working? What are you getting and what are you expecting?

It's definitely shared with your user. Next steps to confirm I'd recommend going to https://developer.domo.com/manage-clients and logging out if you're already logged in, then log back in making sure you're using your user when you're logging in. You can then confirm the client ID and Secret that you're using with your…

Try putting your aggregation outside of your case statement SUM(CASE WHEN `Age group` IN ('121-180 Days','181-270 Days','271-365 Days','366-730 Days','731 Days+') THEN `CurrentBalance` END)

Essentially, the error tells you that the user who created the API Client (client ID and secret) doesn't have access to some of the cards on the page you're embedding. I'd try to unshare and reshare the page with the user and confirm that the embed ID is correct. The scopes on the client just tells the API which API…

Beastmodes don't have access to the selected date grain on the date selector so you won't be able to do it that way. You could utilize a variable to select the date grain which you would have access to.

Apologies @muhammadtalha I pasted the wrong link. Here's the KB article which outlines this process: I've updated my prior comment as well.

As this sounds like an internal Domo issue, I'd recommend contacting Domo Support to have their internal team look at your issue.

By default, Domo tracks content like cards and dashboards, loads, and interactions like Filters, Drill Paths used, and exports. The 3rd Party Analytics feature allows you to monitor your digital experience and use Digital Experience Intelligence (DXI) solutions like FullStory, Sprig, or Heap to track interactions beyond…

Your drill card needs to have the same field that you're drilling down with. Do you have the country name or whatever field you're using in your world level map in your city level drill card dataset?

You have a typo in your style <div style="background=color should be <div style="background-color

I'd recommend switching your logic over to a Magic ETL. MySQL runs on 5.6 which is an older version and due to the nature of those dataflows they run sequentially and can run much slower. I've seen Magic ETL dataflows with the same logic take up to 90% less time to execute.

You can, on the dashboard there's a wrench icon in the upper right. Select Save As and it'll ask if you want to duplicate the cards or not.

Are you utilizing Color Rules in your chart?

Hi @Nandha_Kumar_1 You only have 323k rows, so there are likely some chances for efficiency improvement. When I'm designing an ETL, I like to be a teapot—short and stout. Short—Filter your data as soon as possible to reduce the number of rows. Use a select column or alter column to select or drop columns, respectively, so…

I'd recommend logging a ticket with support to have them assist with this as it's an issue dealing with the underlying architecture.

I'd recommend logging a ticket with Support as it appears to be a backend issue

Currently this isn't possible however I'd recommend adding an idea to the Idea Exchange to enhance the email connector to include the metadata like the subject.

For OAuth connections which don't have a dedicated connector I try and utilize the JSON No Code OAuth connector to connect with those APIs.

Because you have variable length in your string I'd recommend utilizing a formula tile in a Magic ETL to perform a regular expression. FGI REGEP_REPLACE(`Destination`, '^[^\-]*\-((\w\-)?FGI)-(\d{2}\.\d{2}\.\d{4}.*)$', '$1') Tail end: REGEX_REPLACE(`Destination`, '^[^\-]*\-((\w\-)?FGI)-(\d{2}\.\d{2}\.\d{4}.*)$', '$3') You…

Converting to the new upsert will allow your dataflow to run quicker, as you'll only pull in the data that you're updating instead of the entire dataflow. With a recursive dataflow, it starts to run slower over time as it needs to pull in the ever-increasing dataset. It also simplifies the logic of your data flow. I'd…

SUM(`quantity` / SUM(1) FIXED (BY `product_id`)) Use a fixed function to determing the number of records you have for each product, divide the quantity by that to get fractional quantity and then SUM it all together to get the overall quantity.