Sign Up ›
  • Rahul Sherikar 4
  • NEWBIE
  • 0 Points
  • Member since 2016
  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 2
    Replies
4 replies

Solution to move business logic from trigger to controller only in case of record inserted or updated from visual force page(UI) not for Data loader.

I have a Trigger and workflows on an object.

In trigger for every insert or update certain functionality happens. this functionality is added to trigger mainly because of Data loader(records inserted or updated from data loader).

The issue is, it is causing Too many SOQL for insert or update of records from VF page.

I'm using flag to determine if the insert happing from VF page or data loader, if it is from VF page then execute this functionality only at end of the transaction.

Is there any design or logic which can be used to execute this functionality only once and only at end of the transaction when coming from VF page?
 
4 replies

Solution to move business logic from trigger to controller only in case of record inserted or updated from visual force page(UI) not for Data loader.

I have a Trigger and workflows on an object.

In trigger for every insert or update certain functionality happens. this functionality is added to trigger mainly because of Data loader(records inserted or updated from data loader).

The issue is, it is causing Too many SOQL for insert or update of records from VF page.

I'm using flag to determine if the insert happing from VF page or data loader, if it is from VF page then execute this functionality only at end of the transaction.

Is there any design or logic which can be used to execute this functionality only once and only at end of the transaction when coming from VF page?