Apex Trigger Dlrsaccounttrigger Has Not Been Deployed Click Manage Child Trigger and Try Again
Over the course of the terminal couple of weeks, i accept been focusing my customs time on release v2.4 of the DLRS tool. Specifically focusing on some much requested features driven by the community in the the Chatter group.
So lets go stuck in…
Rollup Scheduler Improvements
The power to run a full (or partial with criteria) recalculate of a rollup on a daily schedule has been in the tool for a few releases now. However upwards until now the only choice was to run it at 2am everyday. Information technology is now possible to modify this with this new UI, its a flake raw and basic, only for at present it should at to the lowest degree requite some more flexibility.
Back up for Merging Accounts, Contacts and Leads
The platform has some special handling for merging Accounts, Contacts and Leads. Especially when it comes to when Apex Triggers are invoked. Basically if your parent object is one of these objects, prior versions of the tool had no awareness of this performance, then rollups would not recalculate. If you are using Realtime or Schedule adding modes on your rollups. Since the platform does not fire Noon Triggers for child records reparented every bit a result of a merge.
With this release there are two things you can do to fix this. Beginning when y'all click the Manage Child Trigger button, you get a new checkbox option to control deployment of an additional Apex Trigger on the parent object. If your upgrading you volition need to click Remove then Deploy again, to encounter this.
Of import Note: If you don't feel merge operations are an result for your use cases you lot can deselect this option and cut down on the number of triggers deployed. Also if it is simply the rollup kid object that supports merging, there is no need to deploy whatever additional triggers and the tool does not bear witness the in a higher place checkbox option.
Secondly you need to setup the RollupJob as an Noon Scheduled chore (under Setup > Noon Classes), even if you don't accept any Schedule Style rollups. This is due to the fact that due to a platform brake, the tool cannot recalculate rollups realtime during a merge operation. And then it tin merely record that they need to be recalculated. Information technology does this via the tools scheduled mode infrastructure, by automatically adding records to the Lookup Rollup Summary Schedule Items object. Note that you don't need to modify your rollups from Realtime to Scheduled mode for this to work, only schedule the chore.
Support for Archived / Deleted Records via the All Rows Setting
Salesforce archives Tasks and Events after a while. If you accept rollups over these child objects you can enable the Amass All Rows checkbox. This will ensure your rollups remain accurate even if some records have been archived. Notation this besides volition employ to records in the recycle bin. For upgrades (if your not using the Manage Lookup Rollup Summaries tab), you will need to add this field to your layout to meet it.
Row Limit for Concatenate and Last Rollup Operations
If your using the Last or Concatenate operations, y'all can define a limit as to how many kid records are actually considered when calculating the rollup. This is useful if your using Concatenate into a fix length field for instance. When upgrading you need to add the new Row Limit field to your layout if your not using the swanky new Manage Lookup Rollup Summaries tab.
Improved House Keeping for Scheduled Mode
If your are using rollups with their Adding Manner prepare to Scheduled. The tool records parent rollup records to be later recalculated past the RollupJob Apex Scheduled job. In past releases if through merge or other functioning the parent record was deleted before the next scheduled run. Then records would sit in limbo in theLookup Rollup Summary Schedule Items object, being processed and erroring over and over. These will now be cleared out and there is no upgrade actions you need to accept for this.
Summary
Thanks for everyones support for this tool, i promise these changes help y'all go further with clicks non code! Though as reminder please keep in heed the best practices and restrictions listed in the README. If you have whatever questions you can either mail service comments on this web log or use the Chatter Grouping. The Chatter Group is a groovy place to become your query seen by a broader grouping of people who are also diligently supporting the tool besides!
You can find releases of the tool here.
Source: https://andyinthecloud.com/2016/06/19/declarative-rollup-tool-summer-release/
0 Response to "Apex Trigger Dlrsaccounttrigger Has Not Been Deployed Click Manage Child Trigger and Try Again"
Enviar um comentário