search

SFDO-Community / declarative-lookup-rollup-summaries

Declarative Lookup Rollup Summaries (DLRS) is a community built and maintained Salesforce application that allows you to create cross object roll-ups declaratively - no code! For install instructions and documentation, visit our website https://sfdo-community-sprints.github.io/DLRS-Documentation/
https://sfdo-community-sprints.github.io/DLRS-Documentation/
BSD 3-Clause "New" or "Revised" License
696 stars 238 forks source link

Option for "Do Not Overwrite Target Field Value with Null Value" #521

Open sd5000 opened 7 years ago

sd5000 commented 7 years ago

Problem

It would be great to have a configuration option to tell the rollup process not to delete an existing value in the target field if there is nothing to roll up. Essentially saying "if you have an updated value then update the target field, but otherwise leave it alone."

A sample use case is that we have a field on Contact called "Date of Last Soft Credit". DLRS is set up to roll up the max date of child soft credit records to that field. That works well.

However some Contact records already have a legacy date in that field that we want to keep, even though they don't have corresponding soft credit objects. Currently DLRS deletes that legacy date value when it batch calculates the rollups, since there are no child soft credit records. It would be great to be able to tell it not to do that.

Obviously this wouldn't be the ideal default behavior, but to be able to turn it on would be super useful. I've seen similar settings in tools like formassembly (screenshot below), dataloader.io, etc.

donotoverwrite

Solution

Logic Assertions

QA

Implementation

afawcett commented 7 years ago

Yes @sd5000 thanks for this suggestion, its been covered before in another enhancement request, so this maybe a dupe, for now though i'll leave it open. Thanks again!

asinclair56 commented 6 years ago

@afawcett where was this feature implemented, because I'm getting populated values nulled by the tool in version 2.11

mazz44 commented 5 years ago

This would be a helpful feature. I recently had to roll up to a newly created field since this option was not available.

tcharles12 commented 2 years ago

Yes @sd5000 thanks for this suggestion, its been covered before in another enhancement request, so this maybe a dupe, for now though i'll leave it open. Thanks again!

Any update on this item? Thanks!

jenxyz commented 1 year ago

Hello, this enhancement request 'Do Not Overwrite Target Field Value with Null Value' is affecting me - wondering if there is any update?

aheber commented 2 months ago

Similar to #161, different need but similar engine changes. Mentioning to link them together.