I am using SQL Server for my database. I understand that right now there is no way other than creating a slice to manipulate column order in a form view. Before I go and create slices for my many key tables with this sole purpose, I would like to understand 3 things:
Is this a fundamental limitation that cannot / will not ever be overcome within the platform? I have to guess that it is or it would seem to me that it would have been addressed long ago…
What are the performance implications both within the editor and within my app of creating many, many slices? Based on prior exchanges with @praveen I understand that my app is way outside the typical bounds in terms of table count. I know it probably should/could be broken into “applets” to address this fact, but assuming I don’t do that is creating tens of slices going to negatively impact performance?
If the answer to #2 is “Yes you numbskull, performance will likely degrade with lots and lots of slices!” then would creating Views in SQL be a better alternative, and what unforeseen challenges might that then present?
I welcome any and all wisdom the community can provide on this matter.