GrantSmith Coach

CASE WHEN `field` = '[]' THEN 0 ELSE (LENGTH(`field`) - LENGTH(REPLACE(`field`, ',', ''))) + 1 Some string manipulation options to assist. If it's an empty array list, return 0, otherwise determine the length of the string and subtract the length of the string with the commas removed (count the number of commas). Add one…

You can do a running total with a beast mode with a conditional add instead of using the running total on the card. CASE WHEN `Date` < CURRENT_DATE() THEN SUM(SUM(`Sales`)) OVER (PARTITION BY YEAR(`Date`) ORDER BY `Date`) END This will exclude any future dates today and beyond so you only have a line for the months…

It is, you can use a FIXED function in a beast mode to do this. Here's some documentation on it: https://domo-support.domo.com/s/article/4408174643607?language=en_US - See Use Case #5

What is the formula you're using? You could do something like: CASE WHEN `field` IS NULL THEN 1 ELSE 0 END Then aggregate your dataset and SUM that field to get a count of the records.

This isn't an option currently, but I'd recommend this idea to the Idea Exchange.

You can use some window functions in a beast mode to do this. Specifically the LAG function. Here's a post on how to do this: https://community-forums.domo.com/main/discussion/52679/domo-ideas-conference-beast-modes-rolling-averages

The only way to load just the page and not all of the navigation top and sidebars is to use Embed. If you don't want users to log in when doing the embed, you can use a Public embed, but that would give anyone with the URL access to the page. https://domo-support.domo.com/s/article/360043437993?language=en_US#public_embed

To avoid the issue of comparing a Monday this year to a Sunday last year, for example, instead of subtracting a year from your date, you can subtract 364 days. I've done a write-up about restructuring your data for period over period type analysis that outlines what @ColemenWilson is talking about. You can read more about…

If you use the most recent value of the BOOKMARKETVALUEPERIODEND for your summary number you can then configure a card alert to detect a change for more or less than 5%. https://domo-support.domo.com/s/article/360043430513?language=en_US

You can use a beast mode and the lag window function to calculate the percentage difference: (`Login Value` - lag(`Login Value`,1) over(PARTITION BY `Member` ORDER BY `Login Date`) ) / lag(`Login Value`,1) over(PARTITION BY `Member` ORDER BY `Login Date`)

You can't embed just the dashboard that way as it'd load the entire page along with the navigation bar. If you want to embed just the page you can use a Private or Public embed option with Domo everywhere.

Currently this isn't possible, I'd recommend adding this to the idea exchange.

No, most cards don't support hyperlinks. Only table and HTML table cards support it.

Is the email the only field you're joining on? Have you used the formula tile to calculate the LENGTH of each of your emails to make sure they're the same length?

Is # Devices a beast mode? If it's a column you can select the column in the table and under aggregation select SUM. If it's a beast mode you can wrap it in a SUM value depending on how your beast mode is written.

You can group by your partition / bucket that you're wanting to sum across. If you want to do it over the entire dataset, use a formula tile to create a new field called "Join Column" with a value of 1 then group based on that new field. After the group by you can use a join tile to join your aggregated data back to each…

You can use the IN operand and give it a list of values you want to include in your filter. There's an example of this on the Domo developer website: https://developer.domo.com/portal/buk5zwk1pvjwh-url-parameters-in-embedded-content#pfilters

You can utilize Magic ETL and the Dynamic Unpivot tile to take your columns and convert it to rows. Here's more information: https://domo-support.domo.com/s/article/360044951294?language=en_US

You're sorting by the SUM first and then sorting by the year. Move the Year to be the first thing you sort on.

You cannot but I’d recommend adding a new idea to the idea exchange As a workaround I’d recommend writing your query in an actual database IDE and then paste it into workbench

I'd recommend logging a ticket with Domo Support as they were having API issues last night and this may be related

What I recommend is creating your own date dimension dataset with your defined periods (FY and NextFY). This will allow you to have a single date you can then use in your chart and conditionally use a beast mode to display either FY or Next FY. I've done a writeup in the past on this for period over period analysis you can…

This appears to be a system-wide issue. I'd recommend logging a ticket with Domo Support. I'm having the same issue as well.

There isn't a way to spread out the data labels currently as they're tied to the end of the lollipop. You can submit an idea to the Idea Exchange to improve label positioning and spacing. You can make the chart longer or display less data so it has more space to display the labels and lollipops.

What issue are you experiencing? How is it not working? Have you tried splitting out your conditions into separate beast modes and using a table card to see the values for each row of data?

You can use a Formula Tile and call your new field 'Completed' and use a CASE statement as your formula: CASE WHEN `Screening Date` IS NULL THEN 'No' ELSE 'Yes' END

You can use a beast mode to calculate the average AVERAGE(`Loan Amount Field`) Then you can use it as a summary number or put it into a tooltip field and reference the tooltip in either your data label stubs or hover text settings

@ArborRose The last column is showing 1 / count because it's the summary row on a table, it's not data within the dataset. I agree with @ST_-Superman-_ a Fixed function filter should work to have you only see sites with >= 3 tickets.

CASE WHEN DAYOFWEEK(CURRENT_DATE()) IN (1,7) THEN 'Weekend' ELSE 'Weekday' END

Are you attempting to utilize a single field in your recursive dataflow join for your key field? You should be able to select multiple key columns which uniquely identify each record. Just make sure you're joining on all of your key columns in the join