Hello @nathan ,
Thank you for pointing me in the right direction.
The following pertains only to mobile view (on Android in my case). Looking back in my docs I recognize how Code “chooses” a certain display mode. There have been postings in the past with complaints as to how the ‘card view’ (by lack of a better word) renders the information almost useless, because if Code thinks a card view is best but you have text and number tables, there is no telling what these numbers mean, in particular if they are of similar magnitude. It also seems not very clear as to what you get to see (and where) in the cards. Playing around with column order sometimes helps, but then the the table view might not be the way you like it any more.
Since you say you’d love to allow more customization, I feel invited to come up with some suggestions.
But, and that’s why I started this thread in the first place, there is a bug in the table view, so let me start with that. It is for me an absolute killer of my application and, sorry to complain here, after almost 48 hours trying to get support to even acknowledge the issue, I will discuss the bug here and hope a (quick) solution can be found. This is something that worked until very recently.
I have pretty complex tables that show on mobile in card view. Sliding the cards, clicking on the cards (and the window version) work 100% as intended. For optimal use we need the table mode (on mobile), so we click on the little icon to table mode. And here is where things go wrong: my buttons that have a formula for the button label don’t work any more. My buttons have complicated instructions depending on the status of other fields and this label changing it’s wording is crucial. The workaround would be many more buttons, but that is not an options, since there is only so much screen real estate and I would need way to many buttons. But at this point, in table mode, these buttons with this specific functionality stay gray. Since they work in card mode and in windows, this can only be a (new) bug.
I hope you will be able to get someone to look at this in a hurry, because we have come to rely on this big time.
That said, about the customization, I have some suggestions:
- a canvas button function to change the card mode to table mode for a specific table. And a more obvious icon than the back arrow to return to card mode.
- a set of options at design time with each table to choose the default mode for the specific table. Right now, even though you can switch to table view, it becomes a full screen table and not inline, which is not always handy. So we need 3 default modes: a) card view, b) inline table view and c) full screen table view (edit: I realize this last one can’t work unless the table is the only thing on a page).
- allow us to choose which fields are show in card view (if there are more columns than can be placed) and per field/column allow for a label to show with the data, so you can distinguish something like: high score: 9 - average score: 7 - low score: 6, while someone’s name can show without a label, because it is obvious what it is.
- allow for some buttons to show in card view (rather than having to swipe)
- upon swiping, show only active buttons in the available space (which is only 2 buttons plus the ‘more’ button.
I can think of many more features, but this is a start. I had kind of accepted that cardview was the way it was, but this bug and your remark got me going again 
. However, getting this bug fixed is a good start for me.
Thanks in advance for your consideration!
Greetings,
Joost
…
…
.
… Sorry 
!