I would like to see a "template" structure for views. Use Case: Lets say I have I have a generic table like Vehicles. From that Vehicles table, I want to carve out certain datasets based on the type of vehicle, e.g. sedans, vans, and motorcycles, and create three slices to do so. Now I have to manage up to four unique sets of views, one for the table and one for each slice. I configure each Detail, Form, Inline etc. view individually which can be very time consuming. Alternatively I can copy the original Detail view once its done, and select a new slice and tweak a few options. This is a little quicker, but then I am left with unnecessary duplicate views e.g. "vehicle_sedan_Detail" and "vehicle_sedan_Detail2". At the same time, if I (or the client) wants something to look different, I now have to repeat that process for each change; manage each view individually or copy and reassign the table/slice. Idea: I assign a specific view as a "template", and assign that template to other views. This would copy the format of the "template" view onto the new view. Then the user could manage the specific details from there if needed. Using the Vehicle example, I would customize my Detail, Form and Inline views for the original Vehicle table and assign them as "templates". Then when I generate my new slices I could go to the "vehicle_sedan_Detail" slice view and select the table "vehicle_Detail" as the template. Rinse and repeat for Form and Inline and you're done. It would be awesome if that relationship stuck and any changes made to the original "template" view automatically propagated to all the assigned views, but that might need to come later. If anyone has any tips or tricks to address a plethora of views, I am all ears.
... View more