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.
FYI, these same concerns apply to the Card View as well. In the Card View you are allowed to insert inline tables where images can be placed. The inline tables here suffer the same issues described above for Deck Views.
It would be very useful flexibility if the inline tables were fully supported!!
It’s been another 5 months now and I’ve avoided several instances where embedded Inline tables in Deck and/or Card views would have been a great fit. In fact, I recently implemented such a view thinking that some of these issues had been addressed.
I found out today, based on a message from the client that the column width problem is NOT addressed and now I have to scramble to find an alternative approach.
Could Appsheet please spend some time addressing the issues outlined above? The most prominent problems seem like they wouldn’t be too difficult to correct.
Column Widths not honored in data rows resulting in skewed columns