Exeception on After Insert, Record is read only

Question

I'm writing a trigger for new opportunity products to populate a field Product_Category__c (on opportunity lineitem) getting the value from Product_Category_new__c (on Product).

This is my trigger:

trigger SetProductCategory on OpportunityLineItem (after insert) {

    for (OpportunityLineItem opplineitem: Trigger.new) {           
        opplineitem.Product_Category__c =  opplineitem.PricebookEntry.Product2.Product_Category_new__c;
    }     
}

I get this error message:

execution of AfterInsert caused by: System.FinalException: Record is read-only

I have tried with before insert;in this case there aren't errors but the value Product category it's not saved on Opportunity Line item.

I have found that:

In a after insert trigger is not allowed change field using trigger.new

Please can you suggest a solution for this? i would like to copy the value Product category (Product) on Product Category (Opportunity Product) after the insert of the new opportunity products.

Thanks in advantage for any advice.

Br

Answer 1

The record is locked because you are catching the record after the insert DML statement has happened. So if you'd like to modify this record (or records), you will need to query anew, modify, then execute another DML statement.

Here is an example of how you could modify your trigger to work:

trigger SetProductCategory on OpportunityLineItem (after insert) {

    List<OpportunityLineItem> olis = [SELECT Id, PricebookEntry.Product2.Product_Category_new__c FROM OpportunityLineItem WHERE Id IN: Trigger.newMap.keySet()];

    for (OpportunityLineItem opplineitem: olis){
        opplineitem.Product_Category__c= opplineitem.PricebookEntry.Product2.Product_Category_new__c;
    }

    update olis;

}

And of course, since it's a trigger, we want to be sure to work in batches -- that's why I'm updating a list of olis rather than an individual opp line item.

Answer 2

I know this issue is pretty old, but today I stumbled over an alternative solution by accident. As an apex developer for years, I'm avoiding database calls whenever I can, to save the Limits, so this solution might help someone to overcome data related limit exceptions.

Alternative Solution:

The records can be re-initialized as mutable objects, by serializing and deserializing the list. It runs about twice as fast as a database query, doesn't affect the query and row limits, but consumes more heap.

List<Account> accounts = (List<Account>) 
    JSON.deserialize(JSON.serialize(Trigger.new), List<Account>.class);

After some testing I came up with some details about the heap:

• Deserialized records consum 1/4 more of the heap (don't ask me why, debugging displays two equivalent lists).
• It also needs a lot of heap during processing (that is released after deserializing).
• I was able to run it for about 18.000 records with selecting no more fields than their Id, before reaching the heap limit during the serializing process.