GrantSmith Coach

No, it will only pull in the data that was updated based on the update timestamp from your database thus reducing the amount of data pulled in and processed. If you're wanting to remove old data then you can look into partitioning as @MarkSnodgrass mentioned.

Does your javascript have code to handle the button click even trigger?

Where are you getting your data from? An actual dataset you're passing to mapbox or are you using a mapbox dataset that is stored in mapbox that you pull in?

Do you have a created or updated timestamp in your dataset? You can use variables to only get the updated or created records based on when the workbench job last ran. You can read about lastvalue here:

The issue is you're attempting to aggregate an aggregate, which you can't do within a Beast Mode; you'd need to pre-aggregate your data in an ETL before attempting to aggregate it in a Beast Mode.

For additional clarity, DDX Bricks are pre-built custom domo apps. The dataset mappings are defined within the manifest file when the app is built so you're not able to make changes to the mappings. As @michiko mentioned you can use a different DDX brick with just a single dataset mapped to it or as @MarkSnodgrass…

When I'm dealing with beast mode logic issues I'll typically break out each part of the beast mode into separate beast modes and use a table chart to see which parts match and which do not to see if there's an issue with the logic.

Here's a screenshot with an example (it's using bogus data but illustrates what I'm talking about):

You can filter the data being pulled into your card directly from the dataset using a where clause in your domo.get operation. Refer to As for query beast modes there are specific flags that need to be set. Domo already provides a Beast Modes brick example for reference here: Depending on which base Brick you're using it…

In a beast mode you can do something like: CASE WHEN `value` >= 1 THEN 1 ELSE `value` END In a Magic ETL formula tile you can use the LEAST function: LEAST(`value`, 1)

Feed your dataset into a select columns to pull the who manufacturer and model then put that into a remove duplicates based on the who and manufacturer. Then feed it to a group by and separate with commas. Repeat this process replacing model with color. Then join your two group bys based on who and manufacturer

Have you tried writing the DATE_FORMAT to new columns instead of back to the same column to so if the format changes?

Once you have the rankings you'll need to do another window function to get the maximum rank for each partition / parent company. Then you can divide the rank by the max rank to get the rank percentage / percentile.

You can pivot your data in an ETL first and then display it with an HTML table.

This is because you're attempting to compare a single row value (format='Percent' for example) while then attempting to aggregate your entire dataset with the AVG. Domo can't interpret this so it's causing an error when attempting to save the card. Another issue I see in your data - if you look at Question Number 1 there…

To clarify you want to have a specific month be the last 3 working days of the last month until the last 3 working days of the specific month? You have a couple of options: 1 - Create a custom date dimension where you assign each date to a specific month 2 - Use Magic ETL and a formula tile to calculate what month each…

You'd need to add an event listener to the SyncButton so that when it's clicked it'll perform a get operation from domo to retrieve the data and re-populate the table. Essentially doing what it does when it's first loaded.

That's what I was curious about. It can be a bit confusing but glad you got it working properly.

Is this only when you do the test of the connector or have you actually run the connector and it's requesting the same data multiple times?

Is Domo interpreting your initial string as a date and the column is a timestamp data type? There a function called STR_TO_DATE which will allow you to convert a string to a date type object based on the format string you pass in. Alternatively you can do TIMESTAMP() to convert your string to a timestamp since it's in the…

Ah that makes sense now. You'll likely need to use a different beast mode to calculate the percent of total using something called a window function. A window function will return an aggregation across your entire dataset or subsection of data. Current Year SUM(CASE WHEN YEAR(`Date`) = YEAR(CURRENT_DATE) THEN `Value` END)…

The concept is the same if you're using beast modes to calculate the YTD_22 and YTD_23 values, just create a new beast mode by subtracting your 22 beast mode from 23 beast mode as @ColemenWilson mentioned.

Beast modes perform on a row by row basis for a singular value. You can’t create multiple rows with a beast mode. You’d need to do that in an ETL

Which fields are nested beast modes? What definitions go to which field? Have you tried using a table card and breaking each part of the beast mode into separate sections to determine which part is causing issues?

You can log in as an Admin and go to More > Admin > Dashboards, search for your dashboard in question then check the checkbox next to it. In the upper right select Add dashboard Owner.

You can use a window function for something like this: SUM(SUM(1)) OVER (ORDER BY `Score` DESC)

You can change the data label in the setting to use other fields or values so if you want two separate columns for tie tooltip you can put them into the tooltip values

Can you pass in filters based on the date such that start_date is between your date range and end_date is between your date range?

Because your website and domo are coming from different domains by default you'll get the CORS error which is a standard security check to make sure you're not attempting to access a website from a completely different website. This is to avoid click-jacking attacks. There isn't a way to avoid this except for turning off…

A Domo Brick is a simplified custom app. You can see in the upper left portion of the bottom data mapping tab the name of the dataset that's been mapped and which dataset it's mapped to. The manifest file is already created and deployed with a DDX brick. If you need additional control over the manifest file then you'll…