Jeffsnake 🟠

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.

thanks, I'll check these out.

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

Sweet! Just signed up. Doesn't sound like the initial rollout will include the ability for users to create/save their own filter combinations... but maybe we can convince them to add that in v2? ?

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

This would make the table card so much more functional... seems ridiculous that we can't do this. @Dani - Any chance you can throw your weight behind this one. This is something that we (and many other people) have been asking for a long time. I"ve had several conversations with product managers... but there just isn't…

You still can't lock columns... will this ever be implemented... seems ridiculous that this isn't doable. Jeffsnake

Oh man... that is perfect... but it doesn't show in our instance. I'll reach out to support to see if they can help with that. thanks, Jeff H.

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

Yes... we can accomplish what we need with the current setup. However, in situations where there might be 5 different people who need access to a record of data through 5 different columns on the dataset... that is 25 different policies. We already have dozens and dozens of datasets with tens of thousands of policies per…

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

At domopalooza... I was told by one of the project managers that there is a new card type called "pivot table" that will have added functionality... including freezing panes. He seemed to think it would be hitting beta in the next couple months. Jeff

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

Bump... this would be huge... and be a huge timesaver as we end up creating the same "final drill path card" over and over... come on guys, you know this would be awesome!

this is critical for us... we rely heavily on table cards... displaying the record number seems like it should be super easy... that way the user can sort the table by different columns, and have a "dynamic" rank using the record number.

Has there been any action take on this? having to delete and recreate the transform statements just because I want to insert an index transform at the beginning is a pretty big pain. Jeff

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…

Any update on this from Dev?... this would be really big for us. We rely on quick filters alot... and ofter there are many values in each quickfilter box... and it hurts the usability for our users having to scroll down through long lists before getting to the quick filter they need. Thanks, Jeff H.

Any movement on this?... this would be huge for us... we have a lot of users who use table cards (and sumo cards) extensively... and freezing the header row... and selected columns would significantly increase the value.

There are still not nearly enough color options... we need more colors and more gradients.

This is a huge issue... We do a lot of "not in" filtering... and when you do that, it not only excludes the records with the value you are tying to exclude, it also excludes records that have a NULL value in that field. As mentioned above, the workaround is to create a beast mode to replace the NULL value with an actual…

For me, the key is that you can't sort at all from a mobile device... most of our users on the sales side are using domo on their phone... not being able to sort is definitely an issue.

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…