Best Of
Re: Card Limitations
I also get the sense that Domo has diverted resources to AI at the expense of the core product. At this point Editable tables are not stable enough to use for testing and are a feature my org has identified as vital.
Re: Provide Field Definitions for Domo Stats and Domo Governance Reports
Hi @Abby Brinks We are adding those definitions to the AI Dictionary. Some Domostats reports already have the definitions added. The others are on their way! Thanks for the signal!
Tasleema
Re: Drill in place to filter the Dashboard
Data_Devon,
This Card is in app Studio. Im not sure im following. I added a second View on my drill path and its drilling in place which is great but its still not filtering the other cards on the app. It just keeps drilling down. I tried to enable interactive filters but it no longer allows me to drill in place.
Does that make sense?
Re: Domo Data Model
I'd be curious what the official "Domo" answer to this is. From my perspective, it depends. One big dataset with all the fields you could ever need has some advantages. You can apply color-rules once, BeastModes once, variables, etc. Governance can be simpler, and you might be able to save on execution credits.
However, many Domo interactions will work across multiple datasets as long as they share common fields. For example, you can filter cards powered by different datasets, as long as they have a common field. Similarly, cards can cross-filter each other if they have a common field. What types of interactions are you trying to manage?
You can get pretty far in Domo with discrete, simple datasets. Views of datasets are cheap/fast and can do a lot of the basic data manipulation you would need for most cases (rename/reorder/filter/join/formula).
Re: SQL Server Workbench Writeback ODBC Connector Plugin not getting Installed
I ran into the same issue trying it on my workbench. I would create a support ticket and have them look into it as it is not isolated to just you.
Re: Same period last year measure
My preferred beast mode when showing the same point in time for different years is to use the DAYOFYEAR() function. It would look something like this:
CASE WHEN DAYOFYEAR(dt) < CURRENT_DATE() THEN 'Include' ELSE 'Exclude' END
If you put this beast mode in your filters and filter to Include, this should do the trick for you.
Dynamic Pivot
I have a table with a combination of fields and a target value. I want to concat all the fields (Retailer, Field, Target, Strategic Priority) and pivot the table so they are all columns with their respective Target Value underneath.
I know how to do this with the Pivot option in which I manually create a new column for each combination. However, is there a way to have this automatically create new columns? My concern (beyond a whole bunch of manual input - I currently have 67 rows) is there will be rows (with new field combinations) added to this dataset and they'll be excluded unless I recognize and manually add them in.
Below is a screenshot of the data I'm working with for context.
Re: How to delete a copy of a card
"Copies" are actually just the same card. You can see this if you edit the card on both dashboards the ID in the URL for the card will be the same so there isn't really an original and a copy. If you want to "delete" a "copied" card from a dashboard all you need to do is select Move/Copy and remove the dashboard from the list of dashboards displayed.
Re: Same period last year measure
Hi @Ab_Israni
When I'm doing comparisons for year over year for custom ranges what I do is restructure my data so that I have several different periods for each record based on the date. For example if you're looking at January 1st it'll have a current value of Jan 1 2026 and a Last Year period value of 2025. I've done a write up on this in the past where you can find here:
If you're concerned with rows you can pivot the resulting data so that you have a column for the current value and one for the last year value instead of having multiple rows.