During development or testing you often have to make small changes to views. Deploying an entire project just to make a small change to a view is a bit overkill. So often during changing views you also deploy them in the functionality - result screen. However, if there were triggers on the views these are dropped since the SF does a drop and create. Since it's not always clear which views are editable often the triggers are forgotten when manually deploying a view.
The SF already knows there are triggers existing on this view. Why not give a warning to let the user know that the triggers also need to be deployed, when triggers exist for the view?
Open
Give a warning when manually deploying a view if triggers exist
+5Why not just re-apply the instead of triggers as well? Hey, while at it, just deploy the whole package for the table (view) you have re-created
- create or alter view
- apply instead of triggers
- apply layout procedure
- apply default procedure
- apply context procedure
This way, even if you have added or removed a field, the rest of the application keeps working or gives a specific error (i.e. you removed a column that is being used in the default).
That would save some clicks, I would however like to be notified that additional objects were applied otherwise it can become very confusing.
+5Agreed.
+23Updated idea status New → Open
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.