Salesforce Diaries

I'm writing this article as the second of my CTA series, and I want to walk through some areas that you should really think about when doing the CTA exam and aspects that need to be though about in unison as their impact is wide reaching in the solution. I'm going to call out a few examples in this article to get people thinking and be switched on, on the day of the board. (1) Data Model - Master-Detail or Lookup The use of Master-Detail and Lookup fields has a very stern impact on the Sharing Model. 'Who can see what' suddenly is driven by a parent object and not the object in question itself. Whilst this may seem very trivial it can lead to the downfall for a lot of candidates, and it's something to keep in mind very closely. When doing the Data Model, consider the Sharing Implication hand in hand. If you have time do a sense check for what kind of objects and records the users in the system need to see, and does your sharing Model combined with your data mod

The Salesforce Certified Technical Architect (CTA) credential is the ultimate credential in the Salesforce ecosystem and one that is extremely difficult to obtain, however it worth gold-dust in our industry and really stands you from the crowd. I would stand firmly and say that in the Technology Industry this is definately the hardest credential to obtain and proves that you really know your stuff about enterprise architecture and are one of an elite few. This is one of the hardest things I have done in life, and therefore it is my biggest accomplishment. Salesforce CTA's are a special and elite bunch. Here are the reasons why: ( 1) Consultancy Ability : You need to be a strong Salesforce consultant and on-the-spot thinker to be able to pass this credential. You need to know your stuff really well to be able to apply it in a highly time pressured scenario, and be able to explain highly technical concepts in a manner that makes sense. This is an art, and one that