#Power Of Us HUB1 discussing

A few weeks ago at True to the Core (TTTC) during TDX, I asked the Salesforce Team to clarify the pricing for Prompt Builder. 

Salesforce Foundations is a free offering that includes Agent Conversations, Data Cloud, and features from Marketing and Commerce. However, despite what Trailhead and Salesforce Pricing pages suggest, it does not include Prompt Builder. 

Since raising this at TTTC, I’ve spoken with multiple Salesforce teams, and even they can’t agree—some say Prompt Builder is included, others say it isn’t. In practice, it’s not available in a Salesforce Foundations org, as the required Permission Sets (Prompt Template Manager, Prompt Template User) and Permission Set Licenses (Einstein Prompt Templates) are not provisioned. 

Currently, it appears Salesforce intends to require an Einstein for Service, Einstein for Sales, or Einstein for Platform license — effectively making Prompt Builder subject to both user-based and consumption-based licensing. 

I appreciate that Salesforce teams have been working on this behind the scenes, and I’ve noticed a shift in messaging. Since TDX, Agentforce’s response on Salesforce Help has changed from ❌ “Prompt Builder is not explicitly mentioned as part of Foundations” to ⚠️ “Prompt Builder is available with Salesforce Foundations, but on a limited basis.”

This lack of clarity is a problem for the nonprofit clients I work with, as they rely on the Power of Us Program for courtesy licenses in the first place. 

I’d like the Salesforce team to: 

1️⃣ Clarify whether Prompt Builder is included in Salesforce Foundations, as the official materials currently contradict each other. 

 2️⃣ If Prompt Builder requires per-user licensing (even temporarily), consider extending the Power of Us Program to provide courtesy Prompt Builder licenses alongside the standard courtesy Salesforce licenses. 

 3️⃣ Correct all marketing and documentation to clearly reflect whether Prompt Builder is included with Foundations (or not). 

At TTTC, it was suggested that Prompt Builder was coming to foundations, but I didn’t get a clear time commitment to the above, so I’m posting here. 

Before I raised this at TTTC I verified this was not currently available in two separate orgs both with Salesforce Foundations enabled. 

If you need a recap you can watch the recording of this question from 11:27 on Salesforce+

#TTTC #True To The Core #Prompt Builder #Power Of Us HUB #AI #Prompts #TDX25

@Prompt Builder @* Salesforce Platform * @Trailblazer Community Cove @* Customer Success * @Nonprofit Hub 

Hey team,

I'm working on NPSP, and I realized that I'm unable to add values to the Source Field, Level Field, and the Previous Level Field fields on the Level Object in my NPSP. It looks like it's supposed to be picklist values but when I go to the back-end, it says it's a text field. I find this quite confusing and I've checked this in two different orgs and it's the same. Can someone guide me please, I'm not certain if the values of these fields are mapped from another object, or if I need to change the field value to picklist and add picklist values by myself, or if these fields are for rollup calculations of other fields mapped to them. I have attached screenshots below:

#Power Of Us HUB

I didn't see anything about automating the naming of Deliverables, so I thought I'd share what I came up with, in case it helps anyone. Open to other thoughts and suggestions. 

I created a "New Deliverable" Action on Opportunities and a "Before Save" Flow to update the Deliverable name upon create or edit.

"New Deliverable" action: 

- Setup->Object Manager->Opportunities->Buttons, Links, and Actions

- New Action

- Leave Action Type as "Create a Record"; Target Object=Deliverable; Label=New Deliverable; Save

- Edit Layout - remove Deliverable Name and add the fields you want users to populate when creating a new Deliverable. Consider adding Type, Due Date, Requirements, "Assigned to" (if you have created that field). Consider making fields required here - perhaps Type and Due Date. Save

- Predefined Field Values section at the bottom: Field Name: Deliverable Name, formula value = "x" (include the quotation marks (this is a placeholder until the Flow populates the name)

Flow:

- Setup->Flows->Record-Triggered Flow

- Start element: Object=Deliverable, Trigger: Record is created or updated, No Entry Conditions, "Fast Field Updates"

- Add an "Update Records" element: Leave it set to "Use the deliverable record that triggered the flow," No Filter Conditions, Set Field Values: Field=Name, 

- Value - create new Resource (I called it vConcatenatedName) - Data Type=Text, Formula = {!$Record.npsp__Opportunity__r.Name} & " - " & TEXT({!$Record.npsp__Type__c}) & " - Due: " & TEXT({!$Record.npsp__Grant_Deadline_Due_Date__c}). This will produce Deliverable Names that look like this: <Opportunity Name> - <Deliverable Type> - Due: <Deliverable Due Date>. Modify the formula to meet your own naming convention/needs.

- Save (I called mine "Deliverables - Before Save - Update Name", Debug, Activate, and Test the Action and Flow. Create New Deliverables and modify existing Deliverables.

Please let me know if this helps or what other thoughts you may have.

#Flow  #Flows 

#Power Of Us HUB #Power Of Us Hub Community #NPSP  #Grant Deliverables

Hi, I have a nonprofit client onboarding with Salesforce via the Power of us route. They have passed eligibility and now have to set up their Org Type. 3 options are presented: 10 free CRM licenses, 10 free nonprofit cloud licenses, 10 free nonprofit success pack licenses. See screenshot.

They don't want to use Salesforce for their fundraising, so are unlikely to use NPSP, rather they have a bunch of custom requirements. I'm wondering if selecting "10 free CRM licenses" will therefore simply spin up an empty SF instance with all the standard objects but no customisations? Then they can build on this without all the NPSP clutter in the back end?

#NonprofitHelp

#Power Of Us HUB #Nonprofit Success Pack