Hi!
when I create a new field, the default behavior is to add it to all existing views. many times I don’t want that to happen since the field is a field that no one needs to see. the problem is that if I have 50 Users each with 20 own Private views, its nearly impossible to get the new field out of all the views.
to overcome it we used in the past to create the service field toward the end of the record, but I wonder if there is a way to either not add new fields to existing views by default, or at least have an option to control it?
First of all: welcome to our community! We’re happy to have you.
Totally understood your described case - that can be cumbersome in such situations. We noted your feature request and will discuss it in our next product team meeting in a couple of days.
Just wanted to give this a bump as I am out of votes, but this would be a huge help in apps that have a lot of views. Perhaps this could even be a temporary flag when adding a new field to let the user decide?
@andrew.cranston@roman@1F2Ns I have just included it in the mockups of the field setting for the new record so that the feature is developed with it. I absolutely see the use case and the need for it.
