Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Are you being served - Rob Cowell
- 1. Are you being served? EXPLORING WAYS IN WHICH SALESFORCE DEVS CAN HELP SALESFORCE ADMINS ROB COWELL – SR. SALESFORCE DEV BMO GLOBAL ASSET MANAGEMENT @ROBSALESFORCE
- 2. We’re all Adminelopers. Or Devmins. General Dogsbody DeveloperAdmin
- 3. Lightning Components For Fun And Profit* * Forward-looking statement. May not actually generate any profit. Your mileage may vary. Terms and conditions apply. Seek professional advice on Trailhead.
- 6. Source Control all the things* * Yeah ok, we didn’t actually fix this, but we provided a great deal of advice on preventing it happening again…
- 9. Much to learn, we still have
- 10. Ask your developer to service you, if they’re free
Editor's Notes
- Ran from 1972-1985, so if you’re under the age of around 38 and don’t spend your evenings watching UK Gold, my carefully crafted meme is totally wasted on you
- Boundaries between roles is constantly blurred Many organisations don’t distinguish between them – if yours does, you’re lucky I sit in that little triangle in the middle
- Let’s get the obvious one out of the way – in Salesforce’s new vision Devs make Lightning Components to be consumed by Admins Degree of truth to this – in our shiny new Lightning org, we’ve tried to toe the party line and take the clicks not code declarative approach But we’re constantly finding we have to work around things, which effectively means writing components to do things we’re used to having as standard in Classic
- Not just for Devs – quick and dirty SOQL queries are still the fastest path to seeing data, ahead of reports. And they’re disposable Anonymous Apex – your friendly neighbourhood Dev can also process things in the system programmatically, in bulk, that may be more complex than anything Data Loader and Excel can handle
- Here’s another way in which the path of the Developer can help with the way of the Admin, which Chrisie has kindly allowed me to share with you. None of us like the panic and fear that comes with losing a huge investment of your time and effort on that killer feature that will transform and enrich your user’s lives. So how can Devs help with this one?
- Between developers such as myself, Martin Humpolec and Wade Wegner (oh, and someone called Salesforce Docs…), amongst others, we promoted the adoption of Source Control for admins. Because your metadata is important to us. I genuinely believe that *anyone* making configuration changes in the org, be that code, flow, processes, fields, record types, you name it – should be subject to version control. If you’re a non developer and have never been exposed to this, sure, it’ll take some getting used to, but the benefits are HUUUUGE. Bigly.
- Once we have Source Control of our declarative changes, in the form of metadata, why not go the whole nine yards and align to the DX way of deploying. At London’s Calling and other community events, Developer Evangelist Peter Chittum has often demonstrated why we shouldn’t be afraid of the command line and he’s kind of right. As he often claims, if you can write a formula field, you can use a command line and for Admins, this gives you the power tools to deploy seamlessly to your target environments. If you embrace it fully and use Scratch Orgs, it’ll even detect changes for you, even those pesky front-end config ones. Talk to your friendly neighbourhood Salesforce Developer (or Trailhead) to learn more about Salesforce DX and scratch orgs
- As a note of caution, it’s worth reiterating that Devs are still under the same constraints of governor limits as everyone else – we don’t have magic key here. That said, devs should be well versed in bulkification techniques to help you get those bigger tasks completed.
- Frankly, as a Salesforce Developer, I’m frequently astounded by how you Admins get shit done *without* code – I mean seriously, that Flow stuff is seriously badass, and I’ll happily admit I still suck at it. So I’ll be doing a companion talk to this one at a future London Developers meetup, pitching things from t’other side of the fence – firstly, how can we, as Developers, better meet the needs of our Admins but secondly and possibly more importantly, what can we learn from Team Declarative? I still contend that the sign of a good Salesforce Developer is how much code they DON’T have to write.
- We’re all busy – I get that – and sometimes developers look like they’re sat there just staring off into space. Well, yes, sometimes we are and sometimes we’re actually coding in our heads before committing it to keyboard. So reach out to your Salesforce developers – and not just the ones at work, but within the community too – and ask them if they’re free. You might just be surprised at their willingness to make you life easier.