Andy in the Cloud

From BBC Basic to Force.com and beyond…

34 thoughts on “Declarative Rollup Summary Tool Update

  1. Thanks very much Andy! I’m very excited to dig into these new changes and and cannot begin to tell you how much I personally appreciate your continued work on this wonderful tool. It really is amazing and an essential part of the Salesforce kit. Greetings from the Berlin Developer group and will pass this on in our next ‘virtual’ & virus-free meeting!

  2. Hey @andy – I’m not seeing this in the appexchange – am I missing something?

  3. Hi @Andy, when can we expect the latest version available.

  4. Hi @andy, when can we expect the latest version available.

    • As it’s a community product – there is no formal release schedule – it just depends on when folks have time including me. What do you need?

  5. Hi Andrew, I just discovered your tool yesterday. So usefull for me ! thx a lot !

  6. Hey Andrew, I am having some trouble with this in my org, Salesforce support said they cannot help me and I need to contact you. I cannot see anywhere else I can request support. Could you assist me please?

    • Hi. Sure the best way is to tap into the community chatter group. The link to that is near the top of the readme file on tools GitHub repo. Thanks

  7. Hey Andrew, we have trouble with roll_up summary due to security changes on guest users. Salesforce advised to contact you to resolve the issue. Can you please assist me in this issue?
    Thanks in Advance

    • This is not a paid tool – its is an open source and community supported tool. Thus there is no official support. However there is a great community behind the tool. Check out the README file on the GitHub repo and on that is a Chatter Community Group link. You can post into that.

  8. Hi Andrew.
    I am having some trouble with roll_up summary in my org, Salesforce support said they were not able to debug your code and to contact you. Could you assist me in this issue as we are unble to contact your support.

    • This is not a paid tool – its is an open source and community supported tool. Thus there is no official support. However there is a great community behind the tool. Check out the README file on the GitHub repo and on that is a Chatter Community Group link. You can post into that.

  9. I’m trying to update to version 2.12 from 2.11 in a sandbox using this link…

    https://test.salesforce.com/packaging/installPackage.apexp?p0=04t0N000001E2L5

    Getting this error, any help appreciated…

    This app can’t be installed.
    There are problems that prevent this package from being installed.
    Package Not Found The requested package doesn’t yet exist or has been deleted. If this is a recently created package version, please try again in a few minutes or contact the package publisher.

  10. Hello. With the new release if I change a dlrs record that was once “Realtime” to “Scheduled Full Calculate” and it already had a trigger code deployed for it will it auto remove the trigger code? Or will it still perform real-time calculations as well as the scheduled calculation? due to realtime dlrs Exclusive Lock errors I want to switch it to scheduled off business hours only.

  11. Hi Andrew,
    I saw your comments about going through Security review.
    Is it listed on Salesforce Appexchange? If yes, please let us know the link !

  12. We are using DLRS for sometime in our project. Recently we came across one issue reported by users. Customer Service Back users were getting an error while doing a contact merge operation.

    dlrs_ContactTrigger: execution of AfterDelete caused by: System.DmlException: Upsert failed. First exception on row 0; first error: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, insufficient access rights on cross-reference id: [] Class.dlrs.RollupService.updateMasterRollupsTrigger: line 946, column 1 Class.dlrs.RollupService.handleRollups: line 842, column 1 Class.dlrs.RollupService.triggerHandler: line 307, column 1 Trigger.dlrs_ContactTrigger: line 7, column 1

    (3857562009)|DML_BEGIN|[946]|Op:Upsert|Type:dlrs__LookupRollupSummaryScheduleItems__c|Rows:2
    09:40:32.850 (3973107470)|DML_END|[946]
    09:40:32.850 (3974602711)|METHOD_EXIT|[7]|01p58000008XKOk|dlrs.RollupService.triggerHandler()
    09:40:32.850 (3975043881)|FATAL_ERROR|System.DmlException: Upsert failed. First exception on row 0; first error: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, insufficient access rights on cross-reference id: []

    We were able to reproduce this issue in lower environments. We made log level as finest but log does not display exactly on which object permission , it is errored out.

    Any help will be appreciated.

    Thanks,
    Kaushik

    • I suspect it will be the relationship field on your rollup rule. It maybe that the users sharing rule does not have access to the master record. If you want you can change the rule to run in system mode and that should bypass this check.

  13. Hi Andy, since this is not available on App Exchange. How can I download this in my test org? Thank you !

  14. I am getting errors when using the DLRS – Salesforce support said to try to reach out to the site I downloaded it form since they can not help me. Is there a place I can do that? Or anyway to contact someone directly? Any help would be great.

  15. Hi Andrew,

    Declarative Lookup Rollup Summaries Tool

    We are getting a custom validation error when trying to update opportunity Stage = ‘Dead Project’ with a Reason for dead status = ‘Competition’.

    Error message: Reason For Dead Cannot Be Left Blank

    Line: Class.dlrs.RollupService.Updater.updateRecords: line 1205, column 1

    Can you help me with this issue?

    Thank you very much.

    • It looks like a validation rule on your master object is giving this error – perhaps? If you try to edit the record manually (fake a rollup update) do you see the same error? If so – you need to update the validation logic to tolerate this update scenario – since all the rollup tool does is update the designated rollup field not any other field – and it lookslike “Reason for Dead” field is blank on the given master record here.Hope this helps.

  16. We have an org using v2.5 and we are looking to upgrade to v2.13 we will be going through testing with such an upgrade as we currently have ~170 rollup records across the org.
    Are there features that may not be backward compatible that we will run into at a quick thought?
    (I know quite the ask when upgrading 8 versions all at once…)

    • Wow Josh yes quite an upgrade – glad you are taking your time. Just read carefully the README file and gather together all the release notes and steps described in each release.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s