Andy in the Cloud

From BBC Basic to Force.com and beyond…

About

I started this blog to share some thoughts, ideas and opinions around my main passion in life computing, or more specifically these days Cloud computing. Who knows maybe I’ll go stray now and again into some of my others as well! I am currently working for Salesforce.com in Product Management for the Platform. Previously FinancialForce.com CTO.

Any views expressed on this blog are entirely my own.

Please find me on Twitter @andyinthecloud or post a comment on a specific blog post.

IMPORTANT NOTE: Declarative Lookup Rollup Summary (DLRS) Tool:

This tool is open source and is supported by the community in a volunteer capacity.  Kindly please post your questions to the Trailblazer Community Group. Thank you!

318 thoughts on “About”

Leave a comment

  1. Theodore Hoxie
    August 13, 2020 at 11:56 am

    Salesforce is doing a Critical Update for Winter 21 Release:

    We want to take this opportunity to remind you that we are enforcing the ‘Restrict Access to @AuraEnabled Apex Methods for Guest and Portal Users’ and the ‘Restrict Access to @AuraEnabled Apex Methods for Authenticated Users Based on User Profile’ Release Updates in the Winter ‘21 release.

    Does your installed package have @Auraenabled Classes that i would need to add to profiles?

  2. Sheetal
    September 2, 2020 at 4:33 am

    Hello Andrew,

    I am having an issue with DLRS. I posted on the community chatter group but I did not receive any responses yet. The issue is as under. Can you please help. Thanks a lot.

    I created a Roll up summary to count the number of contact roles on an Opportunity using DLRS. [Parent: Opportunity, Child: OpportunityContactrole, Relationship field: OpportunityId, FieldtoAggtregate: ID]

    I selected the calculation more as scheduled and it calculated the values correctly.But now when I add a new contact role to opportunity it gives me the following error

    dlrs_OpportunityContactRoleTrigger : dlrs_OpportunityContactRoleTrigger: execution of AfterInsert caused by: System.QueryException: Grouped field should not be aggregated: OpportunityId Class.dlrs.LREngine.QueryExecutor.query: line 662, column 1 Class.dlrs.LREngine.WithSharingQueryExecutor.query: line 671, column 1 Class.dlrs.LREngine.rollUp: line 238, column 1 Class.dlrs.LREngine.rollUp: line 117, column 1 Class.dlrs.RollupService.updateMasterRollupsTrigger: line 1035, column 1 Class.dlrs.RollupService.handleRollups: line 919, column 1 Class.dlrs.RollupService.triggerHandler: line 311, column 1 Trigger.dlrs_OpportunityContactRoleTrigger: line 7, column 1

    • Andrew Fawcett
      December 31, 2020 at 9:15 pm

      It should not be running the query realtime for Schedule mode – have you perhaps got another rollup definition lurking somewhere else?

  3. Ani
    September 3, 2020 at 9:00 pm

    Hi Andrew,

    Many thanks for this tool (though in all honesty, thanks is too small a word to describe my gratitude).
    I recently modified the relationship criteria of an existing rollup to add an OR condition.
    When I run a full calculate on this revised rollup the batch completes successfully, but doesn’t pickup any records, so its like a false positive.
    Can you please advise why this could be happening

    Regards

    • Andrew Fawcett
      December 31, 2020 at 9:11 pm

      For full calculate you need to put your criteria in on the screen when you press the button. The criteria on the rollup definition is not used for full schedule rollups.

  4. JR
    September 17, 2020 at 8:58 am

    I created some DLRS while I was in Classic, but I can’t see or edit them in Lightning. Do I need to delete them and re-create them in Lightning?

    • Andrew Fawcett
      December 31, 2020 at 9:08 pm

      No they will exist – the Lightning App however does not by default show the “Declarative Rollup Summary” tab – you will need to add this to your profile or a permission set assigned to your user. Then search for the tab in the laucher or add the tab to the rollup app.

  5. Judith Mandile
    October 7, 2020 at 7:24 am

    Hi Andrew,
    We have created many DLRS fields to update data for lookup relationships. These are defined as real-time. However when the “child” record is created or edited the fields on the “parent” object are not consistently updated. Any insight you can provide would be greatly appreciated since the data is critical to the proper flow of a major upgrade to out current applications.

    • Andrew Fawcett
      December 31, 2020 at 8:58 pm

      Rollups are calculated on insert and delete of a child record – when updating a child – only field changes to fields referenced on the rollup definition are monitored. Check “Relationship Fields” field.

  6. Pingback: Awesome Salesforce – Massive Collection of Resources – You Ever Wondered To Get – Learn Practice & Share

  7. Sirish M
    October 26, 2020 at 10:31 pm

    Hello Andrew, Salesforce has released new updates which impact the existing components of managed packages. As c3HealthcareRX is using Declarative Lookup Rollup Summaries Tool which is a managed package, there may be impact on the components used. Please could you confirm is there any impact on functionality if we activate the critical updates ?
    https://releasenotes.docs.salesforce.com/en-us/winter21/release-notes/rn_lc_secure_static_resources_update.htm
    https://releasenotes.docs.salesforce.com/en-us/summer20/release-notes/rn_forcecom_flow_mgmnt_access_legacy_actions_cruc.htm
    https://releasenotes.docs.salesforce.com/en-us/winter21/release-notes/rn_lc_apex_methods_packages_cruc.htm
    https://releasenotes.docs.salesforce.com/en-us/winter20/release-notes/rn_lc_enforce_prop_modifiers_cruc.htm

  8. Maxwell Hampton
    November 9, 2020 at 8:05 am

    Hi Andrew. We have been using DLRS for a while now and it’s been working fantastically. Until a week or so ago. I have recently had to edit all of our US and Canada State/Country Integration values. Previously they were, for example, United States. I recently changed them to match ISO coding, i.e US.

    Since making these changes, some records are not able to be saved, giving me error messages such as: “There’s a problem with this country, even though it may appear correct. Please select a country from the list of valid countries.”
    Or
    Mismatched integration value and ISO code for field

    After chatting with the Salesforce Support team, and doing some of my own digging, it seems that the DLRS_AccountTrigger, ContactTrigger, and Opportunity Trigger apex triggers are causing the problem. Disabling them in my sandbox solves the issue.

    I’m wondering, why would those DLRS triggers be interfering with my state/country integration values? Have you come across this? And if so, is there a workaround?

    Thanks so much.

    Max

    • Andrew Fawcett
      December 31, 2020 at 8:53 pm

      My guess is it could be one of the rollup rules is rolling up a field with an old country picklist value in it maybe? Go through your rollup rules for these objects and see if thats the case. And if you have any old records with picklist values that are no longer valid. And also does it still fail for brand new records?

  9. Judith Mandile
    November 9, 2020 at 10:09 am

    Hello Andy,

    I’m hoping you can help with an issue that SF Support is troubleshooting for us at Guiding Eyes for the Blind. The issue has been sent to tier 3 and they have sent this request –

    The error that is thrown in the flow in coming from the apex classes that are part of the managed package.

    The managed package: ” Declarative Lookup Rollup Summaries Tool (Managed)”.

    If you are not the vendor of the managed package please get written consent from the vendor the managed package to enable the debug logs in order to find out the point of the error.

    Are you the correct person to give this permission or can you tell me who is. Thanks in advance for your help.

    Judi

    • Andrew Fawcett
      December 31, 2020 at 8:50 pm

      I am a key originating author of this tool yes. However it is reallly supported by a great community and when i can myself. Please check out the readme file in the tools github repo for a link to the chatter community group.

  10. krishna
    January 12, 2021 at 2:45 pm

    I am trying to schedule DLRS apex job Rollup summaries and keep getting the error “Error: You must select an Apex class that has a parameterless constructor” I have not deleted the old schedule that is under an Admin ID. please advise.

    • Andrew Fawcett
      February 6, 2021 at 11:56 am

      You have to use the Schedule button on your rollup definition if this is a full recalc you want. The other way is the incremental reschedule path. Check out the wiki on the repo for a great article that covers the differences.

  11. Twan
    February 17, 2021 at 2:39 am

    Issue: When changing the status of any opportunity everyone gets an error:

    Error:Apex trigger dlrs_OpportunityTrigger caused an unexpected exception, contact your administrator: dlrs_OpportunityTrigger: execution of AfterUpdate caused by: System.QueryException: Non-selective query against large object type (more than 200000 rows). Consider an indexed filter or contact salesforce.com about custom indexing. Even if a field is indexed a filter might still not be selective when: 1. The filter value includes null (for instance binding with a list that contains null) 2. Data skew exists whereby the number of matching rows is very large (for instance, filtering for a particular foreign key value that occurs many times): Class.dlrs.LREngine.rollUp: line 210, column 1

    ============
    Debug logs analysis shows that the error is occuring due to a non selective query from the Managed package code:

    11:13:55.1 (320966640)|ENTERING_MANAGED_PKG|dlrs
    11:13:55.1 (322368972)|SOQL_EXECUTE_BEGIN|[210]|Aggregations:0|SELECT CampaignId, Sum(Marge_2016__c) lre0 FROM Opportunity WHERE CampaignId in :masterIds AND IsWon = true GROUP BY CampaignId
    11:13:58.55 (3055899789)|METHOD_EXIT|[7]|01p24000007K7Dz|dlrs.RollupService.triggerHandler()
    11:13:58.55 (3056161207)|FATAL_ERROR|System.QueryException: Non-selective query against large object type (more than 200000 rows). Consider an indexed filter or contact salesforce.com about custom indexing.
    Even if a field is indexed a filter might still not be selective when:
    1. The filter value includes null (for instance binding with a list that contains null)
    2. Data skew exists whereby the number of matching rows is very large (for instance, filtering for a particular foreign key value that occurs many times)

    Class.dlrs.LREngine.rollUp: line 210, column 1
    Class.dlrs.LREngine.rollUp: line 105, column 1
    Class.dlrs.RollupService.updateMasterRollupsTrigger: line 580, column 1
    Class.dlrs.RollupService.triggerHandler: line 318, column 1
    Trigger.dlrs_OpportunityTrigger: line 7, column 1

    =========

    Query causing the issue: SELECT CampaignId, Sum(Marge_2016__c) lre0 FROM Opportunity WHERE CampaignId in :masterIds AND IsWon = true GROUP BY CampaignId

    ============

    Resolution: The query needs to be optimized to make it selective. This should be looked into by the managed package provider.

    Salesforce supports custom indexes except for multi-select picklists, text areas (long), text areas (rich), non-deterministic formula fields, and encrypted text fields.

    “IsWon” is a non-deterministic formula field hence an index can’t be created.

    • Andrew Fawcett
      March 27, 2021 at 10:32 am

      Yes unfortunately the tool is still subject to these kind of limits per the readme file. Take a look at the scheduling modes wiki page – maybe you need to flip to partial or full scheduled recalcs – likely full. Also it looks then like this parent has lot of children, normally Salesforce recommend max of 10k. The other thing is if your updating a lot of Campaigns (child records at once) then maybe you can flip to the incremental scheduled mode and reduce the scope size (via the tools custom setting). Finally another option is maybe to constrain things further by a date and/or perhaps have an actually Boolean field for isWon for records and update that via a trigger or flow. You would then of course have to get such a field updated for all your historic records keep in mind. So hopefully a few ideas among this response for you. In the end the tool is working within the limitations of the platform unfortunately. Oh and finally have you tried the community chatter group for the tool see what thoughts others have? That is linked on the readme for the tools. Good luck and take care! 👍🏻

  12. Chris Sommers
    March 3, 2021 at 12:20 pm

    Hi, Andy,
    Big fan of Lightning File Explorer. Trying to install the unmanaged code so I can make a couple of changes, but our developer hit a problem he describes here:
    “the package conflicts with an SF critical update from August 2020 – You can now only initiate Apex classes that have a no-arguments constructor that is visible to the code running Type.newInstance. This will result in the code needing to be rewritten, even if we can successfully get it deployed.”

    Is there any chance there is updated code out there that overcomes this?

    One of the reasons I need to make changes is that I’m using Communities, and need the ability to have guest users upload files. But I can’t add guest users to the Permission Set, so every file upload fails.
    Any ideas on how to get past this?
    Thanks again for a great app!
    Chris

    • Andrew Fawcett
      March 27, 2021 at 10:33 am

      Hello – thanks for posting – unfortunately I am not the owner of that tool – have you got the correct site?

  13. Twan Govaars
    March 4, 2021 at 11:57 pm

    Hello Andrew, two weeks ago I left a comment on this site about a problem we are experiencing with a package you created. I didn’t see a reply of you yet, is that correct. Can you please take a look at the message. For your convenience, I’ll paste it again below this message.

    —–

    Issue: When changing the status of any opportunity everyone gets an error:

    Error:Apex trigger dlrs_OpportunityTrigger caused an unexpected exception, contact your administrator: dlrs_OpportunityTrigger: execution of AfterUpdate caused by: System.QueryException: Non-selective query against large object type (more than 200000 rows). Consider an indexed filter or contact salesforce.com about custom indexing. Even if a field is indexed a filter might still not be selective when: 1. The filter value includes null (for instance binding with a list that contains null) 2. Data skew exists whereby the number of matching rows is very large (for instance, filtering for a particular foreign key value that occurs many times): Class.dlrs.LREngine.rollUp: line 210, column 1

    ============
    Debug logs analysis shows that the error is occuring due to a non selective query from the Managed package code:

    11:13:55.1 (320966640)|ENTERING_MANAGED_PKG|dlrs
    11:13:55.1 (322368972)|SOQL_EXECUTE_BEGIN|[210]|Aggregations:0|SELECT CampaignId, Sum(Marge_2016__c) lre0 FROM Opportunity WHERE CampaignId in :masterIds AND IsWon = true GROUP BY CampaignId
    11:13:58.55 (3055899789)|METHOD_EXIT|[7]|01p24000007K7Dz|dlrs.RollupService.triggerHandler()
    11:13:58.55 (3056161207)|FATAL_ERROR|System.QueryException: Non-selective query against large object type (more than 200000 rows). Consider an indexed filter or contact salesforce.com about custom indexing.
    Even if a field is indexed a filter might still not be selective when:
    1. The filter value includes null (for instance binding with a list that contains null)
    2. Data skew exists whereby the number of matching rows is very large (for instance, filtering for a particular foreign key value that occurs many times)

    Class.dlrs.LREngine.rollUp: line 210, column 1
    Class.dlrs.LREngine.rollUp: line 105, column 1
    Class.dlrs.RollupService.updateMasterRollupsTrigger: line 580, column 1
    Class.dlrs.RollupService.triggerHandler: line 318, column 1
    Trigger.dlrs_OpportunityTrigger: line 7, column 1

    =========

    Query causing the issue: SELECT CampaignId, Sum(Marge_2016__c) lre0 FROM Opportunity WHERE CampaignId in :masterIds AND IsWon = true GROUP BY CampaignId

    ============

    Resolution: The query needs to be optimized to make it selective. This should be looked into by the managed package provider.

    Salesforce supports custom indexes except for multi-select picklists, text areas (long), text areas (rich), non-deterministic formula fields, and encrypted text fields.

    “IsWon” is a non-deterministic formula field hence an index can’t be created.

    You may refer the below mentioned article:
    https://developer.salesforce.com/docs/atlas.en-us.salesforce_large_data_volumes_bp.meta/salesforce_large_data_volumes_bp/ldv_deployments_infrastructure_indexes.htm#:~:text=Salesforce%20also%20supports%20custom%20indexes,optimizer%20then%20considers%20those%20fields.

    https://help.salesforce.com/articleView?id=000325247&type=1&mode=1
    ======================================

    • Andrew Fawcett
      March 27, 2021 at 10:35 am

      Sorry for the late reply – my life is quite busy and I don’t get to respond as often as I would like – I am sorry. The good news is I believe I did just respond to your last message with some thoughts. 👍🏻

  14. Kate Michelli
    March 23, 2021 at 7:19 am

    Are you available to help with errors I am getting from the DLRS – is there a help area you offer?

  15. Andrew
    April 15, 2021 at 5:41 am

    Is there an issue with the Deploy To Salesforce Tool? I keep getting the following error when I click the “Login to Salesforce” button

    Application error
    An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. You can do this from the Heroku CLI with the command

  16. Roksolana Kerych
    April 22, 2021 at 4:51 am

    Hi Andrew,

    Is there any possibility to collaborate with your blog via guest post? Do you accept this kind of contribution?

    I would be happy to receive your reply!

    Stay safe,
    Roksi

    • Andrew Fawcett
      June 5, 2021 at 6:05 am

      Not currently Roksi sorry – but appreciate you asking – good luck with your blogging journey!

  17. dennisda7f978f02
    May 14, 2021 at 5:31 am

    Hey Andrew. I’ve been having a BOG of a time trying to get the Metadata API working in a v51 org. Things I’ve tried:

    – FinancialForce class from github: “Web service callout failed: Unable to find apex schema info”
    – Metadata WSDL from org -> APEX Class: “Web service callout failed: Unable to find apex schema info”
    – Switching the version of API Version on various classes from 51 down to 47. Nothing helps.
    – Modify the class a bit to address error: I don’t think I know enough about SOAP. I thought I got close but there were constant errors about there not being a class for various elements like fullName, deprecated, etc.
    – Search internetz: The internet is of no help either which is weird.
    – Ask developer friends: None of my developer contacts have any idea what is going on. They all refer me to the github repo.

    I did notice fundamental difference between the class from the FF git and the generated class. In the FF class, all things extend Metadata. In generated class, all things do NOT extend Metadata. And the Port classes are super different. The FF class has a whole interface structure to handle dynamic return results.

    Either way, I’d really like to get a correct class going so I can move on to building but alas, I am stuck.

    Any help would be amazing.

    • Andrew Fawcett
      June 5, 2021 at 7:18 am

      Yes the FF is modified to support the Metadata SOAP API – the one generated by default does not work. It looks like the FF one needs updating to support v51 orgs. Its odd though because it should be backwards compatible (as the underlying Metadata SOAP API is as well). What operation are you performing and is it with the FinancialForce MetadataService.cls straight from the repo?

  18. Max
    May 21, 2021 at 8:03 am

    Hi,

    I have run into a problem with DLRS. A Guest user (Guest License) is not adding rollup entries, and thus nothing is being calculated (scheduled). Other users are perfectly filling rollup entries (for same object/rollups), but somehow not this Guest user. I suspect it is something with autorisation, the Guest user having no autorisation to add rollup entries to DLRS objects (scheduled items). I have looked everywhere, tried a lot of things but for now to no avail.

    Do you have a pointer for me?

    Brgds, Max

    • Andrew Fawcett
      June 5, 2021 at 7:10 am

      Hi Max, it might be that you need to use the System Mode setting on your rollup here. Also please see the link to the community chatter group for further support – https://github.com/afawcett/declarative-lookup-rollup-summaries#community-support

    • Andrew Fawcett
      June 27, 2021 at 2:17 pm

      Yes it could be – have you tried granting the roll up permission set included in the package to the guest user? This includes these objects. Also try generating some debug logs to see if any errors occur. Finally there is excellent community support – those that may have seen this issue – you can click the link in the GitHub readme file and it will take you to the chatter community page. Hope this jelps

  19. Phuong
    June 2, 2021 at 10:55 pm

    Hello Andrew Fawcett,
    We are using your declarative lookup rollup summaries package, it is a great tool, we have been using it from version 2.11, but now, we are facing an issue that some License Records are not updating with the correct number of licenses assigned. We have done some investigation and found out the problem as below:

    Error:Upsert failed. First exception on row 0 with id a1H0o00000SN4iJEAT; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, dlrs_sfLma_LicenseTrigger: execution of AfterUpdate

    caused by: System.DmlException: Update failed. First exception on row 0 with id 0010o00002mzRH0AAM; first error: UNKNOWN_EXCEPTION, Failed to publish events: []

    Class.dlrs.RollupService.Updater.updateRecords: line 1315, column 1Class.dlrs.RollupService.UpdateWithoutSharing.updateRecords: line 1358, column 1Class.dlrs.RollupService.updateRecords: line 1286, column 1Class.dlrs.RollupService.handleRollups: line 892, column 1Class.dlrs.RollupService.triggerHandler: line 329, column 1

    We tried to upgraded the package to the latest version 2.13, but it looks like this problem still existing. Could you please help to review and advice.

    Your help is appreciated and we are looking forward to hearing from you.

    Thanks and best regards,
    Phuong

    • Andrew Fawcett
      June 5, 2021 at 7:15 am

      Sorry I am not sure – “Failed to publish events” is not an error generated by the tool. I wonder if it comes from the trigger sfLma_LicenseTrigger?

    • antoniograssiuy
      June 14, 2021 at 12:58 pm

      Phuong, we are facing a very similar issue. In our case, it’s a custom trigger that executes upon changes on the sfLma__License records. We get this “UNKNOWN_EXCEPTION, Failed to publish events: []” when updating an Account record, or sending an email, from these triggers (these used to work alright a while ago).

      We suspect the root cause is the Salesforce limited system under which the LMA integration executes.

      Have you been able to find a solution to your problem? I see it’s also an integration with the LMA, so I suspect it has to do with some limitation on the LMA integration system user.

  20. Jeff
    July 1, 2021 at 5:22 am

    Hi Andy. I am new to my company and I see we are using your product Declarative Lookup Rollup Summaries Tool. I get Apex Application error messages every day that reference the summaries this tool is running, for example: “A calculate job for rollup ‘Num Active Summit Assets’ is already executing. If you suspect it is not aleady running try clearing the applicable record from the Lookup Rollup Calculate…” I’m trying to find out why we’re getting these messages and if they’re something I need to worry about? It almost seems like the summaries are maybe schedule too closely together or one isn’t completing before another one starts or something. If there is any kind of assistance or support you can offer regarding these I would appreciate it. Thanks!

    • Andrew Fawcett
      July 10, 2021 at 2:34 pm

      That’s a likely reason – check out the tab for inspecting these errors on the app itself. Clear the records if you believe no job is running and yeah check if the jobs are overlapping. Also checkout the community chatter group linked on the readme file

  21. Harshit Johar
    July 13, 2021 at 12:28 am

    Hi Andrew

    We are using DLRS in our org and recently while creating contacts via third party system using api the system started throwing exception dlrs_ContactTrigger: System.LimitException: dlrs:Too many query rows: 50001. I still dont have the exact debug log which I will get soon but can you please guide what might the issue be here.
    We have 3 Lookup summary metadata defined to roll up 3 fields from Contact to Account. Can you please help with what could be the possible issue in this case?

    Also will the 3 roll ups defined will work in synchronous or asynchronous transaction.

    Any help is highly appreciated. Thanks in advance!

    • Andrew Fawcett
      October 9, 2021 at 9:48 am

      Yes this is a platform limit rather than one of the tool. It is documented with advice in the tools readme file on the GitHub repo where the install links are. Here you will also find link to a chatter group for an amazing community to support you. Yes async and sync contexts work the same way. You might find these are one off errors during the data load and you just need to run a full calculate for the rollups – see button on their derail pages. If the problem persists you may have to switch to one of the scheduled modes – there is some good docs on this on the GitHub wiki. Hope this helps and sorry for the delay in responding. Andy

  22. C.
    September 6, 2021 at 8:30 am

    Hi Andy,

    A Salesforce User tried to update a record, indirectly connected to an Opportunity. The processes failed and this is the error:

    An error occurred when executing a flow interview. Error ID: 1128159254-70161 (306543461): [] Class.dlrs.RollupService.Updater.updateRecords: line 1318, column 1
    Class.dlrs.RollupService.UpdateWithoutSharing.updateRecords: line 1361, column 1
    Class.dlrs.RollupService.updateRecords: line 1289, column 1
    Class.dlrs.RollupService.handleRollups: line 895, column 1
    Class.dlrs.RollupService.triggerHandler: line 311, column 1
    Trigger.dlrs_OpportunityTrigger: line 7, column 1.

    Any idea what the cause could be please?

    Thanks in advance!

    C.

    • Andrew Fawcett
      October 9, 2021 at 9:02 am

      That does look like a gack error code only Salesforce can decode – you will have to raise a ticket to them. It does look like someone has configured DLRS from a flow linked to the save action on the Opportuntiy. So have a look around that area and see what you can see that might look odd or something you can disable to narrow down what might be causing the issue.

  23. prince
    October 5, 2021 at 7:43 am

    Hi Andy, We had a bulk api job running everyday to sync records from our native DB to salesforce all the records are failing with the following error CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY:dlrs_npe5_AffiliationTrigger: System.LimitException: Apex CPU time limit exceeded . Even we tried by reducing the batch size to 20, but still they are failing. Please help me to get rid of this issue.

    • Andrew Fawcett
      October 9, 2021 at 9:18 am

      The cpu limit issue could be a number of triggers and declarative rules on that object it’s hard to pin down at times – this might just be the trigger where the limit finally got reached. Mostly DLRS uses the db not cpu also. What some folks do is when scripting the bulk load leverage the activate field on the rollup definition to disable selectively certain rollups and then when done run switch back on and run full recalc. Other option is to switch from real-time to incremental scheduled mode. This is a good topic for the community behind DLRS as well – they will be super happy to help – you can find a link to that amazing group in the GitHub repo for the tool and it’s readme file. Hope this helps.

  24. Missy Hogue
    October 6, 2021 at 9:57 am

    I need to uninstall because it’s causing issues with our roll-up helper. I am having the hardest time. This is the error is get and I don’t know how to even delete any of the inactive triggers.(all are inactive)
    Unable to install
    Package Declarative Lookup Roll-up Summaries Tool
    Apex Class RollupService Component is in use by another component in your organization dlrs_TaskTrigger
    Apex Class RollupService Component is in use by another component in your organization dlrs_OpportunityTrigger
    Apex Class RollupService Component is in use by another component in your organization dlrs_LoanTrigger
    Apex Class RollupService Component is in use by another component in your organization dlrs_ContactTrigger
    Apex Class RollupService Component is in use by another component in your organization dlrs_Invesyment_AccountTrigger
    Apex Class RollupService Component is in use by another component in your organization dlrs_box_FRUPTrigger

    Please help.

    • Andrew Fawcett
      October 9, 2021 at 9:13 am

      Sorry to hear that. If you have deleted the rollup definitions or unticked the active field on them – the triggers will be doing nothing in reality. However I can understand your need to remove if the tool is not being used. Simply go to a rollup detail page and click the Manage Child Rollup button and then the Remove button – do this for each object. If you have deleted your Rollup definitions create some basic ones and the button will appear on the page of each. Andy

  25. Scott
    October 7, 2021 at 9:41 am

    I need help. You’re triggers remain active even after you remove a job.

    • Andrew Fawcett
      October 9, 2021 at 9:08 am

      Yes the job is just for scheduled rollups. You need to click the Manage Child Trigger button on the Rollup details page – on that page there is a Remove button. If you need further help there is a wonderful community group see the link on the tools main GitHub repo on the Readme file. Andy

  26. Melissa Hogue
    October 7, 2021 at 11:53 am

    We are getting the below error after figuring out how to get rid of the trigger error when attempting to uninstall. Please provide advice on how to fix this issue. dlrs has completely errored out our rollup summaries and they haven’t been working ever since rollup summaries latest update.
    “Package Declarative Lookup Rollup Summaries Tool This extension depends on the package you are trying to uninstall. Package”

    • Andrew Fawcett
      October 9, 2021 at 9:05 am

      I am sorry to hear that – have you tried the community chatter group for advice on your issue? There was some post install steps on the latest version that might not have been followed. Links to both can be found on the read me file in the GitHub repo for the tool. Meanwhile if you want to proceed – clock the Manage Child Rollups button on the rollup details page and then click Remove.

  27. Todd Kadas
    October 20, 2021 at 1:28 pm

    Hey mate-I saw you at CactusForce last year in Phoenix. Nice to finally meet/see a Salesforce celebrity in person. DLRS is a great tool. I’ve used it for quite a few rollups. Just ran into an issue with one. Hoping you might be able to offer some thoughts. I have a task count that rolls up to Account. The DLRS calculates with no error until I activate a process builder that creates a task from an opportunity based on change made to a field. Whilst that PB is active, if a user tries to edit said field, they are thrown an error that indicates that grouped field should not be aggregated: Id. Two separate error messeges to share: dlrs_TaskTrigger: execution of AfterInsert caused by: System.QueryException: SELECT Id, MasterLabel, DeveloperName, Description ^ ERROR at Row:1:Column:18 Grouped field should not be aggregated: Id CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: dlrs_TaskTrigger: execution of AfterInsert caused by: System.QueryException: Grouped field should not be aggregated: Id. I’ve tried to calculation mode: scheduled, realtime, and process builder to no avail. Again, appreciate any feedback you might be able to provide.

    • Andrew Fawcett
      November 14, 2021 at 10:43 am

      Hiya – sorry for the late reply and yes Cactusforce was a really good event – hopefully a another comes along soon. Nothing comes to mind sadly with your issue – I don’t have much time for deep debug these days. The good news is the tool now has a great group of folks behind it thanks to joining Salesforce open source foundation. On the readme file for the repo near the top is a link to a support group where I would advise you post this. Sorry I cannot be more help this time. Andy

  28. Kanchan Rohlania
    November 9, 2021 at 1:32 am

    Is there any support team who can help us review the code in “fflib_SObjectUnitOfWorkTest” class? We are working on encrypting Opportunity name field. Since it is used in this class, we are not able to do so. We need urgent assistance with the same.

    • Andrew Fawcett
      November 14, 2021 at 11:04 am

      Yes head on over to the repo and raise a GitHub issue for your issue. Keep in mind this is a open source community driven free library – there is no formal support. If you have engineers they can review this class and contribute a change back that conditionally reviews the fields encryption status and implements test code accordingly. Here is the main project link – https://github.com/apex-enterprise-patterns

  29. Eduardo
    November 10, 2021 at 3:23 pm

    Hello Andrew,
    I’m trying to enable Shield Encryption to an org that uses DLRS, however I got an error on the “Opportunity Name” field:

    Opportunity.Opportunity Name:
    Apex Class: fflib_SObjectUnitOfWorkTest, line 79, column 28: The operator like is not supported on an encrypted field
    Apex Class: fflib_SObjectUnitOfWorkTest, line 115, column 10: The operator like is not supported on an encrypted field
    Apex Class: fflib_SObjectUnitOfWorkTest, line 142, column 10: The operator like is not supported on an encrypted field
    Apex Class: fflib_SObjectUnitOfWorkTest, line 154, column 28: The operator like is not supported on an encrypted field

    Is there any workaround for it?

    Thanks!

    • Andrew Fawcett
      November 14, 2021 at 10:45 am

      Sorry this is a platform restriction and nothing the tool can do about it. Try consulting the shield docs to see if there is a config to allow this for the fields you are referencing on your rollup that are also encrypted.

  30. Nate
    January 19, 2022 at 8:49 am

    Andy, I have a customer that uses DLRS and there is no dlrs__LookupRollupSummary2__mdt that defines any access to an object that is somehow still being referenced. Specifically FinancialForce’s SCMC__Condition_Code__c object. There just be something somewhere that is still writing dynamic SOQL that is referencing this in a realtime triggered dlrs trigger. But I cannot find any setting or metadata that would be prompting DLRS to reference that, now unlicensed, object. Any ideas or a place to go for help?

  31. Taylor S
    February 23, 2022 at 11:26 am

    Hi Andy,

    I have an installed package for your Declarative Roll Up and I wanted to change the user who comes up on the record changes. What is the best way to do this? Is it only by changing the primary contact on the installed package?

  32. Taylor S
    February 24, 2022 at 9:57 am

    Hi Andy,

    I am trying to change the user who had installed the Declarative Roll Up into our org. The issue is that the records update in his name, we want to move it to a generic user we have set up. Is there a way to do that?

  33. Rajni Bhagat
    March 11, 2022 at 6:46 am

    GETTING BELOW ERROR
    IO Exception: Exceeded max size limit of 6000000
    Error is in expression ‘{!checkMdApi}’ in component in page custommetadataloader: Class.MetadataService.MetadataPort.listMetadata: line 9218, column 1
    Class.MetadataUtil.checkMetadataAPIConnection: line 30, column 1
    Class.CustomMetadataLoaderController.checkMdApi: line 16, column 1

  34. Boris Gichev
    March 15, 2022 at 12:57 am

    Hi Andrew,

    We are one of the many DLRS tool user.
    Thank you for developing it!
    I have a question.
    What is the role of the field “Location” (User or Profile value) in the Custom setting controlling the “Calculate Job Scope Size” and “Scheduled Job Scope Size”

    Do I get it right that when a rollup is running if it is running from this user or a user with thist profile, only then the Scope sices are taken from the custom setting so that you can have more flexibility and different scope sizes on different rollup jobs depending on user or profile ?

    Have a calm day

  35. Sergio Pedraza
    March 24, 2022 at 1:14 pm

    Hi, Andrew.

    We have the following package installed in one of our clients salesforce organization:

    Declarative Lookup Rollup Summaries Tool, Version 2.11

    In the spring 2022 and summer 2022, SOAP/REST API versions 7 to 30 will be deprecated.

    We wanted to know if this package uses any type of SOAP/REST API versions (almost sure it does not, but wanted to confirm).

    This in order to know if we need to upgrade the package to whatever new version is not using a deprecated Salesforce SOAP/REST API versions.

    Thanks for your quick response!

    Best regards.

  36. Joana Matos
    April 1, 2022 at 1:59 am

    Hello,

    As Salesforce will stop supporting API versions 7.0 to 30.0, could you please confirm if DLRS use any of these versions? Thank you!

  37. Dalit Shlapobersky
    July 25, 2022 at 1:36 pm

    Hello there! We are a S. California based nonprofit (affordable housing and homelessness). In 2019 a staff member who is not with us anymore installed a Declarative Lookup Rollup Summaries Tool (version 2.11). It is not working as it should anymore, and our (self-taught) admin cannot resolve it herself. Who could I turn to for help with this?

  38. Tim lehmann
    October 17, 2022 at 3:47 am

    Hello Andy,
    We have a fatal error in our Trigger regarding Accounts. In the Debug log it says”Scheduled rollups are running in legacy mode and are unable to resolve corresponding shadow rollups. Please visit the Lookup Rollup Summary Tools tab for more information and steps to resolve.”

    When I go to the to summary tab it says
    “This version of the tool no longer requires the field dlrs__LookupRollupSummary__c on dlrs__LookupRollupSummaryScheduleItems__c. For optimum configuration and performance please delete it after reading the further information provided.”. However, I cant delete this field in the custom object itself. Andy hints what we can do here?

    Best,

    Tim