[SalesForce] Activate an InActive Trigger using the Force.com IDE

Trigger code :

trigger SetFieldsOnContact on Contact(before insert){
    System.debug('------------inside contact trigger SetFieldsOnContact before insert---------');
    String accId = [SELECT Id from Account WHERE Name='GenePoint'].Id;
        for(Contact c : Trigger.new){
        c.Description='This contact updated.';
        c.Title='Mr.';
        c.Phone='8888888888';
        c.Email='abc.def@gmail.com';            
        if(c.AccountId == null){
        c.AccountId = accId;
        }
        }
}

Execute Anonymous code :

List<Contact> contList = new List<Contact>();
for(Integer j=0;j<200;j++){
Contact c = new Contact();
c.FirstName = 'Trigger Contact'+j;
c.LastName = 'Trigger Contact'+j;
contList.add(c);
}
insert contList;

Issue : Fields on inserted contacts are not getting updated.

Best Answer

The trigger will need to be activated in order to run. You can do this from Developer -> Apex Triggers -> Edit next the name of your trigger. There is a checkbox called "isActive". Assure that this is checked.

You can also edit it with the Force.com IDE by modifying the metadata file for the given trigger. Change status from "InActive" to "Active".

<?xml version="1.0" encoding="UTF-8"?>
<ApexTrigger xmlns="http://xxxxxxxxxxxxx">
    <apiVersion>32.0</apiVersion>
    <status>Active</status>
</ApexTrigger>

Related Solutions

[SalesForce] Error: Compile Error: Illegal assignment from String to Boolean

Change

c.Volunteer__c = 'FALSE';
c.HOC__Minor_Wavier_on_File__c = 'FALSE';
c.HOC__Disabled_Person__c = 'FALSE';
c.HOC__Calculated_Birthdate__c = 'FALSE';
c.HOC__Confirmed_Organizer__c = 'FALSE';

c.Volunteer__c = false;
c.HOC__Minor_Wavier_on_File__c = false;
c.HOC__Disabled_Person__c = false;
c.HOC__Calculated_Birthdate__c = false;
c.HOC__Confirmed_Organizer__c = false;

[SalesForce] Update parent object on child object update/insert

The trigger appears to be using the wrong field, based on the field name (and observed patterns through the rest of the code). It should be "Vested_Org_User__c" instead of "Vested_Org_Id__c".

As near as I can tell, you want your code to look like this:

trigger ProgType on Opportunity (after insert, after update, after delete, after undelete) {
    Set<Id> contactIds = new Set<Id>();
    if(Trigger.new != null) {
        for(Opportunity record: Trigger.new) {
            if(record.RecordTypeId == '012...') {
                contactIds.add(record.Vested_Org_User__c);
            }
        }
    }
    if(Trigger.old != null) {
        for(Opportunity record: Trigger.old) {
            if(record.RecordTypeId == '012...') {
                contactIds.add(record.Vested_Org_User__c);
            }
        }
    }
    contactIds.remove(null);
    Map<Id, Set<String>> programs = new Map<Id, Set<String>>();
    for(Opportunity record: [SELECT Vested_Org_User__c, Program_Type__c FROM Opportunity WHERE Vested_Org_User__c in :contactIds]) {
        if(programs.containsKey(record.Vested_Org_User__c)) {
            programs.get(record.Vested_Org_User__c).add(record.Program_Type__c);
        } else {
            programs.put(record.Vested_Org_User__c, new Set<String> { record.Program_Type__c });
        }
    }
    Contact[] contacts = new Contact[0];
    for(Id contactId: contactIds) {
        contacts.add(new Contact(Id=contactId, All_Program_Types__c=programs.containsKey(contactId)?JSON.serialize(programs.get(contactId)):null));
    }
    update contacts;
}

Standard optimizations are done here:

Use Trigger.new and Trigger.old to make sure you don't miss any contacts.
Use Maps and Sets to reduce overall usage, especially versus nested for loops.
Don't use queries when they're not needed (no need to query the contacts, as you already have their ID values).
Sets automatically deduplicate, so no need to check if the value exists first.

Best Answer

Related Solutions

[SalesForce] Error: Compile Error: Illegal assignment from String to Boolean

[SalesForce] Update parent object on child object update/insert

Related Topic