GrantSmith Coach

The version of MySQL (5.6) that Domo is on doesn't support window functions so you won't be able to do that in a MySQL dataflow. You can do unbounded preceeding and current row within a Magic ETL 2.0 dataflow using the Rank and Window tile to do what you're wanting to do.

Hi @DomoNewbie Do you have any NULL values in your Value field? Subtracting a null value would result in a NULL.

Hi @vgupta Currently this isn't an option. I'd recommend adding it to the Ideas Exchange as an idea for an enhancement.

@MarkSnodgrass - First! 😂

You can use a conditional sum like the following (assuming you're not grouping based on the description field) SUM(CASE WHEN `Description` IN ('0_0-10_Period', '0_11-30_Period') THEN `Value` END)

Since you're only looking at the number of days in the current year have you tried using DAYOFYEAR(CURRENT_DATE()) as your denominator (I'm assuming this is the case since you mentioned 70 days even though you have 2021 as the year)? I'd recommend breaking down each component of your beast mode into it's own beast mode and…

@Dr_Duru I'm assuming you're using a MySQL dataflow here. What are you data types for field 3 and 4? String comparison is typically slower than numerical comparison. Also have you added indexes on field3 and field 4? I'd also recommend trying to utilize Magic ETL 2.0 as that is typically much more performant than MySQL…

To add my two cents to Mark’s answer: MySQL will load your datasets sequentially so the more datasets you have the longer it will take. Magic will load them in parallel / at the same time so it’s a lot faster. I try to use magic unless I need to do some very complex join. Even then I’ll have the MySQL do at little as…

I’ve gotten some success updating to the latest version of workbench and also pressing enter when I enter a value for my replacement variable. This will show an empty row but have found that typically will save the variable

Did you try and run the beast mode and it said it couldn’t find it or are you looking for it in the list?

@ankt84 Domo currently doesn't provide the actual owner of the beast mode in the governance datasets, only the card owner. I'd recommend putting this as an idea in the Idea Exchange.

Hi @Hedger You can use some case statements to convert your values to 1 or 0 and then add them together: CASE WHEN `Column A` = 'Yes' THEN 1 ELSE 0 END + CASE WHEN `Column B` = 'Yes' THEN 1 ELSE 0 END + CASE WHEN `Column C` >= 1 THEN 1 ELSE 0 END + CASE WHEN `Column D` >= 1 THEN 1 ELSE 0 END

@Chet Do you have multiple client IDs and secrets? Have you confirmed you're using the correct one (This has happened to me multiple times)? Are you able to make that API request using another tool like Postman to narrow down if it's something with how Domo is sending the request with the Domo action or if it's how Domo is…

Hi @Salmas In your example for Token ID 108 you have two records - Are you wanting to keep these records separate or should they be merged into a single row? Assuming they're separate rows you can use COALESCE and NULLIF: COALESCE(NULLIF(`A`, 0), NULLIF(`B`, 0), NULLIF(`C`, 0)) NULLIF returns null if the column given is 0…

If you reload the page does it still show it as having other objects being affected?

Single Value card with a beast mode will get you what you're looking for for the current date: DATE_FORMAT(DATE_SUB(CURDATE(), INTERVAL '1' MONTH), '%M %Y')

I've done write ups of this in the past about how to structure your data differently to get YoY periods like you're requesting. You can read up on it here: https://dojo.domo.com/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest

How is this dataset coming into your instance? Through a connector or through workbench?

You can utilize Domo Workbench or the database connectors to write queries against your instance and bring in that data as a dataset but there isn't an actual interface to explore your data by writing queries against it,.

@brave14 Try using a formula filter to convert your string you're using for comparison to a date: `TicketCreatedDate` >= DATE('2022-01-01') AND `TicketCreatedDate` <= DATE('2022-02-21')

DONE

I was getting the field formatting mixed with the summary number formatting. For whatever reason Domo doesn't have that option on the summary number formatting options. You'll need to have a separate beast mode for your summary number where you divide the final number by 100 and format it as a percentage.

Uncheck the box that says to multiply by 100 and that should resolve your issue

You won't be able to aggregate on an aggregate within a beast mode. You'd need to pre-aggregate your data to get the average signups and average targets. You can then use that aggregated data and apply the beast mode to count the number of records which meet that criteria.

Currently it won't send a buzz, likely because that'd be a lot of unnecessary buzz messages users would get. If you're looking to configure a notification when a measure changes have you thought about utilizing an alert to send out a notification to a group that way?

This isn't compatible with the group by options in the date range because we're defining how we want to do the grouping in the window function with the PARTITION BY section.

Hi @dylang91 How are your numbers weird? IFNULL returns the second parameter if the first one is NULL. This means you're subtracting NULL - CaseSubmissionDate which equates to null. NULL / Number is also NULL. What you'd likely want is something like this where you're calculating the value if it's not null:…

My guess here is that Facebook deprecated any API version prior to v12 recently and it cause an issue with the connector but was upgraded to a newer version so it’s working now. Complete guess though. I only know Facebook deprecated their APIs prior to v12 because it cause me some issues outside of Domo

@Abhijith wrap your entire case statement with the SUM instead of just the condition SUM( CASE WHEN `Approved` = 1 THEN `Total Charge` ELSE 0 END) SUM( CASE WHEN `Approved` = 0 THEN `Total Charge` ELSE 0 END)

This appears to be a display bug. I’d recommend reaching out to support and logging a case with them.