kkorynta

Perhaps what I need to do is switch this to developer mode and merge it with my current trigger framework? I looked around for some documentation on a few examples...

@horzel The prefix a0D in our org is pointed to the dlrs__LookupRollupSummary__c object, which is what makes this error tricky to manage. Also, I've since merged the two triggers, which...

@horzel This record was auto created by the system after I converted the settings to the new metadata format. When I reached out to the SFDC community group (Declarative Lookup...

Right, that's why I'm here. The only processes that would access that dlrs__LookupRollupSummary__c record in our org are those in the dlrs package.

Will this issue be prioritized? is there any additional information I can provide?

I’ve tried to delete it before, the package just ends up recreating another record like it. No other process is accessing dlrs records except for this package. The dlrs triggers...

Hey Jim, We are currently using version 2.11.1. In regards to the task trigger, yes, sort of. Originally when I started at this company, they had two triggers on the...

It's likely an old record, but it doesn't make sense why current transactions are referencing it. I'm calling dlrs in both the before insert and after insert as that's what...

Hey Jim - still working with Salesforce support on getting the logs and vetting the information that they're telling us. I'll be sure to update you as soon as I...

Yep, I know how to run a debug log. The problem is, I'm getting logs like this on full detail, which is why I've involved salesforce support to take a...