Skip to main content

#Declarative0 debatiendo

We are facing issue as DLRS rollups are not working at any level. 

 

Object Hierarchy Requiring Rollups 

Opportunity → Quote → Carrier_Quote_Coverage__c → Carrier_Quote_Details__c 

 

Rollups Required Across All Levels 

For each level, we have rollups for: 

 

  • Taxes
  • Premium
  • Fees

 

Specifically: 

 

Opportunity:

 Amount field (using Type__c picklist with values  - Taxes, Premium, Fees) 

Quote:

 Amount field (using Type__c picklist with values  - Taxes, Premium, Fees) 

Carrier Quote Coverage: 

Amount field (using Type__c picklist with values  - Taxes, Premium, Fees) 

Carrier Quote Details:

 Amount field (using Type__c picklist with values  - Taxes, Premium, Fees) 

 

Issue 

DLRS rollups are not working at any level. Previously, the lowest-level rollup (Carrier_Quote_Details__c → Carrier_Quote_Coverage__c) worked, but now even that is no longer updating. No rollups are firing in Realtime across the entire hierarchy. 

 

What Has Been Verified

  • All rollups are configured as Realtime.
  • Lookup relationships are correct.
  • DLRS child triggers are installed.
  • No errors appear in DLRS logs.

 

The managed package is the standard Declarative Lookup Rollup Summaries package. 

 

We need help to understand why all DLRS rollups have stopped functioning, including the lowest level, and determine whether this is due to platform behavior, trigger conflicts, or a DLRS package issue. We also need confirmation on whether DLRS supports cascading multi level rollups natively or requires additional configuration. 

 

#DLRS #DLRS Package #Declarative Lookup Rollup Summaries

1 respuesta
  1. 4 mar, 22:35

    I'm only going to answer the first of these to come through. I'd recommend you delete this and comment on that other post from Rick C (DUAL) so that you can get updates. 

     

    There is no reason to post the exact same message under three accounts.

0/9000

Our company (Finning CAT) is embracing Well Architected and moving towards better CI/CD, and especially Easy and Adaptable core principles.

One challenge we’re discussing is how to move away from org-based development to using source control and automated pipelines, while not losing the ability for admins (and citizen developers) to participate in the process to create low-code solutions quickly and efficiently. We’re currently using Azure DevOps for our core DevOps processes and agile ALM governance, and we’re looking closely at DX@scale as well as test automation since our org has grown a lot. We’re aware some organizations have seen success using Salesforce DevOps to allow admins to participate in the process without needing to get into the complexities of an IDE or CLI, so considering that too.

How have others tackled the challenge of moving to source control as the source of truth while preserving the low code promise of faster-time-to-deliver?

#Salesforce Developer #Devops #Salesforce Admin #Declarative #Maintainability #Release Management
0/9000

Hi, I have a successful Declarative Lookup Rollup Summary running but would like to narrow down the calculation where the PARENT object record type is 'New Business'. Is it possible to specify this please? I only need the field updating if the record type is new business.  #Declarative Lookup Rollup Summaries    

 

#Sales Cloud

1 respuesta
0/9000