GrantSmith Coach

COALESCE will work in either a Beast Mode or a formula tile or custom group by aggregation logic in Magic ETL.

@hollyrene1225 - I recommend restructuring your data so that you have multiple periods within the same dataset. I've done several writeups on this and it allows you to show multiple periods on the same graph. You can find more information on how to do this here:…

You can coalesce the values to default to 0 if they're null: SUM(COALESCE(`Budget GP`, 0)) - SUM(COALESCE(`Gross Profit`, 0)) Edit: updating the formula.

You can also use the Date Selector on the page as well to select a specific granularity on the graph. Alternatively if you want to allow the user to display the MoM, YoY and WoW on the same graph you'll have to restructure your data. I've done a write up on how to do this here:…

You can use the pfilters get parameter in the URL link. You can find more documentation on it here: 2. In your URL you can have it open in the same window with target="_self" <A HREF="https://public.domo.com/embed/pagse/ASQ72D?pfilters=…" target="_self">Hyperlink</A>

Currently the maps don't support highlighting just the states with a border. You could attempt to create your own custom map with the states having the border applied already and then just display the chart. You can read up more on custom charts here:

You can use the group by tile to group based on the Position Owner and do a count. Then, do another group by tile to do it based on the candidate owner. Once you have those two, you can full outer join them together based on the Owner name. Finally you can fill the count field into a formula tile and to an IFNULL function…

A more straightforward method rather than multiple CASE WHEN statements is to use SPLIT_PART SPLIT_PART(`Fruit`, ',', 1) -- First in CSV SPLIT_PART(`Fruit`, ',', 2) -- Second in CSV SPLIT_PART(`Fruit`, ',', 3) -- Third in CSV

@Data_Devon It depends on your use case. Having your columns wide will allow you to consume fewer rows overall, potentially reducing your costs. On the other hand, Domo likes things as rows to deal with filtering. If you want to filter your records based on the City, then you'd need to pivot your locations stomore easily…

I'd recommend logging a ticket with Support to have them help diagnose your connector issue as they own that connector.

Have you tried redirecting the user to the same URL but utilizing an empty pfilter get parameter?

If it's not included in the standard connector you could try and leverage the JSON No Code OAuth connector to pull this information.

Have you inspected the network traffic to determine if you're getting an error with your JavaScript code used to save the records?

Sorry getting my languages mixed. You can use NOW() instead of TODAY()

You can use a beast mode calculate if it's a future date: CASE WHEN `StartDate` > TODAY() THEN 1 ELSE 0 END Then just filter for 0 in the beast mode.

In the buildForm function, you'd need to set the input box size conditionally based on the key field.

AppDB should update every 15 minutes. Do you have "syncEnabled" set to true in your manifest? For reference:

Change Type of Values from Number to Text

You can use a window function to do a lag LAG(`Action Time`) OVER (PARTITION BY `Ticket Number` ORDER BY `Action Time`) This can also be calculated using a Rank and Window tile in a Magic ETL Then taking that you can calculate the time difference: SEC_TO_TIME(UNIX_TIMESTAMP(`Action Time`) - UNIX_TIMESTAMP(`Prior Action…

You can use a case statement to convert the 1 to 'Priority': CASE WHEN `field` = 1 THEN 'Priority' ELSE 'Non-Priority' END

When you go in and edit the layout of the dashboard, are you able to see the delete / trash icon when hovering over that section?

You can use a Select Column tile to set the ordering of your columns in your output dataset.

You can feed it into a regular expression in a formula tile to convert () to a negative number with something like this: REGEXP_REPLACE(`field`, '\(\d+\)', '-$1')

You need to remove all non-numerical characters first. In a formula tile you can do something like this: REGEXP_REPLACE(`field`, '[^0-9.]', '') Then feed that into the Alter Columns tile

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…