GrantSmith Coach

Having one audience per record. Something like: C-Suite | 19 | Enterprise VP | 19 | Enterprise Director | 19 | Enterprise You could utilize Magic ETL 2.0 formula tiles to use the SPLIT_PART function and grab each entry in your CSV list and then append each of those formula tile outputs to each other.

You can calculate the length of the string, remove the character you want, recalculate the length and take the difference. LENGTH(`Color`) - LENGTH(REPLACE(`Color`, ',', '')) + 1

Can you apply an aggregated filter to have count of your metric be greater than or equal to 10? You can set the filter in each of your drill downs to be the minimum value you're looking at.

How exactly does Domo Everywhere work? Is it an add on that you purchase to basically iFrame a dashboard to an external website? Simply yes, there are two different versions of Domo Everywhere / Domo Embed - There's a private embed which allows you to utilize an iFrame but requires users to have a Domo license. Then…

Alternatively you could restructure your data so you have one record for each audience to allow you to count, filter and group by the different audience types easier.

There isn't a way to dynamically hide or show a card based on a filter condition. I'd recommend adding it as an idea to the Idea Exchange.

You'd have to have an Admin move the pages under the Admin - Pages section to change the parent page of the pages you wish to move.

You'd need two separate jobs, one for hourly append and one for monthly replace updating the same dataset. There is some risk involved with this as it can cause them both to run at the same time and get unexpected results. What you can do is limit the hourly job to run in between certain hours and then once a month or…

You can use a window function or fixed function to calculate the row number. The following example will rank them based on the Total Revenue column. You can replace that column with others to get the row number based on other values. This won't take into account ties. SUM(SUM(1)) OVER (ORDER BY `Total Revenue` DESC)

Google represents dollar amounts as micros. $1.00 = 1,000,000 micros (or $0.01 = 10,000 micros) so if you want to convert it to cents divid your value by 10000.

It's been around for a while but can be easy to overlook. Glad I could help. If you could accept the answer so others can hopefully find this easier in the future I'd appreciate it.

You can download the dataset as a a CSV and open it it Excel. Go to the Data tab on the dataset, click the three dots in the upper right and then select Export Data. As for your error - do you have your instance name put into the customer field correctly including the https:// prefix? For example:…

Hi @CarolineRogg1 It sounds like you want a Trellis chart. You can read up on these here: https://domohelp.domo.com/hc/en-us/articles/360043428713-Applying-DataSet-Columns-to-Your-Chart#6.

Here's a REGEX version: Something like this might work for you in a formula tile in Magic ETL 2.0: REPLACE(REGEXP_REPLACE(`landing page url`, '^.*ufhealth\.org\/([^?]+).*$', '$1'), '-', ' ') It's looking for your base URL and then pulling everything after it until it finds a ? character and ignoring everything before and…

You might want to look into Segments to show the total but not have your filters apply to the totals. You can read up on Segments here: https://domohelp.domo.com/hc/en-us/articles/4403089503383-Creating-Segments-in-Analyzer

There is a Domo Governance Datasets connector which has several datasets including one on beast modes. You can pull that dataset and filter to a specific dataset ID. You can read up on this here: https://domohelp.domo.com/hc/en-us/articles/360056318074-Domo-Governance-Datasets-Connector

You're using backticks (`) for your 2021 value and not a single quote to denote it's a string (') CASE WHEN `end_date__c` >= '1/01/2021' and `end_date__c` <= '12/31/2021' then '2021' else '0' end

You'll need to pass in a specific value with the pfilter for it to work properly. You can use the row's value with the specific column (Campaign Name in your case) and concatenate it with your URL. There's an example of this here:…

Hi Hal, you can use pfilters for this and dynamically create your URL based in a beast mode based on the fields you want to filter. Having the pages embedded isn't a requirement.

Alternatively you could store three values in a lookup table dataset and use an Etl to left join it to your original data. Then use a formula tile to do a coalesce to set the default value (your else clause) so you keep your lookup list in a single place rather than possibly across multiple beast modes.

Instead of using ELSE WHEN just use WHEN for additional cases. Use just ELSE for your default clause.

You can utilize a Rank & Window tile (see https://domohelp.domo.com/hc/en-us/articles/360044876094-Magic-ETL-Tiles-Aggregate#3.) within Magic ETL to select the LAG value of your column. Domo does offer a Data Science suite of tiles which includes the outlier detection tile to calculate standard deviation but this is a…

This isn't possible as you can't aggregate a window function within a beast mode. What you'd need to do is perform your lag in an ETL and then calculate the average in your card. You may lose some filtering abilities as it's going to be pre-aggregated.

Use an ETL to group your tickets dataset based on the identifying column (id / name etc) and do a count on your ticket id field, then use a JOIN to join that with your User table based on your identifying column

When you say 47 rows and 14K records - do you mean 47 columns and 14k rows? Have you confirmed that each row has the same number of fields?

Use DataSet views. It’s the same underbelly but views have more options and eventually fusions will be deprecated. Converting them shouldn’t have any issues as it’ll keep the same ID just stored in a different format. I haven’t had any issues swapping for a view.

You're getting a blank because your CASE statement is likely returning a NULL value. Are you displaying you data split by anything other than Company?

Earliest date for the year MIN(MIN(`Date`)) OVER (PARTITION BY YEAR(`Date`)) Latest date for the year MAX(MAX(`Date`)) OVER (PARTITION BY YEAR(`Date`)) Remove the partition clause if you want it across your entire dataset.

That's how the data is displayed. Text and dates are typically left justified and numbers are right justified. There aren't any extra spaces or padding added automatically (not without possibly having spaces in your actual data) Do the IDs exist in both dataset? Are they both the same datatype (numbers?) Have you manually…

Yeah that sounds about reasonable. The one caveat to recursive dataflows is the don't scale the best as the larger the dataset grows the longer it will take to run the ETL (more data to transfer means more time).