function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
pdopdo 

"Aggregate query has too many rows for direct assignment" Error

I read in some other posts that this may be a bug, but I did not see resolution.  Here is my code for my trigger and it works just fine in the Sandbox, but it does not work in production.  Can anyone help with this?

 

trigger PhysicianUpdateAccountContactCount on Contact (after delete, after insert, after undelete,
after update) {

// Declare the variables

public set<Id> AccountIDs = new Set<Id>();
public list<Account> AccountToUpdate = new List<Account>();

// Build the list of Accounts to update
if(Trigger.isInsert || Trigger.isUnDelete || Trigger.isUpdate){
    for(Contact c: Trigger.new){
    if(c.role__c == 'Physician')
    AccountIDs.add(c.accountid);
    }
}

if(Trigger.isDelete || Trigger.isUpdate){
    for(Contact c: Trigger.old){
    if(c.role__c == 'Physician')
    AccountIDs.add(c.accountid);
    }
}

// Update the Accounts

if(AccountIDs.size()>0){
for(Account a: [Select a.Id, a.Calc_Physicians__c,
(Select Id From Contacts where Role__c = 'Physician')
From Account a where Id in :AccountIDs])
AccountToUpdate.add(new Account(Id=a.Id, Calc_Physicians__c = a.Contacts.size()));
}
update AccountToUpdate;
}

 

dkadordkador

Aggregate queries have a maximum number of rows supported.  The reason this works in sandbox but not in production for you is likely because your data set is much larger in your production org than in your sandbox org.
pdopdo

Thanks dkador, only problem is even if I add more filtering, it will still error at 200, which is not the max.