GrantSmith Coach

@fromMinnesota It looks like you may need to use square brackets instead of parenthesis with your in statement: It expects an array, which is denoted by square brackets. It's not the same as the SQL version of IN used with beast modes or formula tiles.

When you add a null to a number the result is null. Wrap your SUMs with a COALESCE to return a 0 instead. COALESCE(SUM(ActionsPost),0)+COALESCE(SUM(ActionsPostReaction),0)+COALESCE(SUM(ActionsComment),0)

Can you expand on why you're wanting something similar to IFNULL in your first condition? Do you want to include the AMT if either flag is set to Y? Can you give an example record which would fall into the scenario you're talking about?

Are you doing this inside a formula tile or a beast mode? If it’s a formula tile in ETL you can’t use aggregations (SUM) as it doesn’t know how to group them. You can do it using a group by tile in magic instead and have a custom aggregation alternatively you can remove the sum in your formula and then just sum your new…

The error message can't be supressed but you can increase the row count on the card to a much higher number. By default cards will load 25k or 50k but increasing it will allow more records to be loaded. The caveat to this though is that the more rows you request the more RAM / Memory it will consume on the user's machine…

Under General you can set a No Data message to display if no records are found

On your input dataset you can go to the configuration tab, find your field and then change it to Date data type. If you click the gear next to the field you'll then see a Date settings submenu. Go into that and you can set your date format there: %Y-%m

Feed the dataset into a magic ETL. Depending if you care about the possible duplicated records or not you can either set the output method on your output dataset as Append to just continually add the rows that were imported. Alternatively if you're using dates or some sort of partition that you'll be overwriting ever time…

Regexp replace in a formula tile should work for you. Autoformatting is messing up the expression so here's a screenshot: REGEXP_REPLACE(`field`, 'REGEX HERE', '$1')

The Domo API is authenticated as the user who creates the dataset. So if you created the Client ID and Secret, then it's emulating your user with your permissions. You'd need to create separate Client IDs and Secrets for other users with restricted access to certain datasets to allow them to only see what they would have…

You need to use the backticks (`) instead of the apostrophes ('). Backticks represent a column name; apostrophes are for literal string values, so when it's 'Column A', you're getting the actual string Column A instead of the value inside the field.

Because you have empty strings it doesn't know how to interpret it as a number. You can try and use a formula tile to convert it to null which should then allow you to convert it. NULLIF(TRIM(`Column A`), '')

This is likely because you have the data as multiple rows instead of on a per-brand record. You can use a magic ETL with a Group By tile and then aggregate (with a sum aggregation) your revenue and quantities together so that each brand has one record with all your data together to condense the duplicated rows.

I'd recommend reaching out directly to the training team about this.

There isn't a dataset currently containing the email for you to search. You'd need to search through each connector configuration for the email address. I'd recommend adding this as an idea to the idea exchange to enhance the email connector.

It's hard to say what's going on in the back end. If you right-click on the webpage you can select Inspect from the drop down Then you can select the Network tab, select Fetch/XHR from the top and see if any of them are red. You can then select one to see what the error may be. Does your filter card load if you limit it to…

If you want the connector to add additional endpoints or datasets, you'll need to contact Domo Support, as they control the source code for that connector and would need to make the changes for you. Alternatively you can create your own custom connector and self-publish to connect to the endpoints you want a bit faster…

I'd recommend you split out each of your case statements into their own beast mode so you have just the formatting logic in each to see how each one applies to your data. This will help identify if there's an issue with your specific individual clauses or the entire beast mode.

Can share means they can share it with other users. Can edit means they can change the settings and scheduling of the dataset. In order to edit the dataset, you'll need access to all the rows, which is why you're seeing that.

There isn't a connector that's been created for recruiter data. You'd need to create your own. Domo does have documentation on this in their developer portal here:

Ah. You can't dynamically change the format in the formatting options but you'd have to do it within a beast mode which can be a bit complex. You can use something like this to get you started with numbers or currency formatting:

To clarify, the company timezone is what the UI will display your timestamps with and will convert the values when the data is displayed. Domo assumes UTC for all data being imported.

You can't change the title of a field on your cart with a variable. It's set to whatever you define it when in analyzer. You'd have to use a generic name like Metric or something.

I'd agree. Have two separate cards, one for the line + bar and the other for an HTML table where you can have up and down color-coded arrows. Here's a post I did talking about architecting your data for PoP comparisons, which gives you more flexibility: And here's another post about how to do custom colorization within a…

You can use the LAG function to calculate prior row values. Here's a previous post I did talking about LAG and doing a rolling average:

I've written up a post about this previously here: It will go over the beast mode and have a video on it as well.

You can use the domo.navigate function to go to a different URL: Known Limitation Regular HTML link syntax will not work in Domo Apps. Use the domo.navigate javascript function below to create a link. As for your images, are they included within your app? Have you inspected the network traffic to see if the images are able…

You use the SQL format for comments which is two dashes -- in place of a hash #

If you inspect the network traffic, are there any errors occurring? Typically, Domo has a timeout of 60 seconds, so if it can't get your data within 60 seconds, it'll fail.

CASE WHEN `Date` >= CURRENT_DATE() - INTERVAL 6 DAYS AND `Date` <= CURRENT_DATE() THEN 'YES' ELSE 'NO' END This will check if your date is within today and 6 days ago (Tuesday - Monday using today as an example) You can tweak it if you want to look at 1-7 days ago.