I liked the borders and the inner spacing and outer margins of the old version 
Viewing on mobile devices was impaired. They could at least consider fixing the first column and keeping the other columns slideable (as is done in the data grid)
1 Like
These two components are really great improvements. Some minor quibbles I would love to see fixed.
-
Column sorting is great but you should be able to select whether it is available for each column and also be able to specify what the column sorts by. Sometimes the data for the displayed value does not sort correctly. Once the user breaks the correct sort by clicking the toggle all they can do is toggle between ascending and descending versions of an incorrect sort. If you could turn off sorting for columns where the data won’t sort correctly that would help. Even better, be able designate a different column as the sort value.
-
In the data grid if the type is set to tag, even though there is a drop down arrow, clicking the arrow does nothing. You have to double click the item. Seems like one click in the arrow or item should display drop down.
The new table isn’t showing anything in the collapsible Data window in the Layout editor, but the new data grid does.
Also, when editing the value of a table column, the column order in the dropdown is surprising and I don’t know how it’s sorted - usually when browsing columns it would just be the same as order of the columns in the data table.
1 Like
In the previous version of the Data Grid, users could easily transfer data from external tables into Glide using the classic Ctrl+C and Ctrl+V method. It worked great with any number of rows and columns. The new version of the Data Grid only allows adding a value to a single cell, and this is a huge problem.
The previous version of the Data Grid is no longer available, and I am unable to assist users whose workflows have been disrupted, and they are suffering losses. Can you suggest any solutions?
2 Likes
Yes, we are keeping the older Data Grid for those same reasons. As I understand it, if you have a backup copy of your app or any app for that matter that still has the “older” Data Grid component in place, you should be able to copy that component and paste it into your app that is using the new version.
Once you remove the older Data Grid and replace it with the new one, I don’t think there is any other way to get back to the older version unless you still have the older Data Grid component present somewhere.
@Carbonsquare can you be more specific about what you mean by “scale better” on smaller screen sizes? Obviously any wide data representation will have scale issues on narrow screen devices – how would you like to see that handled?
Thanks!
Look back at the entry from aledesousa in this thread 8 days ago showing the visual comparisons of the Old Version Table to the New Version Table. That’s kind of what I mean by scaling on mobile phones. Also reference the comments from tobihaas and idevnva who mention mobile view of new tables compared to old and ability to Ctrl+C and Ctrl+V of the previous table versions. We use all of that.
We only have 6 columns in our table (but often with 700+ rows). On the desktop and mobile we can scroll down through this list super fast with a few swipes. The new table did not respond that way for us when we tested a rebuild.
The old table with it’s rounded edges also had a better visual appeal for us. Being able to select the entire table, copy it, paste it into Google Sheets, make changes and then paste “All” of that back into the table in our Glide app, updating multiple cells at once is an awesome feature on the old table. I thought we read a comment somewhere on here that this may not be possible with the new implementation.
Again, all of the new baked in features of the new version of the table make a lot of sense for many of your Glide users who do a lot of display with the Table component. For us, we simply use it as an alternative method of updating one column in our data so we don’t need all of that power. Hope that helps a little.
1 Like
I referred to this same post in one of my replies earlier in this thread. The old data grid feels a little better on mobile screens. For me is has slightly smaller fonts and slightly tighter cells, so it’s better for information density with less horizontal scrolling. Not a big difference, but noticable.
This post contains a screenshot from the builder.
This is how it looks on my phone.
3 Likes
Fix for this should be live on Monday.
4 Likes
To solve this, you could make the first column fixed and keep the other columns sliding (as is done in the data grid), when displayed on smaller screens.
1 Like
Thanks for your effort to solve all this @tristan .
A last issue that I just found:
Can New Table respect the orden of my values when the Tag/Choice type is selected?
By the default, the list is alphabetically sorted but it’s a headache when UX needs another thing (e.g.: a ranking).
Thanks for your help… saludos!
3 Likes
That would be great
Yes we are working on this.
1 Like
Hi All – loving the new Table and Data Grids, but is there a reason why title actions no longer show in a Data Grid when 0 rows are being displayed? This was possible in the previous Data Grid version, this was helpful in creating the first item in a list that will be displayed in the grid.
Now, an action button needs created above the grid to create a first line which takes up more vertical whitespace.
Thanks!
4 Likes
@mstam2 - This should be fixed in our next release. 
1 Like
Works great! One suggestion is to hide the column headers when there are not any rows to display, similar to the old Data Grid / Table. Here’s an example of how the current components display:
3 Likes
One other thing: rows in this Table seem to be changing their sort orders without any prompts at random intervals. The first line in this table “Transplant Surgery” moves down a few rows after a few seconds – over time, it moves back up and down again repetitively
I’m wondering, the Data Grid component. The row index. Would it have been better if the index doesn’t reset every time the user goes to the next page?
Currently the maximum index is the page-size. so if we have page-size 20 and 50 rows of data
it would go
1-20
1-20
1-10
it would be nice if the index showed the row count of the query or relation rather than the index of the current page only
and the 1-50 would be numbered 1-50
or have I missed other advantages of having it show just the page-size index
2 Likes
@mstam2 @abdo - Great suggestions!
Could you please take these to Feature Requests as new threads? We’re setting up an automation to get posts from that category in front of our development team. 
2 Likes