Skip to main content

#Delete Field Dlrs LookupRollupSummary0 diskutieren mit

Hi team,

 

I am using Nonprofit Cloud and I have installed DLRS Package.

I created Lookup Rollup Summaries between Account and Benefit Disbursement, While deploying the child triggers I am getting this error.

 

Please refer to the attached Screenshots.

 

Could you please help me identify the source of this issue? I’m trying to determine whether it's related to Non-Profit Cloud or the DLRS package. Additionally, I’m unable to delete this auto-generated class and trigger.

 

Unable to deploy child triggers

 

Screenshot 2024-11-06 at 1.51.22 PM.png

 

Screenshot 2024-11-06 at 1.51.36 PM.png

5 Antworten
  1. 8. Nov. 2024, 16:17

    Looking at the bottom of the rollup configuration you should see an "Advanced" header and inside of there "Test Code (Child Object)" which would be the method body that should be executed when testing the added trigger. This text will be merged into the generated test class and once added should be visible on the "Manage Child Trigger" page.

0/9000

Hi All,

 

There are two checkboxes ( Renewal check ) . One on Contact & Asset. I am using DLRS to have them in pair. 

(1) When Renewal check =True on Asset ---> at it`s related contact record (Renewal check) = True. Configured DLRS & it works fine. 

(2) When Renewal check updated on contact ---> It should update on its related Asset. Created new lookup field on Contact object to asset & tried to configured it but it is not working. Not getting any error. 

 

Any Idea what is missing or is it possible to update from Contact to asset from DLRS ?

 

Update check box from Contact to it`s Asset via DLRS

#DLRS Field

#Delete Field Dlrs LookupRollupSummary

1 Antwort
  1. 24. Aug. 2023, 07:00

    I don't think that DLRS is the best fit for your requirement. Have you tried to use flows for this automation? One Flow that triggers on Asset and updates all related Contacts and another that triggers on Contact and updates the related Asset (and maybe also all other Contacts that are related to the same Asset)

0/9000

Hello Team,

As I am receiving system emails regarding the rollup summary job fails

So I have deactivated the roll up summary job by unchecking active checkbox on the custom meta data record. But Still the job is being run and receiving the job failure emails continuously.

1. How to stop the specific roll up summary job  ?

2. If we delete the DLRS configue record then related child trigger gets deleted      automatically ?

 

#DLRS SOQL #Delete Field Dlrs LookupRollupSummary #DLRS Field

 

Thanks,

Pavan Thammali.

3 Antworten
  1. 3. März 2023, 11:14

    @Pavan Thammali, Can you share a screenshot of the error message? Usually, we deactivate unwanted rollups on the rollup itself but it can be done via metadata as well. However, the schedule should get deleted manually if the rollup has been scheduled. Delete the entry manually if the rollup is referenced in the so-called 'Lookup Rollup Calculate Jobs' tab. Child triggers should get removed via the 'Manage Child Triggers' button on the next screen by clicking remove.

0/9000

Hi All,

I am looking to delete field dlrs__LookupRollupSummary__c on the Custom Object dlrs__LookupRollupSummaryScheduleItems__c as per the DLRS optimizer instructions. But I am not given an option to Delete when I lookup the field from setup.

Anyone got any ideas how I do this? The github says just to delete it but not sure from where.

5 Kommentare
  1. 29. Aug. 2022, 19:22

    https://github.com/SFDO-Community/declarative-lookup-rollup-summaries/wiki/Attention:-Need-to-delete-unused-field-on-dlrs__LookupRollupSummaryScheduleItems__c

    What do I do? 

    • Run a report or create list view on the Lookup Rollup Summary Schedule Items object that filters for records that do not contain a value in the Lookup Rollup Summary 2 field. If you have records like this its possible they are very old, since this field has been being populated since v1.15 and beyond. If you want you can delete these records and re-run a full calculate for the associated Rollups.
    • Next you need to go to the Object Manager in Setup and find the Lookup Rollup Summary Schedule Items object. Locate the field Lookup Rollup Summary (its a Master-Detail) with the API name dlrs__LookupRollupSummary__c.
    • Delete this field and don't worry about accidentally deleting others the platform will block this. This will not effect any other data in your org as it is was purely used for the operation of the tool in prior releases and is now no longer needed.

    Note: If you do not see the Delete option for the above field - try switching to Salesforce Classic UI mode.

0/9000

I wanted to abort the current full calculate so that I could adjust it with a filter (less records)   I aborted the only apex running job I could find.. Still getting this error when trying to edit the filter parent object Contact records to update using WHERE clause #Declarative Lookup Rollup Summaries #Apex #Delete Field Dlrs LookupRollupSummary Error:A calculate job for rollup 'First Gift Date (Contact)' is already executing. If you suspect it is not aleady running try clearing the applicable record from the Lookup Rollup Calculate Jobs tab and try again.

6 Antworten
  1. 13. Juli 2022, 06:37

    Assuming there are no jobs currently running (which you can check in Setup -> Apex Jobs), go to the Lookup Rollup Calculate Jobs tab and delete all records in that object. Then try running a full calculate again.

0/9000

This issue has been going on since 9/9 out of nowhere. Audit trail doesn't show any changes. I ran a debug log and have some logs to show what's happening.

 

#DLRS  #Delete Field Dlrs LookupRollupSummary  #Apex Trigger

 

Is it possible I've reached a data capacity limit on dlrs?

 

Thanks

1 Antwort
  1. 16. Sept. 2021, 05:43

    Hi Collin,

     

    I have an experience of using DLRS. What I can think of in your case is that there might a an automation or related update that might be causing this.

    As per my knowledge DLRS creates triggers the run when a record is created/updated. 

     

    Your Records might be getting updated from some place.

     

    Thanks

0/9000