If you have kids you’ll know how disgusting a sandbox can get. Just keep that in mind as you read this post and think about how it applies to some of the things you’ve done in a Salesforce sandbox over the years.
One thing I’m really growing tired of is dealing with half-baked tests, proof of concept examples, and random fields with no descriptions in the sandbox that I’m using to deploy changes to Production. Part of the reason for this is that prior to the Spring ’16 release Enterprise Edition orgs only got a single sandbox. So if an admin is trying something new, they only have one sandbox to work in. As of the Spring ’16 release you now get 25 with the same edition. This post is going to talk you through how to leverage one or more of those 25 to stop screwing up the sandbox you need to make real deployments from, and separate your playground from your deployments.
It’s been a little while since I posted but this solution got me back into the swing of things. There was a question on Answers, not unlike others that have come before it, about how to open up one field for edit by non-owners in a public read-only environment. Not a different profile, not custom pages, just one field that non-owners can edit on each other’s records.
This is one of those things that comes up now and again, and the answer is always that it isn’t really the way Salesforce is built. The difference this time is that it bothered me enough to come up with something. I decided to roll up my sleeves, break out my “try crazy stuff” developer edition, and see where I could take things.
Once it’s done, the solution is remarkably simple. So here it is:
This is my contribution to No Code November and a way to demonstrate how you can use Flow to create an email alert each time a record is deleted. This type of question, especially around record deletion, comes up a lot on the Answers community and if you google it, most of what comes up is Apex-based solutions.
Since Process Builder doesn’t currently support actions on delete we need to be a little bit more creative with this one. Continue reading
*Hint – not a real email address*
This is a quick post to show you guys why I decided to cut yet another completely free Developer Edition of Salesforce for the sole purpose of attending and functioning at Dreamforce this year.
Even though I consider it a strength, my wife would say that I’m slightly compulsive when it comes to planning itineraries, especially around travel. The more I looked at the Dreamforce15 app the less comfortable I got with relying solely on it for my travels. Hopefully everyone gets to see a few reasons why getting more than one developer org can be helpful, even for small and short use cases like this