It feels like a major violation of Trust that Salesforce has installed a new setting defaulted to ON that allows them to use YOUR data to train AI models
https://www.freelikeapuppy.tech/post/this-setting-makes-me-mad
@Admin Group, Philadelphia, US @Nonprofit User Group, Philadelphia, US @Admin Group, West Chester, US @Nonprofit and Education MindShare @Salesforce MVP Collaboration Space
#AI Trust & Ethics
In the Winter ’21 release Salesforce enforced access restrictions to AuraEnabled Apex methods. As a result of these changes, users may encounter errors when trying to do specific operations in NPSP if permissions have not been adjusted. Historically users were granted default access to Apex Classes. With these updates Salesforce is providing increased access security by requiring that you grant explicit user permissions for users.
What is the change?
In the Winter ’21 release, Salesforce enforced a security update which restricts access to AuraEnabled Apex methods. Unless users have been granted access to specific Apex classes, they will encounter errors when attempting to complete specific tasks in NPSP.
How does this affect me?
If access has not been granted to specific NPSP Apex classes either through User Profile settings or Permission Sets, users, including System Administrators, will see errors when they attempt to:
What action do I need to take?
You will need to explicitly grant users permission to either through User Profile settings or Permissions Sets. For detailed instructions on which Apex classes users need access to, please see this troubleshooting article here in the Power of Us Hub.
@Katherine Prouty This a link to the help article from the original post: https://help.salesforce.com/s/articleView?id=sfdo.NPSP_Troubleshoot.htm&type=5&language=en_US#topic-9192
If the anchor link does not work in the above, clicking on the "I can't seem to access certain NPSP pages" section will take you to the relevant section
Update on Winter 21 Top Ten Items for Power of Ten License Holders!
Unwrapping Winter 21 Release!
First, I logged in this morning. I got a brand new admin only in-app guidance telling me about MFA. But this also told me that Winter 21 is installed. I also had emails from Salesofrce telling me the scheduled upgrade completed.
Second things was to google and find the HTML Winter 21 Release notes. They are also available in PDF if you prefer. Then I went directly to the section about how and when do features become available. Many features are automatic. But some features require admin work and some require asking Salesforce to do something. The latter two were my focus. I scanned down the column to see what required my intervention in terms of features I have from Power of Ten.
I'll post what I found as a comment to help break this up.
Third, I went to my top ten list of Winter 21 Candy for power of 10 license grant recipients. I like to see if the feature is there, how I can use it, and try to find an initial use case. Since I didn't see it initially, I'll add the Mobile Launchpad feature.
1 Dynamic actions for most standard objects on desktop (joining custom objects from Summer) and for custom objects in mobile! Both Beta. Standard object dynamic buttons is a quick win for me, just as it was for custom objects in Summer 21. I was able to configure buttons on our contact page in the highlights panel lightning component to be visible or not based on the values of rollup data for client programs, volunteer programs, donor activity, etc.
On custom objects, once I had created dynamic desktop buttons there was also a checkbox to enable it for mobile. This is per record page. Four round buttons appeared at the top of the record above the other highlight panel info. Note that form factor is one of the conditions so I could have different buttons on mobile than desktop if desired. This is really great once it comes to standard objects since you can really save screen space by only showing relevant buttons! I also made the delete button disappear for non-admin users on one object once status has advanced beyond planning (using user profile name containing admin). This also saves space and improves data integrity.
I'm looking forward to thinking carefully about all these buttons especiually once dynamic field placement comes out for all objects. Buttons can be standard actions, custom actions (which can be tied to interactive flows), or quick actions. So there is a whole lot of power here.
2 New fields auto add to custom report types. Yay! Beta. I enabled it in my profiles. It's a system permission. Then I went to report editor to try it out. I created a new report and selected the managed package version of Contacts with Volunteer Hours and Volunteer Job. I have heavily customized my VH object and none of those fields were available previously in this report type. For this reason, I have a custom report type. But not, all those fields are available on the lighting report editor! Fabulous! I'm not entirely sure this is a proper test because that report type might not be managed. I did a different test using Accounts with Volunteer Hours (which is managed report type). The report has limited fields from VH and does not contain custom fields. So I'm not sure if this works or what limitations are on it yet.
3 Scheduled list email sending! Worked like a charm. I have an email template that I send to donors on the anniversary month of their first donation. I just indicates how important they are to us and gives them a star rating (based on how many years they have given in and how many years they increased giving level by at least 10%). I updated the template on Saturday morning but watned to send the list email Sunday evening. I set it and will forget it. Hopefully I'll get an email Sunday evening letting me know that 47 donors were sent their donor appreciation certificates with this new feature!
Flow got more love than any other customization product. The writing’s on the wall that admins and developers must use flow for maximum impact. The great news is that with every release it simply gets easier and more powerful.
4 Flow: Filter logic added to record searches! Before every condition was ended. So you had to really struggle to do custom logic searches in flow. No more! So now when you get records in a flow, you have the choice of using AND (as in the past), OR (new) or custom logic. I don't have a use case at this moment, but I can recall having big troubles in FLOWS when I needed to do this in the past.
5 Flow: Auto layout editor friendlier for learning and time saver. When you create a new flow, you are asked to use manual layout or auto layout. I chose auto layout on a new flow I was making. It's very clean looking. you are presented with a start and end element and a plus sign on the line between. You click the plus sign to pull up a menu of things to add. Much nicer than dragging an item onto the palette and then needing to wire it up. Decisions create one new wire per possible branch. Oddly it now forces default outcome to merge bck into the flow with the other outcomes. This takes away a sloppy way to exit flow (by not hooking up the outcome). You also can't drag items to reorder, but instead you can select and copy the lower one, click the plus sign above the upper one, select the paste option, and then delete the original lower one. I expect this will get better. There is no zoom that I could find so I found myself having to struggle to click something off the canvas with something like this: click an element in view, drag the whole palette up, then go back and click what I wanted to click. Not efficient but I imagine it will get better.
6. Record triggered flows get criteria. I had one record triggered flow that I needed to update that includes two decisions boxes first thing to test if it should really be running. It was cleaning to put these in the trigger conditions. I was able to do that easily using exactly the same format. That cleaned up my flow a bit. Not sure it adds any new capability since you could always just include a decision box to exit inside the flow.
7 Flow: Debug auto launched flow. Flows that automatically run when records are created or updated is super fast and really the way of the future for Edmonds. Now you can debug them! My assumption is this does work. While you can run the dubugger on a before save records, it just fails since there isn't an ID to set in the debugger. Perhaps they will improve this in future.
8 Flow: Debug flow as another user. This is only available in sandboxes. I don't regularly work with a sandbox so I can't test. But it's available in the debug interface (just can't be set in production) so I assume it does and will be nice.
9 Tabs work better to navigate a lightning page. This is billed as an accessibility update, but for those of us who like to be mouseless, this is priceless. I don't really know how to test or check this. Seems OK when I try to go mousehold and tab to the first view buttons on the page.
10- Lightning record page performance analyzer. You can now get Salesforce his opinion about what you can do to speed up your record pages. This is visible when you edit the record page. I clicked it and it told me some things about my contact page. In my case it noticed that I don't have a detail component and suggested I need one. I don't because I'm displaying field information conditionally through related record components. It also says I have way too many components in the page. But that's because I have a bunch of conditional components that show badges like VIP Donor, Donor, or Lapsed Donor (three components). And similar for other attributes like volunteer and client. It is arguably slower. When dynamic field placement comes to custom objects I may be able to improve this. The page analysis was not that exciting but perhaps it will be more useful over time and as I get more exposure to its recommendations.
11 Email template builder. I’m skeptical, since this is yet another email template format but hopefully this one will be worth it! So I went to the email tab in my account page where I usually send my donor thank you personal notes and didn't see any changes. I used the app picker to select email templates and created a new template. Once I saved a new blank template, I had the option of using builder. I created a nice email relatively intuitively with merge fields for the donor name, a paragraph of thank you, a nice looking button to give again, and included two photos. To include photos, I had to first have them on my local device, then select image. There was a pretty intuitive way to upload new photos and select them. Attachments are not part of what can be done with the builder. I then managed to select the new template for thanking people from my account email widget and send it. Not bad! Tweaking of the template is allowed within the email component although I saw that I could lock the components of the template as well with the builder.
12 Flow: Trigger flow before record delete. I’m not really a big fan of deleting records at all. However, you can now update things using Flow when the record is deleted if you need to.
After a little over nine years at Salesforce.org, I’m leaving today to begin a new journey (after some family time!) at a place I’ve always been proud to call home: the intersection of philanthropy, education, and technology. Reflecting back on the past near decade of my career with Salesforce, there are a few things that hold true throughout, some things that have changed, and some things I hope for our collective future as an ecosystem of people who care deeply about the social sector. I hope you’ll indulge me one last time in this format to share some of those thoughts.
Constants
One of the core constants in my time at Salesforce has been the change, the evolution of the organization and how we plan, effect and measure the impact we can have on the sector as a whole. I’m often asked what is it like to work for the same organization for nearly a decade, especially in the tech sector? The answer is a bit counter-intuitive: I haven’t! The organization now known as Salesforce.org has been through multiple iterations in my time here, with different sizes, different scales, different focuses, revenue models, and more. The plucky corporate foundation evolved into a technology distributor, evolved into a social enterprise, evolved into… well, you get the idea. This change is exciting, and exhausting, and challenging, and rich with opportunity, and constant.
Second has been the importance of product. Since day one in December 2010 I’ve been tasked with ensuring we can deliver the best possible product on the Salesforce platform to our customer stakeholders with the resources we have. Salesforce.org has always endeavored to support our community via product development from its inception, and today that commitment of support is no different. Did you know there are more people working on NPSP, EDA and other open source initiatives today than there were total Salesforce.org employees in 2012? In fact, there are more people working on just the NPSP today than total Salesforce.org employees in 2010! Technology, and the impact it can have on our sector has always been at the forefront of everything we’ve done, and that has been a constant throughout my time here.
Finally, I haven’t always made the right calls. I haven’t always thought we as an organization made the right decisions. I haven’t always aligned with our partners. I’ve even disagreed with customers from time-to-time. However I’ve always firmly believed, whether a nonprofit consultant, a Salesforce executive, an AE, an engineer, an admin on the Hub, a pro-bono volunteer, or some other participant in this ecosystem, that that individual cares, is committed to doing the right thing, and is looking out for the betterment of all stakeholders in the ecosystem.
To be clear, that idea of “betterment” isn’t always black and white. Should it all be free, or is today’s revenue tomorrow’s free product? Is it better to release something half-finished sooner? Or better to wait? Is it better to deprecate a bad product or continue to support an ecosystem? Is a feature “too complicated” or “not sophisticated enough”? These are all decisions that live in the massive swath of space between right and wrong and they’re judgement calls. Sometimes the call is easy, sometimes not, but I’ve never doubted the sincerity of all the stakeholders in our ecosystem to advocate for their assessment of the right thing™.
Changes
One might assume this list is long over the course of nine years, and that certainly is true. However, I think I would narrow it down to the two I view as most impactful: scale/reach and organizational structure. They are inextricably linked, and so I’ll attempt to talk about them both simultaneously.
In 2010 when I joined, the entirety of the organization then known as the Salesforce.com Foundation consisted of somewhere around 25 people. There were around 1200 organizations across the social sector utilizing Salesforce in some capacity, and the concept of “product” or “app” on the platform was very much in its infancy. Undoubtedly, we felt like we were doing good work, but ultimately we were limited in our reach. We were a two (soon to be three) person technology department: one executive and me. For our 1200 customers and burgeoning product line, I was the product manager, lead developer, lead tester, doc writer, support person and product marketer. We put out one release a year… if I could find the time to do it. Webinars were whenever they fit into my schedule, and community engagement consisted of lots of questions answered in online forums late into the evenings. In short, we did the best we could with what we had, but what we had was limited.
By 2015, we were a different kind of organization. We’d moved away from our small grant-making foundation to something bigger: a social enterprise. We had revenue, which meant we had multiple developers, a writer, a product manager, an entire marketing team, and more! No longer were we serving 1200 customers, we were serving 12,000 customers. The self-sustaining enterprise model bestowed on the Salesforce Foundation had evolved into something bigger, Salesforce.org. This gave the technology a reach and an impact we never thought we’d have, and left us grappling for tools to move even quicker, to help the organizations we serve be more effective, more efficient, and better able to serve their constituents. It was an incredible time to be a part of the organization as we were making up this model on the fly. The rules hadn’t been written yet for how to operate a social enterprise of this stature, and we were in the driver’s seat to write them. It changed how we could engage with customer’s missions, how deeply and how many. It afforded us an opportunity to grow a new approach to building products, to building ecosystems. It allowed us to take the best of the incredible culture and work at Salesforce.com and blend it with our own unique identity and build something distinct in the software world.
Today, Salesforce.org is a different kind of organization with a different kind of scale and possibilities. No longer needing to reinvent the wheel, our systems and capabilities extend to helping support 45k+ customers and their constituents. We can now support CSR programs through our philanthropy marketplace, the Salesforce Philanthropy Cloud. We can bring incredible new products to market like Salesforce Advisor Link at a blistering pace. We can continue to grow, support and maintain the incredible communities that have grown and supported us through our open source programs and more. Whether you are a small part-time nonprofiteer looking to get organized or you’re an international NGO, a community college or a member of the SEC, Salesforce.org can help your organization get smarter and more efficient so you can focus on your mission. That’s an incredibly powerful place to be and there’s more to come in this year alone.
Hopes
In the future, there are a few things I hope to see as Salesforce.org continues to evolve as an organization. I’ll be an outsider observer for this next iteration, so consider these my parting words of advice.
Salesforce.com is an incredible company. What has been accomplished there over the 20+ years since its founding is nothing short of a technical and business miracle. It’s been an honor to work for so long in association with the company. At the same time, Salesforce.org has always carried with it an identity all its own. I believe that identity always stemmed from a deep connection with the customers and communities we serve. Something about the altruism so often found in our sectors imprinted itself in the DNA of this organization long before I arrived and is a critical part of what makes Salesforce.org such a special place to work. I hope that distinct DNA continues to thrive, and maybe even spread.
Salesforce.org has an incredible mandate. Equally serve the customers who can pay you little or nothing, as well as customers who can pay their way. This mandate creates challenging dynamics, both ethically and financially. It also creates incredible opportunities across products and services. I hope Salesforce.org and Salesforce.com continue to embrace this paradox and keep alive the commitment to all customers as we’ve done so to this point.
Conclusion
I’ve made my share of mistakes during my time at Salesforce.org, but I’m damn proud of what we’ve built here.There are always improvements to be made, and there’s still so much more opportunity, so much more that can be done. I’m looking forward to watching from afar where the leaders here are going to take it, what’s going to happen for the Open Source Commons, for Salesforce.org Labs, for Philanthropy Cloud, the NPSP, case and program management, FoundationConnect, EDA, SAL, and all the announcements and new products to come. It’s an exciting time for the sector, and an exciting time to be involved in technology and philanthropy. Thank you Salesforce.org for one hell of a ride.
Until we meet again…
-Kevin
Happy Holidays Hubbers! ... it’s time for an end of year holiday *limerick challenge!*
We want to take a moment to say THANK YOU, and also end the year on a fun note 🎵 -- what better way to end the year with a bang than with a limerick challenge!?
>> Comment below and share a limerick of your own if you want to! This is meant to be fun and silly. Here’s a little limerick overview if you want some help.
To start off....
There’s a Hub full of ol’ good folks
who give out help and a few jokes
At the end of the year
we appreciate their cheer
and are proud to call them our blokes
... alright, who else has one they want to share?!?
🏆 PRIZE: the limerick with the most likes gets a Lionheart plushie!
Taking a break from the regular grind
Leaving emails and spreadsheets behind
I'm off to blaze trails
While others grind rails 🏂
With future certifications in mind!
Oh my goodness! If only this had been done years ago! So what will we do in Winter '2020 with this? Oh my...
Contacts: Customize Opportunity Contact Roles for Better Tracking and Reporting
Opportunity contact role customization options give you the flexibility to track and attribute revenue to roles, titles, and individuals. With custom fields and page layouts, validation rules, and Apex triggers, you can design an Opportunity Contact Role to match your specific sales and reporting processes. You can capture new data, such as titles and roles, to help your sales reps be more efficient in targeting the right contacts.
Where: This change applies to Lightning Experience in all Salesforce editions with the Sales or Service Cloud.
Who: Users with the Customize Application permission can customize Opportunity Contact Roles. Users with Read on Opportunity permissions can view customizations, such as custom fields. Users also need Edit on Opportunity and Read on Contact to add, edit or remove Contact Roles from an Opportunity.
Why: When you customize opportunity contact roles to capture and track data, you can report ROI and revenue based on lead conversion, campaigns, contact roles, and more. See the impact on revenues and opportunity close rates from specific roles (1), such as decision-makers, or from leads converted to contacts.
For example, a nonprofit organization can create a custom opportunity contact role called “personal donor” that allows it to track donations directly from individual donors. The organization can then identify its best donors and set up triggers to send thank you emails or other communications based on donation amounts or contact changes.
Many folks, myself included, are concerned about the recent announcement that Salesforce is merging with Salesforce.org - and what this means for nonprofits.
My latest blog post outlines the unique contributions of this community - and what I hope will be a call to action for Salesforce to preserve and cultivate what has been built under the Salesforce.org umbrella.
Please keep up the conversation here and online {twitter, linkedin}- there's folks outside these walls that need to know the contributions, and what's important to us.
https://brightstepleadership.com/salesforce-acquires-salesforce-org-what-could-go-right/
@Salesforce MVPs in the Hub @Open Source Partner Success Forum @Open Source Commons & Community Sprints @Amplify
I particularly highlight some of the contributions of leaders including @Alicia Schmidt @Brad Struss @Sam Dorman @Ryan Ozimek @Kevin Bromer @Angela Adams
I'm especially excited about the potential for integration between Philanthropy and Nonprofit Clouds!
Hi folks,
Thanks to everyone who has shared their questions about the recent combination of Salesforce.org and Salesforce with us via the community, direct messages, texts, and personal conversations. ; ) We hear you!
Salesforce.org has always been committed to this community and, through the Power of Us Program, ensuring that every nonprofit and educational institution has access to powerful technology to help them achieve their missions. In the 8 years I've been at Salesforce.org, our operating model has evolved, but we have never wavered from this commitment. As we move to this next chapter, we remain committed to the Power of Us Program, and will continue to provide free and highly discounted software to nonprofits and education institutions around the world.
I also want you to know that the same folks at .org that have been supporting you as Account Managers, Success Managers, Product Developers and (ahem) Community Managers are still going to be here after we combine with .com working hard to ensure that you all have access to the products and services you need. Salesforce.org will be a dedicated team within Salesforce, mission-aligned with our customers focused on technology for social impact. Sorry, but you’re stuck with us!
Salesforce.org combining with Salesforce is an exciting new chapter for our community creating new opportunities for our sectors. We can now accelerate impact by leveraging the full power of Salesforce and Salesforce.org together to deliver meaningful, measurable, and sustainable outcomes around the world.
This is about driving greater impact with you.
Finally, we want to keep this dialogue going. We will have more information to share once the combination is complete. So, again, we ask for your patience as we work through this together.
I am trying to understand what these post are about and I have 1 concrete question: Is there any plans to stop the 10 license donation program for accepted Non-profit orgs?
*Introducing Batch Gift Entry - LIVE IN SANDBOXES TODAY and GA IN PRODUCTION ON JANUARY 16TH*
We're thrilled to share that Batch Gift Entry is now live in Sandboxes and will be GA in production orgs on January 16th. A big thank you to the 80+ customers and partners who participated in the pilot!
What is Batch Gift Entry (BGE)?
Batch Gift Entry is a data entry tool optimized for getting donation data into the Nonprofit Success Pack (NPSP). This new feature includes a new grid interface for high volume, mouse-free data entry, the ability to process large batch files on one page and use matching logic to prevent duplicate information and advanced donation matching and selection.
With Batch Gift Entry you can:
See the post in the NPSP Release Announcements group: https://powerofus.force.com/_ui/core/chatter/groups/GroupProfilePage?g=0F980000000D9Qr&fId=0D51E00004gH0eU
DOCUMENTATION:
Overview: https://powerofus.force.com/articles/Resource/NPSP-BGE-Overview
Setup: https://powerofus.force.com/articles/Resource/NPSP-BGE-Setup
#Batch Gift Entry #Data Entry #Donations #NPSP
will tackle it one day), but it's really easy to setup and use. If you have an existing Sandbox you should see version 3.146 has automatically been updated so you can play with it.
Or, you can wait until next week when it will be updated in Production (but not automatically enabled).
