#Salesforce Admin360 discussing

We are migrating to SOQL, meaning we will use the same Google Connector to query the data directly instead of exporting reports. Because this SOQL export operates via the API rather than the UI, it successfully bypasses the mentioned limitation.

However, please keep the following SOQL specifics in mind:

• Row Limits: Extracts are capped at 10,000 rows.
• Headers: Google Sheets will display field API names instead of standard field labels.
• Formatting: The column order in the sheet may not match the order of fields in your query.

Despite these quirks, this remains a highly effective workaround.

Hi Tami,

Don't worry, the functionality is still there, but a couple of UI layout changes and common list view quirks can make the template button seem to disappear.

Here are the most common reasons this happens and how to get your template back:

1. Check the Bottom-Left / Bottom Toolbar of the Composer

In the Send List Email pop-up window:

• Look at the bottom toolbar (below the main body text box, near the send/attachment buttons) rather than the top formatting bar.

• Look for an icon that looks like a sheet of paper with a plus sign / folded corner (the tooltip will read "Insert, create, or update template").

• Click that icon and select Insert a template... to choose your template. You will get that familiar prompt asking if you want to overwrite existing content.

2. Make Sure the Composer Isn't Minimized or Cut Off

If your browser zoom is high or the modal is docked:

• Sometimes the action toolbar at the bottom gets pushed below the visible window frame.

• Try maximizing the email composer pop-up or zooming out (Ctrl - / Cmd -) to reveal the bottom icon row.

3. Check Which List View You Are In

• If you are in the default "Recently Viewed" list view, mass emailing behavior and button visibility can be restricted or behave inconsistently.

• Make sure you switch to a custom list view (e.g., All Contacts or your specific filtered list) before selecting records and clicking Send List Email.

4. Template "Related Entity Type" Mismatch

If you click the template icon but your template is not showing in the list:

• When creating Lightning Email Templates, check the "Related Entity Type" field on the template.

• If it was created specifically for a different object (like Lead or Account instead of Contact), or if the folder where the template is stored isn’t shared with your user/public group, it won't appear as an option to insert when sending from Contacts.

Hope this gets your emails out the door! If this helps resolve it, please consider marking it as Best Answer so others running into the same issue can find it quickly.

Hi @John Fine

Both are reasonable. Which tool you should use will depend on what you are rolling up: 

• Customizable Rollups understand NPSP concepts (soft credits, household and contact rollups, time-bound rollups, GAU allocations). They are configured in the NPSP settings UI, run as batch jobs, and stay inside the managed package.
• DLRS works on any object (including custom ones and outside NPSP), can update quickly by trigger, and is actively maintained by its community. It requires deploying Apex, and someone has to own it when you leave.

Use Customizable Rollups for standard NPSP giving metrics, and DLRS only for rollups NPSP cannot do. Do not run both on the same target field. Whichever you pick, document it, and check batch times on your data volume. 

 Hi @Michelle Chang, 

Have you checked out the AppExchange to see if there are any apps that you can use instead of doing any custom dev?

• I could find few options for both Stripe and Aquare

https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FnCw4UAF

I hope this helps.

Thanks for testing those, Souvik - since browser, My Domain, and admin are all ruled out, that error is almost certainly coming from one specific org-wide setting: 'Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows' in Setup > OAuth and OpenID Connect Settings. 

Here's the trap: you mentioned enabling PKCE there. When that org-wide toggle is on, the org forces a code_challenge on every supported authorization flow - but the internal namespace-linking flow doesn't send one, so it fails with exactly 'missing required code_challenge'. So that setting being enabled is what's breaking the link, not something you're missing. 

The fix: turn that setting off (Setup > OAuth and OpenID Connect Settings) in the org that owns the namespace - and in the Dev Hub too if it's enabled there - then retry the namespace link. Once it's linked, you can switch it back on if you want PKCE enforced for your own apps. Note this org-wide toggle is separate from the greyed-out PKCE box on the Salesforce-managed connected app you can't edit - this one you do control. 

If it's already off and still fails, then it's on Salesforce's side (the managed linking app), and the right path is a Partner Support case referencing the error - it's a managed flow you can't patch yourself. But I'd bet on the org-wide setting; toggle it off and the link should go through. 

Hope that finally clears it! 

And if this resolves it, please mark it as the Best Answer so it helps the next person who hits this - thanks! 🙂