Best Of
Re: Card Limitations
I can see the dashboard now. I believe after attempting - you understand my point. You can do the line chart in Domo as shown in the mock-up. But the rest, as simple as it looks, can't be replicated. I have experience with other systems and tools. That mock-up shouldn't be a problem to replicate.
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.
