Question on using formula fields that return dates in Calc Item Where Clause #120
-
I'm trying to determine why I'm not getting the results I'm expecting and I wonder if it's because I'm using a formula field on the child record that returns a date. I know formulas aren't evaluated unless they are needed, like when displaying on a page or in a report. So I'm wondering if that is causing the issue? Here's the scenario: I'm trying to roll up fund grant amounts (child object) to funds (parent object) for a given time period. On the child object, I'm using Calc Item Where Clause = Grant_Date_From_Grant__c >= 2021-04-01. Grant_Date_From_Grant__c is a formula field that looks at a parent object, grants, to get the date. The fund grants object is a junction object between Grants and Funds. The roll-up is working, but it's getting unexpected amounts. For example, I have one grant for $35,000 but I keep getting a value rolled up of $36,500. I've re-created the query in the developer console and in a report and get $35,000. Here are my settings for this rollup: And here is a quick ERD: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
@jkenzer have you cleared out the rollup field and recalculated using the rollup app? We have several other NPSP rollup orgs using formula fields with dates in the Let me know if the full recalculation is still yielding some bizarre value, like $36,500! If that ends up being the case, modifying the Thanks! |
Beta Was this translation helpful? Give feedback.
@jkenzer have you cleared out the rollup field and recalculated using the rollup app? We have several other NPSP rollup orgs using formula fields with dates in the
Calc Item Where Clause
, so that shouldn't be an issue. Typically, for updates to the child objects (Fund Grant Association
here), only when theGrant Amount
field has been updated will that value get incremented to the existing parent-level value (which is why the full recalc using the app is a pre-req).Let me know if the full recalculation is still yielding some bizarre value, like $36,500! If that ends up being the case, modifying the
Org_Defaults
rollup control Custom Metadata Type record to enableIs Rollup Logging Enabled
…