Production and Sandbox orgs link to the same Quip/Salesforce Anywhere org. So when you’re knee-deep in testing triggers and flows in a sandbox, when one of your core change management colleagues messages you via an Anywhere chat, it appears in the Sandbox user interface as well — alerting you to the fact that some attention likely must be paid.
Salesforce Flow and Process Automation constitute a suite of tools that make an admin’s life (and those of the users s/he serves) easier and easier. This is because the tools steadily become and more and more powerful. And more approachable to non coders. Win. Win. Win.
There’s a funny asymmetry at play in Salesforce NPSP. If you use the UI to enter a lone, “naked” contact, the fancy business logic envelopes that lonely figure in a Household account, as the primary contact on the household.
Nifty. Gee-whiz bang.
So why is it that when you create an organization and a first staff member on that organization, it doesn’t do something similar? Manually setting the primary contact gets irritating if you’re doing too much of it..
But with the aid of Process Builder launching a flow, this too can be configured in all its automated elegance — with the added benefit of affiliated the contact with their account’s API validated mailing address.
A client of mine in Education Services is uploading a large amount of data published by NYS Department of Education about some 7,000 schools & hierarchical entities related (Districts, Charter Schools, Charter Operators) in NY State.
The ETL professional in me likes large numbers. But the SF Admin in me is wondering about a performance hit. Also, hoping to upload this to an Enterprise org I have with Einstein Analytics licenses for the soothing transformations when selecting subsets of the data. Stay tuned.
We still have a few more child objects off the account to go, and I’m wondering if this is a good case for using Big Objects or an external data source. Suggestions welcome!