Best Of
Re: Any row is added alert issue
I noticed that the 'Any row is added' option is still available on datasets that aren't views, so maybe you can get the same results you had by doing this in Magic ETL instead of a view. Also, it may be worth opening a ticket with Domo support re: the email, since that just doesn't seem right.
Re: Ability to Search ETLs
This is a great idea and is on my roadmap (no official dates available yet). This is something I'd really like to get done this year if possible.
Re: Image size doesn't reflect settings (table)
Unfortunately Mega Tables do not support HTML tags or style attributes. See the below documentation. If you have control of the images you are trying to use, your best bet is the change the source image size.
Re: OKTA CONNECTOR
Can you confirm the API token has full permission to access the events? There may also be something blocking it, like a rate or size limit by the Okta API.
Re: Multi value comparison
@LearningNinja if you use Domo's built in date range/grain page filtering, this is handled for you. However, you can't specify the exact year. When you use a filter card, the rows are filtered down, so you would need your comparison values in a column to be able to reference them.
For example, here is a card which is defaulted to show the current year compared to the previous year. You can see that 2024 is 2.3k and all of 2023 is 5.39k.
If you select YTD using the built-in page filter, now we are comparing 2024 ytd to 2023 ytd for the same period.
I understand that you want to be able to select a year, and see the previous year as a comparison, but how would this work if a user also selects a quarter? Would you want to show the same quarter in the previous year? The previous quarter in the same year? Same question for month. If you're just wanting to always compare the same period, but in the previous year, you could achieve this as follows.
Set this up comparison periods in your ETL and stack those. This would basically look like this
Then in Analyzer, you could set up the following beast modes.
Gauge Value
SUM(case when compare_type = 'Current' then Column end)
Comparison
SUM(case when compare_type = '1 Year Ago' then Column end)
Then if you create your filters off of the column "compare_date", you drive interactions like this.
For example, here no comparison is selected.
Here we are comparing 2024 Q1 to 2023 Q1.
Filter persistence between pages within App Studio
Hi, I'm starting to play around with the App Studio. I was wondering if it would be a good way to have multiple dashboards within one place. Is it possible to persist filters across these pages within the app? For example, if I select a campaign ID in one dashboard, and then navigate to another dashboard within the app using the navigation at the top:
How can I have that filter automatically applied to all other dashboards? I know it isn't possible for filters to persist across separate dashboards in general but I'm hoping App Studio is a way to do this. Thank you.
Re: Being Able to Change Default Colors
They have brand kit, but from what I understand, it makes you lose all of the standard colors. It would be amazing to have an additional row of colors that are custom for the instance so that branding can be done without messing up every existing visualization. (Which is what happens currently.) Plus, this should not be an additional expense.
Re: In Beast Mode
If I'm understanding you correctly, you want to add 2 numeric columns (Spot & Fixed) when another unnamed column is equal to the value "GET". If that is true.
CASE WHEN Unnamed Column = "GET" then Spot + Fixed END
If you want to aggregate up, you can either do that in your card settings, or in the beast mode itself.
SUM(CASE WHEN Unnamed Column = "GET" then Spot + Fixed END)
Re: In Beast Mode
If you are looking for anything "like" GET then you can use the following beastmode and then apply it as a filter:
CASE WHEN UPPER(`yourField`) LIKE '%GET%' THEN 'In' ELSE 'Out' END
If you want only rows where the field is equal to GET then you would use:
CASE WHEN UPPER(`yourField`) = 'GET' THEN 'In' ELSE 'Out' END
Re: Split Edit and Share Grants
I just submitted a very similar idea topic:
Hopefully the squeaky wheel gets the grease here!









