A headsup for anyone whose Production org hasn’t been upgraded to Hyperforce yet: after cutover, all our integration users had to re-authenticate. Made for a lively Monday in the office.
Also, this formula field (Number 18, 0) causes any Hyperforce org’s Report to return a “Number Too Large” error. . .
And pow, hey wow, whaddaya know, you’ve taken a Process like this
and converted it into a Flow like this (after you toggle from “Free-Form” to “Auto-Layout”):
. . . I still haven’t figured out how to save it as a BeforeSave. Because it came from a Process, it seems locked into being an AfterSave, ugh. Still working on that!
API/Integration Profile (custom, using “Salesforce Integration” User License)
User Profile (custom, cloned from “Minimum Access – Salesforce” Profile)
The latter two Profiles should grant
the barest-bones permissions and object/field access (when in doubt, leave it out!), with
whatever Login/Session/Password settings adhere to your organization’s security policy.
Everything else can be granted by Permission Sets. Don’t forget to leverage features like
Permission Set Groups — to define a collection of Permission Sets that apply to a generalized Role like Sales Rep, Customer Support Rep, or Sales Manager. (Don’t forget the power of muting!)
User Access Policies — to assign Permission Sets and Permission Set Groups programmatically (eg, “if user has a ‘Sales Rep’ Role, assign them the ‘Sales Rep’ Permission Set Group”).
Three more random thoughts:
User Access Policies is the feature I have really high hopes for. Programmatically assigning Permissions is huge. Sadly, at least as of this writing (2023-11-14), the feature still has some glaring omissions. In particular,
it doesn’t support OR boolean logic,
nor does it support specifying multiple values for fields like Department.
I encourage you to name API/Integration Users with a consistent naming scheme that makes ’em easy to pick out. Personally, I set such users’
First Name to null, and
Last Name to “API User: [System]”, like “API User: NetSuite”.
Supporting materials from Louise Leckie’s presentation can be found at bit.ly/PS-LL. So gratifying to see someone else is a Bitly fan!
A lot. Beware “Archived Activities”: Salesforce’s quiet policy of hiding Task and Event records from end users after a year.*
Remember Salesforce storage is wildly expensive, hundreds or thousands of times more what it costs to store data in other clouds.
Archive-and-purge old Activities from Salesforce or pay the price!
* The specifics: any
Event created more than 365 days ago,
Closed-Task-with-a-due-date due more than 365 days ago, or
Closed-Task-without-a-due-date created more than 365 days ago
disappears from Reports, Dashboards, and Related Lists. (You can see them by clicking “View All” buttons/links. In my experience, almost no one does that.)
I was also surprised to learn–just today!–that Salesforce enables customers to increase the 365-day threshold. The setting is called “Archive Days”, although beware performance degradation if you increase this too much.
(If the Salesforce Release on that page doesn’t match your org, click the “Order of Execution Overview” link on this page.)
Props to architect.salesforce.com (and its Architecture Basics page, source of the above diagram). I understand Salesforce has discontinued their Well Architected efforts 😢
Long story short: make a copy of this spreadsheet to speed up your Wordle-solving!
The gory details: If you obsess over Wordle like I do, you’ve probably run into the conundrum of
having narrowed the answer to a smallish set of words, but
being unsure which word to play next.
My friend Dave and I are convinced: the best approach is to list all the candidate words, count the number of times each letter appears in all the candidates, and play the word whose letters appears in the most candidates.
Not difficult, but time-consuming! Save yourself time by entering the words in the Wordle Counter, and letting it do the counting for you.
Example: today (September 26th, 2023), I was staring at this after two turns:1
I came up with five possible words: FOCAL LOCAL LOYAL MODAL VOCAL
. . . but which one’s the best to play next?
1] I pasted those five words into Wordle Counter’s “Input: Word List” tab:
2] then on the “Input: Parameters” tab I told Wordle Counter which letters I wanted to count (and activating the “Count by WORD?” setting prevents a duplicate letter from being double-counted within a single word):
And voila, Wordle Counter tells me how many times letters appear in those spots:
. . . and how many times each of those letters appears in my candidate words:
Armed with that information, I played the highest-freq word LOCAL and guaranteed getting the answer in two or fewer guesses:
RAISE as my first play? Yup, I’m convinced, after looking at Wikipedia’s entry on letter frequencies(and sorting the table by descending order of letters in dictionary words), that RAISE is your best play. Come at me, bro. ↩︎
I’m still tweaking it. I’m not sure it’s working right in every situation, but I’m really proud of some of the ARRAYFORMULA() logic. ↩︎
Q: “How worried should I be about my Salesforce Community’s security?”
A: Let’s say “more vigilant than you are right now”, ie, pretty worried.
This article gets at the problem: Salesforce makes it easy to accidentaly set up a Community that overshares data.
Salesforce, in weaselly corporate fashion, doesn’t shout this problem from the rooftops, but instead quietly pushes out Release Updates.
This article has some good commonsense fixes–let’s call it solution #1.
This article lists some more–let’s call it solution #2.
And this article delves into a specific problem, that you ought to switch off allowStandardPortalPages for all your Communities. Vote for the related Idea. Call it solution #3.
And OMG, I was astounded to learn that there’s a User Permission out there called “View All Custom Settings”–and, based on my quick experimenting, it overrides “API Enabled”. wtf!
Kudotek v2.0 