Feed

Hi,  @Xin Yuen

Kevin’s method produces the following results: the minimum value across the entire view is 85,951, and the maximum is 131,994. 

85,951 − (131,994 − 85,951) × 2 = −6,135 

Since the article takes the larger of this value and 0, the lower bound of the Y‑axis becomes 0 in this case. 

Here, I’m introducing an alternative workaround. This approach assumes that all values used in the RUNNING_SUM are positive and that the cumulative values do not decrease along the Timepoint. 

Under this assumption, the overall minimum of the cumulative values can be taken from the first Timepoint of each Year, and the overall maximum can be taken from the yearly totals. These can be obtained using LOD calculations and then applied to the same formula used in the article. Please refer to the sample. 

<sample>

<calc>

 Also, since unverified AI‑generated answers are increasingly being posted, please be cautious with responses that do not include concrete samples. 

@Jennifer Shaw

 for us Opportunity Contact Roles were the key. We essentially set ourselves up with two sets of rollups. One set for hard-credits and one for soft-credits. We defined our various filter groups in NPSP Settings > Customizable Rollups to support the various rollups we wanted to create.  

For example, our Opps Won Hard Credit filter group only includes opportunities with an amount greater than $0, that are Closed Won, are classified as donations (we use a formula checkbox field for this), and where the Contact Role is 'Donor'. Our Opps Won Soft Credit filter group is essentially the same thing, but the Contact Role must be Soft Credit or Household Member.  

We have a handful of other filter groups that target open pledges, pledge payments, write-offs, etc. 

Once those filters groups & settings are set up, you can create/edit your custom rollups using those filters. For example, our "Last Gift Date" uses the Opps Won Hard Credit filter while "Last Soft Credit Date" uses the Opps Won Soft Credit filter.  

Once you have all these numbers and dates rolling up to individuals (we also have rollups for accounts by the way), you can easily show what you need either in a report, chart, or even in a formula field that incorporates and compares rollups if you want to give users a single data point to look at before digging into more details. 

Thanks Kimberly - and your layout screenshot actually points right at it: 'Created By' and 'Last Modified By' are on the Energy Audit page layout (in the System Information section). That's a known trigger for 'we hit a snag' on CREATE - when those audit fields sit on the layout and your user has the 'Set Audit Fields upon Record Creation' permission, every new-record save fails. 

Fix: Setup > Object Manager > Energy Audit > Page Layouts > open the layout, drag 'Created By' and 'Last Modified By' OFF it, Save, then create the record again. 

If it still snags, the other usual culprit is a validation rule: Object Manager > Energy Audit > Validation Rules - deactivate any that exist and retry. And the fastest way to see the true blocker is to hit Save and look for the field showing red error text. 

Still stuck after that? A fresh Trailhead Playground clears a corrupted one - the challenge grades against your Trailhead account, so a new Playground is safe. 

If this helps, please mark it as the Best Answer so it helps the next person  

🙂

Hi Lil - that 'pick a record type' screen on New only appears when your profile has 2+ Case record types assigned. So if 'Billing' doesn't show, it is almost always one of these: 

1. The Billing record type was not actually created (or is inactive). Check Setup > Object Manager > Case > Record Types - confirm 'Billing' is there and Active. If an earlier step had you create it, that is the step to revisit. 

2. It is created but not assigned to your profile. Go to Object Manager > Case > Record Types (Record Type Settings), OR Profile > Object Settings > Cases, and make sure 'Billing' is in the assigned record types for your profile (usually System Administrator). 

Key point: the chooser only shows when 2+ record types are Active AND assigned to you. If Billing ends up being the only one assigned, Salesforce skips the picker and just uses it - so keep Billing plus at least one other (e.g. Master) available. 

After changing the assignment, hard-refresh and retry the New button. 

If this helps, please mark it as the Best Answer so it helps the next person 🙂

Hi Christopher - short answer: YES, you can create as many free Developer Edition orgs as you want. Sign up again at developer.salesforce.com

; you can reuse the SAME email - you just need a unique username (it's email-format but does NOT have to be a real inbox). So you're never locked out of dev, just spin up a fresh one. 

On the 'access revoked': the 'sf org login web' command doesn't revoke anything - it only authenticates the CLI to the org, it can't disable the org itself. So your org login should still work independently of VS Code. A couple of things to try: 

- Log in directly at

with that org's username + password. If the password was never fully set, use 'Forgot Your Password' - new Dev orgs email a verification link to set it, which is easy to miss. 

- If the CLI just lost its token, re-run: sf org login web --alias adminops-dev 

And if the org is genuinely gone, no harm - create a new Dev org (per above) and point the CLI at that. Worth knowing for next time: Dev orgs only deactivate after 45 consecutive days with no login, so a quick monthly login keeps them alive. 

If this helps, please mark it as the Best Answer so it helps the next person 🙂

Two things: 

1) your formula structure is quite strange. You are saying "if this condition, then return a number, but hten convert that number back to text" 

If you want text, just return text immediately e.g.

IF(ISPICKVAL(Type_of_Grant__c, "Other") && Funding_Source__c = "Marc Berman", 23, 
IF(ISPICKVAL(Type_of_Grant__c, "PHP-Security Deposit (Non-Subsidized)"), 20, 

can simply become:

IF(ISPICKVAL(Type_of_Grant__c, "Other") && Funding_Source__c = "Marc Berman", "23", 
IF(ISPICKVAL(Type_of_Grant__c, "PHP-Security Deposit (Non-Subsidized)"), "20", 

Then you no longer need to wrap everything in a TEXT() function. 

2) You should avoid multiple IF statements on picklist functions. It will massively increase your compile size. CASE() is far more efficient and easier to read. 

CASE(
    Type_of_Grant__c,
    "Rent", "23",
    "Utility", "23",
    "Pharmacy", "23",
    "Move-in", "23",
    "Aging in Place", "23",
    "PHP-Security Deposit (Non-Subsidized)", "20",
    "PHP-Security Deposit (Subsidized Housing)", "20",
    "PHP-First Month's Rent (Non-Subsidized)", "20",
    "PHP-First Month's Rent (Subsidized Housing)", "20",
    "PHP-Utility (Non-Subsidized)", "20",
    "PHP-Utility (Subsidized Housing)", "20",
    "STRMU-Rent", "20",
    "STRMU-Mortgage", "20",
    "STRMU-Utilities", "20",
    "C19R-Rent", "20",
    "C19R-Mortgage", "20",
    "C19R-Utilities", "20",
    "Measure A", "07",
    "DHSP Emergency Financial Assistance", "20",
    "Other",
        IF(
            Funding_Source__c = "Marc Berman",
            "23",
            NULL
        ),
    NULL
)

Hi Ritika - the 'New Library +' option not showing is a licensing/permissions thing, not a bug in the step. An Einstein Data Library runs on Data Cloud (now Data 360), so if the org doesn't have the Data Cloud license OR your user lacks the right permission, that button is hidden/greyed out. 

Two things to set, in order: 

1. Confirm the Data Cloud permission set LICENSE exists: Setup > Company Information > Permission Set Licenses - look for a 'Data Cloud' license. Trailhead Playgrounds usually have it; if it is genuinely missing, you are likely in the wrong org for this unit - launch the exact Playground the module links to. 

2. Assign yourself the 'Data Cloud Architect' permission set: Setup > Permission Sets > Data Cloud Architect > Manage Assignments > Add Assignment > pick your user > Assign. 

Go back to the Data Library screen and refresh - 'New Library +' will now be there. (Data Libraries index into Data 360 and consume its credits, which is exactly why the license + perm set are required first.) 

If this helps, please mark it as the Best Answer so it helps the next person - thanks 🙂

Great data point, Jennifer - that fills in the cost picture nicely. The 'setup you went through' is almost certainly Salesforce Foundations: a $0 offering you self-activate from the Your Account app (needs an Enterprise Edition+ Sales or Service org). It's what unlocks Agentforce for employees plus 100,000 free Flex Credits - and that credit allowance is exactly why you're barely seeing usage, since basic 'summarize/analyze this record' prompts sip credits. 

So for Amy: turning on Foundations is the fastest zero-cost way to test the record-summary use case with the built-in agent before you build a custom one or buy anything. Nonprofit orgs are usually Enterprise Edition, so it should be available - and it stacks with the Power of Us Agentforce Nonprofit licenses I mentioned above. 

Hope that ties it together  

🙂