Assistant has been on my homepage by default forever and this week it has stopped being populated with notifications of new recurring donation records. I'm having difficulty identifying exactly which "Assistant" this is within Salesforce in order to look up why it may have stopped working. I've seen documentation that Service Assistant was retired in 2025 but I'm thinking this is something different. Any insight is appreciated.
Have you reviewed this Guide? https://resources.docs.salesforce.com/230/latest/en-us/sfdc/pdf/state_country_picklists_impl_guide.pdf
If a contact/account isn't found in the lookup of the gift entry screen, but is actually existing in Salesforce already, where do I configure the matching rules so that this match occurs when the dry run/processing happens.
I am offered matching choices when doing an NPSP Data Import batch from that screen, but the options don't show as part of the Process Batch process for Gift Entry. Which rules is it using? Do I have any control over them?
Go to Setup > Custom Settings > "Manage" next to "Data Import Settings" > Edit. In the "Contact Matching Rule" field, you can type your desired matching behavior. The valid values, I. believe, are:
⛰️ 🔐 New Hands-on Workshop for Premier & Signature Admins: Secure the Org: Find and Fix Vulnerabilities (ADX012)
Misconfigured security settings are one of the leading causes of data breaches. In this 90-minute instructor-led workshop, you'll step into the role of an internal security auditor to identify and fix real Salesforce vulnerabilities across the most common misconfiguration areas.
This workshop was adapted from a fan-favorite capture-the-flag game that has been a hit at live Salesforce events — now available virtually so more admins can play! This practical workshop is for:
Sessions are live and available!
➡️ Premier and Signature customers — Register today on Trailhead Academy — Course code: ADX012
I am trying to connect Microsoft Power Automate to our Salesforce instance and receive the following:
Test connection failed. Details: Test connection has failed. Please check connector documentation and verify that your Salesforce instance meets connector limitations. clientRequestId: 7bae6fa8-7c6d-8fdc-c21d-afd383c1841a
I am trying to connect using Salesforce API version 47.0, which is the highest version available in the list. I have checked our API version and we are on v50.0 (Winter '21).
Is this version mismatch causing the error? If so, is there a workaround since selecting V50 doesn't appear to be an option?
This is the first time I have tried to connect Salesforce to Microsoft via Power Automate (Flow).
Hi, I'm facing the same issue. I've disabled the option 'Lock sessions to the IP address from which they originated' in the session settings and I've also granted access to 'Approve Uninstalled Connected Apps' but still no luck. Any idea how I can resolve this error?
Based on the SF announcement that come June, System Administrator users need to adopt Phishing-Resistant MFA for login, we will move to using a Yubikey for me. We are a relatively small non-profit, totally virtual/no physical location. Thus, all workers are remote. We have 20 SF users. I appreciate any guidance. Question is, what is the justification or real world need for use making it required for all our users to use a physical key?
I wanted to share with everyone some quick updates on this. The enhanced MFA requirements have gone live in my Sandbox and just so everyone knows the UI has changed a bit. I am posting a couple of screen shots, as an fyi.
Also, if you now hit "Use a Different Verification Method", it takes you to this screen.
Not a huge deal, but if you have created any training documents around this, you may need to update them.
Can anyone please suggest some better alternatives?
1) Picture Uploader really only works in Classic because it uploads to the Notes & Attachments related list, which is deprecated by Salesforce Files in Lightning since Winter '18. Once you use Magic Mover to convert all your Classic legacy notes and attachments to Salesforce files for Lightning, and enable "Files uploaded to the Attachments related list on records are uploaded as Salesforce Files, not as attachments" (as recommended during Lightning migration), it breaks the link and the image no longer display.
2) https://developer.salesforce.com/blogs/developer-relations/2015/11/create-lightning-component-drag-drop-profile-pictures.html (You'll get 2 compile errors regarding the "return null"...more deprecated code -- see https://help.salesforce.com/articleView?id=000269952&language=en_US&type=1 -- I couldn't make enough sense of this to understand how fix the code, so instead I just commented out lines 9 and 23, and then it compiled... However, it's very basic, drag and drop only, not even "Upload", "Edit" or "Delete" buttons so users can easily understand how to use it.)
Could a developer here modify the Apex code above to build a more user-friendly app with a resizable Lightning component, Upload/Edit/Delete buttons, etc. and post to the AppExchange... Please??
Hi,
If you're still looking for a native-looking option, we recently launched an AppExchange component for this.
It lets users upload, crop, and display images or logos directly on standard or custom Salesforce record pages, alongside selected record fields so everything stays in one place.
Might save you some time if you don't want to build and maintain a custom LWC just for image upload and display.
Here’s the link:
https://appexchange.salesforce.com/appxListingDetail?listingId=a0NKX000001VLyT2AW
Our org wants to utilize GAU Allocations - but from what I can tell, On the "New Opportunity" form, there's no way to just have a field similar to Primary Campaign Source where you just select which GAU you want to associate the donation with. The only way to do it is after the Opportunity is created, going to related lists in the newly created record and edit the GAU, which takes too long. I imagine this is because GAU has the ability to be split up the amount into multiple Allocations, which is too complex for a simple lookup field, but 99% of the time I just want it to go 100% to one GAU. How can I make this an option directly from the New Opportunity form? I know Campaigns can be tied to a GAU but sometimes we'll have an event where people give to different things, so that's not a solution. Would the easiest thing be to Create a picklist with the GAU options and then a flow that creates a GAU based on the picklist selection?
I don't have need for this so I've never solved it. An opportunity has one closed date. A payment has one date. GAU offers zero dates.
If I truly had a one off for this, I would break it into three opportunities with three closed dates and market so that we don't think people for them multiply and try to live with it. If it were an extremely routine thing, I would probably create 3GAU for the funding in different years and make the allocation that way. Reporting would obviously have to be driven by the GAU grouping and not necessarily the year given. I don't think NPSP or Salesforce has a clean answer for this type of thing.
Even financial folk don't have a great solution. They typically accrue all of it into one account separate out the future part into a liability and then transfer from the liability to current assets one year at a time. That's another option, I suppose. Inner one opportunity with the full amount and make 1/3 GAU allocation to the fund. Create two activities do a year from now and two years from now to allocate more of the Donation to the GAU. In the end, you have 100% of an allocated to the fund and it reports Properly. In the middle, the donation reports properly as a whole donation, but the GAU only gets credit for the "earned" portion. But it's two manuel tasks for someone.
--Terry
PSA for anyone using Grants Management (managed package built on Outbound Funds model) AND also actively using the guidestar verification feature in any automated manner.
In case you aren't fatigued enough with all of the security changes coming next week, there was an announcement for anyone using the native guidestar verification included in the Grants Management managed package with changes deploying now > the underlaying certificate will be changed to Candid's Premiere API instead of the current Guidestar Essentials API.
If you automated the guidestar check in any way (including using the out-of-the-box flow that was released in 2022), at some point you will hit a gobbly gook error and not know why (fun fact: there are no plans to fix it).
If you have already manually updated all of your custom code to handle that error based on the change to the new Candid Premiere API OR you already manually run the tax verification OR you don't use the included guidestar API - excellent > ignore me.
If you are still heavily dependent on the included guidestar verification and don't know WTF I'm talking about, and you want to understand what will break for you, holla at me! (< am I showing my age? I know). I'm happy to chat or even have an open office-hours / ask-me-anything for anyone, depending on level of interest.
also copying @Nonprofit and Education MindShare @Salesforce.org System Administrators @Foundations User Group
Salesforce asks to verify email domain ownership. I go to setup -> authorized email domain -> domain name "salesforce.com" -> edit -> check the box "Verify domain ownership". then I got a message saying "We could not verify this domain. Add a DNS TXT record for this domain with the verification code."
I sent this to our IT and asked them to create the DNS TXT record. They say "can't be done because we don't own salesforce.com or the other domains provided."
Did I misunderstand Salesforce requirement? If I am to give our IT permission to Salesforce, what kind of permission/profile should I give them? I don't really want to give them admin.
Yep should be good. Email Logs have DKIM and SPF columns also if you want to check each email. Support has told me and this article indicates you shouldn't need authorized email domains if you have DKIM setup for that domain. DKIM is the recommended method.
https://help.salesforce.com/s/articleView?id=xcloud.security_user_email_verification_domain_auth.htm&type=5