Just want to be sure if we on the same page.
Am I not correct by stating that using slices in itself is not going to solve my problem. In my case I do not want to just reorder columns but REMOVE a few virtual or column with automated expressions from my form view of all the tables on my app. Using a slices from various tables achieves this if I link the form to it, I however want to show these columns in the higher related detail and table view levels.
I therefore cannot link the form and the related detail and table view to the same slice in this scenario where a columns need to be removed in a form but visible in other related views?
Am I correct in stating that I can only achieve this by either Aleksi’s work around, or combinations of slice (to reorder) and column showif (to exclude column in form view).
I believe that efficient data capturing (I.e. forms) is the most fundamental element of any good app and these are rather time consuming work arounds just to keep data capture efficient by having focused and well organised forms. Especially if you have a few tables.
It also defeats the purpose of
utilising system generated views and just making some changes as you see fit vs needing to create a whole “arsenal” of custom views, slices and actions that slow apps down just to keep an app organised.
It seems rather intuitive that form views need to have a column order option.
The exclusion of which would rather
be considered a bug compared to a feature request to include it! This is taking my above statements into consideration, every other view other than forms has this option and the amount of people requesting a column order option in forms.
Why do I get the feeling that most advanced apps with more than a handful of tables created by various users have really disorganised forms!
Care to comment on this one. I am sure you are quite busy…but your feedback would mean a lot…following the amount of appsheet users I have come across regarding their frustrations on theit request of column order in forms.