Skip to main content

My questions are:

1. Why is the wizard complaining about the parent and the child on screen 1?

2. Why is my rollup working in my dev org but in my sandbox I get "IO Exception: Read timed out"? Could it be the difference in the Salesforce release? Or the renamed Account object in the sandbox?

 

Here are the details:

 

Using the Wizard in preview Spring '24 sandbox, I chose the Account object (which was renamed in this org to "Organization" pre-me, don't ask!) to "Organization (Account)". When I try to save (on the first screen) it says the parent does not exist and the child does not exist. It hasn't asked me for the child yet.

 

When I try it without the wizard, I'm getting 

"Error:IO Exception: Read timed out"

 

So I next installed DLRS in my Winter '24 dev org. Wizard gives me the same message - parent doesn't exist and child doesn't exist. Account has not been renamed in this org. And I haven't had a chance to select a child yet. 

 

Without the wizard, I was able to save, deploy, and successfully calculate the rollup in my Winter '24 dev org with these values (it also contains this custom object and fields. I cut and pasted field API names in each org):

Parent Object: Account

Child Object: Food_Trip__c

Relationship Field: Food_Recipient__c

Field to Aggregate: Trip_Date__c

Field to Order by Trip_Date__c (do I need to specify this?)

Aggregate Operation: First

Aggregate Result Field: First_Completed_Delivery__c

Active

Realtime

User

 

Both orgs have DLRS v2.19

 

Thank you!

 

#DLRS Package #DLRS #Declarative Lookup Rollup Summaries @Stephane Plancke @Commons Project: DLRS

3 respostas
  1. 12 de jan. de 2024, 16:12

    @Dodi Friedenberg, very odd behavior. I don't know why the new wizard would be so different. "Read Timed Out" suggests a problem talking to the Salesforce API but both wizards talk to the same API endpoints, and I think using the same code.

     

    I think the most interesting is the parent does not exist error, like it is collecting the wrong value for the renamed object... BUT in your org that isn't renamed it does the same thing.

     

    I can't think of anything off the top of my head that tells us what is going on. Any other insight or tests that might surface more details?

0/9000