Card views with nested inline tables prevent users swiping/scrolling down

[Jonathon]

Problem 1: Nested inline tables take up the same space, whether they have 0 rows or 1000 rows

---

Problem 2: When mobile users swipe down through card records, they inadvertently swipe on the nested tables causing them to scroll instead.

---

Problem 3: Users can scroll down, hiding records in a really unintuitive way:

---

This has been standard behavior for a while, perhaps to accommodate the variable size that nested inline views can occupy? In any case, the current implementation is mostly unusable save for very niche scenarios.

Soution?: We should be able to specify how many rows we want to display here, similar to detail UX views. Ideally, the container would be flexible to some threshold upon it would default to the existing scrollable behavior. Currently this is 4 rows of data without column headers or groupings…

[Steve]

Attn @Arthur_Rallu

[aforrester]

[WillowMobileSys]

Just like to add that I believe Deck Views suffer the same issues and I suspect it may be the same source code responsible for these deficiencies which is why I raise it here. Nested Tables are supposed to be explicitly supported in Deck Views. There have been several bugs opened concerning the Deck View issues before Card Views were available.

AFTER Card Views were rolled out, I also opened a support email to draw attention to these same issues citing the Deck View bugs as well. I’ve attached them below for reference - do not know if all are still an issue.

It would be nice to get these issues addressed as they can be extremely useful for a number of user experiences!!!

---

Some other posted Feature Requests and Bugs

Deck & Card view with Nested table column - Bug summary Questions

Since about 1.5 years there have been reported several bugs about Deck View with Nested table column. I want to summarize them here. AppSheet Team: Please tell us frankly, if you will fix them, or if we should avoid using Nested table column. Adding @morgan @praveen @Aleksi @JCadence Not working in Dashboard Not able to set the number of Max. nested rows Table view no consistent column widths Clicking on a Child row will open the Parent Large white space gap…

Deck View - nested tables do not retain consistent column widths from row to row in the table Questions

The column widths are not consistent from row to row in a Deck View embedded table creating a very difficult to read table view [25%20AM]

New Bug Encountered: Deck View - Nested Tables have large gaps and will list beyond view Questions

I like the concept of nested tables in a Deck View. But there are a few issues that keep me from using them related to the Deck View fixed height when the Nested Tables are added. When a table has only a few lines there is a large gap left between one Deck View item and the next - due to a fixed height. This gap should be dynamic up to any size limiting factor meaning it should dynamically reduce the white space gap between Deck View items until it reaches the maximum Deck View item height. …

New Bug Encountered: Deck with Nested table column view not consistent Questions

Good afternoon, It won’t be a big bug, but when we put the nested table in a deck view, it looks like this: [chrome_2019-11-09_16-17-46] With misaligned values relative to headers. If we click and open the relative view, it looks fine: [chrome_2019-11-09_16-18-31]

New Bug Encountered: Deck View's Nested Table Column Not Displaying in Dashboards Questions

I’m not sure if this is a bug or just a limitation of Deck Views. The Nested Table Column for the Deck displays as expected in a standard view, [15%20AM] …but is missing from that same view when it’s part of a Dashboard. [04%20AM]