Hmm, I'm not so sure about option A. While the automatic updates are nice, I've seen some declarative customizations break when Salesforce makes changes. I think B and D are the safest bets here.
Agreed, Ahmed. I think options B and A are the way to go. Declarative customizations may be more maintainable, but I wouldn't say they're immune to errors. That's just wishful thinking.
Haha, 'can't generate runtime errors'? That's gold! I'd love to see the developer who can create a 100% error-proof customization. I'm going with B and D as the best options.
I'm not convinced that declarative customizations can't generate runtime errors. That seems a bit too good to be true. I think option B is the strongest answer here.
I agree with Ryan. Declarative customizations are definitely more low-maintenance, and the fact that they automatically update is a huge plus. I'm not sure about the test class generation though - that seems a bit far-fetched.
Hmm, this is an interesting question. I think the key benefits of using declarative customizations over code are the reduced maintenance and the automatic updates with each Salesforce release. What do you all think?
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Buddy
8 months agoJames
8 months agoTrinidad
8 months agoNobuko
7 months agoMireya
7 months agoQuentin
8 months agoCarisa
7 months agoYesenia
8 months agoGeorgeanna
8 months agoCammy
8 months agoKenneth
8 months agoQueenie
8 months agoStephaine
8 months agoTiara
9 months agoVivan
9 months agoJoaquin
8 months agoGlory
8 months agoJospeh
9 months agoGeoffrey
9 months agoThaddeus
10 months agoLashunda
10 months agoDaren
11 months agoIzetta
11 months agoJade
9 months agoDelfina
9 months agoAhmed
11 months agoDaron
11 months agoArlette
11 months agoRyan
11 months ago