How to Delete Triggers from Production Org

We can delete unnecessary triggers in Production by using the eclipse IDE:

Step 1: Assuming you have a sandbox environment synchronized with your Prod org, you will first want to inactivate the trigger in sandbox. You can refresh your IDE project to consume these changes

Step 2:  In the Sandbox org, you will then want to run all tests: Navigate to Setup-->Develop-->Apex Classes and click "Run All Tests". This will run all of the tests in the sandbox org. This is an important step to validate whether or not the inactive trigger has impacted any asserts within your test methods. Assuming this behavioral change has impacted your tests, you will need to update your asserts to reflect this.

Step 3: Once all tests are passing, you can now deploy these changes to your production environment. You can use the Deploy to Server wizard in the IDE. Simply select the tests that you have modified, as well as the inactive trigger, and deploy these changes to your production environment.

Step 4:  Validate the trigger is now inactive in your production environment.

Deleting the trigger (if necessary - an inactive trigger will not fire and therefore can be considered as "soft deleted")

Step 5:  Create a new IDE project against your Active production org.

Step 6:  Right click on the specified trigger and select delete. Accept the option to delete from server. Since the trigger is inactive, it can now be deleted from the production environment.

Comments

Track Field History for more than 20 fields - Salesforce

All of us would have come across a situation when we need to track more than 20 fields for an object in salesforce. We have raised this Idea around 8 years ago in the success community. But sill it has't implemented by salesforce. But for now, we can achieve it partially with the following workaround. Approach: This approach uses a custom Text field which stores values of multiple other individual fields. Then enabling field history tracking of this field would allow you to track changes for multiple sets of other individual fields. Thus even though remaining within the count limit 20, yet track changes of more than 20 fields. Let us in this example take “Account ” object and apply the steps to track change in Account Name, Phone, Parent Account and Billing Address all together. Steps: Step 1: Add a new custom field. Setup -> Customize -> Accounts -> Fields Create a new Text (255) field “ Track FieldHistory ” (Or give any other n...

Customize the columns in the Items to Approve section on home page

We can customize the items to approve section with the help of custom visualforce page. All you need to do is create the below page with your object and respected fields to be displayed and then add the page to a new home page component. Page: <apex:page controller="itemstoApprovecontroller" sidebar="false" showHeader="false"> <apex:form > <apex:pageBlock title="Incidents/Service Request To Approve"> <apex:pageBlockTable value="{!items_to_approve}" var="item_to_approve"> <apex:column headerValue="Action" width="160 px" > <apex:commandLink target="_top" value="Reassign |" action="{!REASSIGNnavigation}" style="text-decoration:none;color: #015ba7;" styleClass="cactionLink"> ...

Kanban view for Lightning

Tired of list views? Looking for a dynamic views to show your cases or opportunities in all new way? Here we go, Salesforce introduced Kanban views for us to have better visibility of our cases/opportunities and their journey from opening to closure. A case kanban allows you to visually summarize all of the cases for your agents, by status or priority. It's not only a board, but also a drag and drop tool that will help agents keep their cases moving towards resolution. Similarly an opportunity Kanban display opportunities from a particular sales path Let's take a closer look at what all we can do with Kanban Track a Deal with Path Display opportunities by Sales path Move an Opportunity to the Next Stage Take Action on Your Records

The Fundamentals Of Salesforce.com

Search This Blog