Does anyone know if there has been any movement on this... the ability to have color rules applied to subtotal and total rows...

@MarkSnodgrass - Yep, someone just turned me on to that... and it looks like it has what I need. thanks!

I think it would have, but I had so many dates/comparisons, I would have had to branch like 25 times in the ETL... so I ended up going back to the source (SQL Server) and did the date comparisons in SQL. thanks, Jeff H.

Interesting... I hadn't thought of that technique... I'll give that a try and see how it works. thanks, Jeff H.

@guitarhero23 - When we provide table cards like this to our users, it usually comes along with many quick filters. So they may start at seeing 10,000 rows... then using quickfilters, they narrow it down to a smaller popoulation. Then they might just poke around there in domo, or they might export for analysis outside of…

I agree that, ideally, the purpose of domo (and the BI group in our organization) is to do the heavily lifting of the data analysis/aggreation/etc. in Domo and present easier to digest results to the user. The vast majority of the time, that is exactly what we do. However, for us (sales organization with a heavily…

@Ashleigh - We want to display static multiple cards on a single large screen. Using Embed is our next thing to try... but we haven't purchased it yet, and I was trying to make it work without it for now. Everything works great, except for the fact that it auto logs off overnight so I have to manually log it back in every…

Hmmm... that is interesting. But I imagine that the meat of the app is just handling the display to the monitor... which we can already do with just a browser... but if a user has to be logged into domo, I assume we would run into the same "forced log-off" situation with the apple app. We want the dashboard/page to be open…

that sounds cool... I'll take a look.

Yeah, I thought about doing a beast mode to define the date ranges... but there are too many overlapping ranges they would need to be able to choose from... so that wouldn't work. thanks for your help on this!

I thought I had done that... but was wrong :-(... that made it so the data returned is accurate... thanks! Now for the trickier parts... and I don't think there is a current way to handle these (based on dojo searches)... but I'll run them by you to get your thoughts. 1. I made the data card "all time" as discussed above…

the page level date range selector is almost unusable until you guys can allow us to select defaults... just too clunky for me to give to our execs. Dani - Any movement on this? thanks, Jeffsnake

Unfortunately... using text wrap doesn't work because that wraps the actual data as well, and makes some of the fields (especially date fields) much harder to read. And manually setting the width doesn't really work either because the card has so many columns... and most of them vary in widths depending on the record...…

Has Domo made any statements around this?... this is a huge issue for us. We rely heavily on table cards for our users... and not being able to view all the records in a table card is a huge problem. Telling them they have to export the records to view them completely defeats the purpose of Domo and doesn't do any good on…

jhl - I like this idea... I'm pretty sure you are correct about not being able to do this natively in a card using only filters and beastmode. You basically took my idea about using a workflow to roll up by month before hand and improved upon it. Rolling up by day and then using a left join from a "seed" dataset that…