GrantSmith Coach

Have you thought about splitting your metrics into different tables for visualization instead of putting in a blank line? As @MichelleH mentioned they only way is to add rows to your dataset

What do the raw numbers look like and what is the date they get translated to? I’m wondering if it’s assuming they’re Unix timestamps and you can convert them back to Numbers by using the TO_UNIXTIME function in a formula tile

Have you been able to look over the network traffic with the developer tools on Chrome? This will typically show you any connection or network errors that may prevent the iframe from loading correctly.

rdomo doesn't support defining the dataset's schema when you upload it. It attempts to determine the schema automatically. With your numbers it fails the first two checks where it's looking for a specific date format however the third check attempts to conver the number to a date which succeeds so it assumes it's a date.…

rdomo doesn't support defining the dataset's schema when you upload it. It attempts to determine the schema automatically. With your numbers it fails the first two checks where it's looking for a specific date format however the third check attempts to conver the number to a date which succeeds so it assumes it's a date.…

Awesome work @jessdoe !

Look into using FIXED functions in a beast mode with the FILTER NONE option to prevent filtering from being applied https://domo-support.domo.com/s/article/4408174643607?language=en_US

You’ll need a dataset with each metric and definition. You can then use a filter dropdown card to allow the selection of a specific metric. You can then use a table card to display the metric and definition after it’s been filtered

Domo has documentation on creating custom connectors in their developer portal. You can reference it here:

Do you have something in the data label box at the top of those settings? If it's blank it won't display anything, you can use a magic keyword to return the total and then show where you want it displayed on.

You can use the split columns tile in magic ETL or utilize a formula tile with a regexp_replace or split_part function depending on how your field is formatted. Do you have an example of what your data looks like?

Domo doesn't expose that information in the api.domo.com dataset endpoints. You could attempt to get the api call the dataset page is using and use that to get the data you need but it's a more technical route and it's supported by Domo.

Have you looked into utilizing color rules so that if it's < 0 it's green and > 0 it's red?

You can install other libraries in your workspaces. It's documented here:

You could use magic ETL and a regular expression to format your data and then split it. SPLIT_PART(REGEXP_REPLACE(`Parent Lead Source`, '([a-z])([A-Z])', '$1::$2'), '::', 1) This will find the occurrence where a lowercase letter precedes an uppercase character and then injects '::' between them to be able to split it apart…

There may be a beta available that could allow you to change ownership of accounts, but you'd need to speak to your CSM about it.

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.