DavidChurchman Coach

@ckwright, would know better than me, but I thought this would be true for the legend but not for the summary number. Not removing the legend of the card that you're clicking on makes some sense, because the legend can also be clicked on as an interactive filter, so it gives you another way to click/unclick the fields, and…

I thought they had turned the "last updated off" based on this post: But it seems like it's just been removed it from the main Workspaces page, but not on all the underlying objects within the workspace. So the problem has just been moved down a level. I have folders that say they were last updated 2 weeks ago, even though…

I don't think this is currently possible. I was trying to think of an approach that would achieve a similar effect, and the closest I got was using a variable to switch how the pie chart is broken down. Instead of Active/Non-Active, I used this sales dataset with 3 product categories. When the variable is set to all, then…

I've been reflecting on this, and I think I have a mixed reaction. On the one hand, I would love more customizability on the cards, but on the other hand, customization —> complexity —> barrier to entry. One of Domo's strengths is a low barrier to entry (not because of AI, but because of the core product), so I could see…

Okay, so it seems like your question is less about the MoM and YoY calculations and more about the filtering so it just shows the most recent month based on the user's filter. My first thought is that if you've already got the data structured with MoM and YoY calculated for each month, and you want the user to view one…

@GrantSmith is the king of this and has a great write-up I'll link to at bottom. His approach allows for a lot of flexibility in grain, etc, so might even be more complicated then what you need. The way I would approach this is to calculated the MoM and YoY and YtD for every month in the dataset in the ETL itself. So each…

Your date range of "Last 12 Months" will always be the last 12 months based on today's date, so selecting past years won't work. If you want users to always see 1 year of data, change "last 12 months" to "all time". Make your filter card single-select, and save a default filter on the App page for this year so it's always…

I don't think there's any way of getting that exact graph using standard cards, but you could get similar analysis. Assuming your data looks something like this: I would say the closest thing to an "out-of-the-box" card for this use case would be the variance line chart: With a little more work, you could get pretty close…

Agreed; I posted a question about this before, which got some agreement from other users that it should be possible: I also posted this on the initial Beta forum, and got agreement there, as well:

This would be incredibly helpful. You can jury-rig some "contains" filters using variables, but this would be so much cleaner.

It doesn't matter what you populate the variable with when you originally create the variable, because that will be overwritten with the dynamic values later. You populate the dynamic values by creating a slicer card that has those values, then on the App, you select the "action" for that slicer card, and instead of…

Congrats, Anh! I definitely appreciate your curiosity

Update: I looked again, and the "set variable" action now appears on all (most?) card types, not just the slicer. I tested it with the drop-down, and it worked. I tested it with a table, and it didn't, so not sure if that "set variable" action makes sense/should be on every card type, but I appreciate being on the…

No, no one figured it out.

This is GA. It's done through the actions in the Slicer card: https://www.domo.com/product/new-features/slicer-card-and-variable-linking

You could post these as ideas to the ideas exchange…

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,…

I checked again, and now I see sections in that app, too. Not sure if you changed something or if it just took a while for it to become available everywhere in my instance. Thanks for the new feature!

My understanding of the documentation is that it is only enabled for the Slicer card, not any other card type. I agree it would be nice to be able to do this with the dropdown. You should post that as an "idea" that folks can up-vote. For multiple values, currently variables can only take on a single value at a time.…

Not sure what might be causing that. Can you share some screenshots of before/after? Is it all of your charts or just certain charts? When I change the chart color palette, it does change the colors in my cards across my app:

Something I noticed is that links work in headers but not text cards. I think that probably stems back to text cards being the buggiest card in Domo

Another random annoyance: links in text cards don't work in PDF/PPT export, even in the new report builder.

When I first got on the Editable Tables Beta, I could not bring their associated datasets into Magic ETL. The workaround was to create a view of the dataset, and that view did work with Magic ETL. I recently tried again, and it does appear that I am able to use the Editable Table in MagicETL now, but I haven't tested it…

Yeah, an "action" on cards where you could set a variable value!

Yeah, it would be great to be able to add some filter cards to the left of the tabs.

In the BeastMode, when the value rounds to a whole number, it is passing that whole number (7) to the CONCAT with ".00" to get "7.00". The ETL is maintaining that decimal (7.0), probably because of how it deals with the 'float' data type, so it gets "7.0.00". For both, I might try a different approach to get to the nearest…

I made some progress on this. I added a form to the top of my App with the fields I wanted a user to be able to control. I created a view of the form responses with only the the most recent response, and then joined the data onto that response in the view, which effectively subsets the data for those form selections. Since…

Yes! The "Range Selector" is also super finicky when working with dates, so having a purpose built date range filter with a modern UI would be great.

In general, it would be nice to be able to tie the current scale markers to a field to enable highlighting any range of interest.