[SalesForce] Trigger – update Case field based on FeedItem

Apex newbie quest continues.

When new Chatter comment is added to Case, custom field on Case should be populated with information from latest Chatter comment.

Currently I have developed a 'before update' trigger on Case. It works quite well and suits my requirements, however works only when a Case is updated (doh). Now I want to make this solution a bit more "good-looking" and create "after insert" trigger on FeedItem object.

So far I have managed to identify that FeedItem is related to Case using parentId field (using code mentioned here as a sample – http://www.salesforcefast.com/2012/02/get-object-name-from-record-id.html).

However, I don`t know how to update information on Case from FeedItem trigger knowing only Case id (which is FeedItem parentId). Can anyone point me to the right direction? Thanks.

Best Answer

I suggest code like this:

trigger MyTrigger on FeedItem (after insert) {
    List<Case> updates = new List<Case>();
    for (FeedItem fi : Trigger.new) {
        if (fi.ParentId.getSObjectType() == Case.SObjectType) {
            updates.add(new Case(
                    Id = fi.ParentId,
                    ??? = fi.???
                    ));
        }
    }
    update updates;
}

It checks that the FeedItem is related to a Case and uses the update pattern that does not involve a query.

Related Solutions

[SalesForce] Migrating FeedComments and FeedItems

What do you mean by the FeedComment object is not accessible. You should be able to access it.

In an execute anonymous window try this

 list<FeedComment> fComments = [Select Id, FeedItemId, CommentType, CommentBody From FeedComment limit 25];
 system.debug(fComments);

What results do you get.

You should be able to extract the feedComment objects and reparent them in the same way that you have described above. Where exactly are you hitting an error?

[SalesForce] Detecting Trigger -> Workflow -> Trigger

Here is my attempt at solving this problem - adapted from my code here.

public class MyObjectServices {
    public static Set<Id> recordsProcessed = new Set<Id>();
    public static Map<Id, MyObject__c> cachedObjects();     

    public static void myTriggerMethod(Map<Id, MyObject__c> oldMap, Map<Id, MyObject__c> newMap){
        Boolean isFirstRun = true;

        //The number of records processed in all "batches" to this point
        Integer sizeBefore = recordsProcessed.size();

        //Add the ids all records being processed this "batch". If they've already
        //been processed, the set will prevent duplicates from being added
        recordsProcessed.addAll(newMap.keySet());

        //Determines if the records included in the current "batch" of 200 
        //have been processed before
        if (recordsProcessed.size() == sizeBefore){
            isFirstRun = false;
            //Removes them from the set so they can be re-processed in the same transaction
            recordsProcessed.removeAll(newMap.keySet());

        } else {
            cachedObjects = newMap;
        }
    }
}

After evaluating this logic, if you are in a first run, isFirstRun will be true and you will use the oldMap and newMap as before. If you are evaluating this code after a workflow, isFirstRun will be false, and the cachedObjects will be the versions of the objects before workflow.

Now, after the workflow run, the ids will be removed from the map, allowing subsequent updates on the same records to interact as usual. The only shortcoming I see is that this will not work if the trigger itself calls an update on the same records (which is enforced by Apex but workarounds exist).

Best Answer

Related Solutions

[SalesForce] Migrating FeedComments and FeedItems

[SalesForce] Detecting Trigger -> Workflow -> Trigger

Related Topic