The Story Behind this Course
Have you ever felt like an imposter, sitting in a meeting and participating in discussions on a topic that you were not familiar with? I have.
In 2014 I moved to London for two years to join a Salesforce Consulting Company. I was staffed on a fairly complex project as a Technical Architect. The client wanted to implement Salesforce for their business operations, and this required integration with various backend systems. Sure enough, there were frequent meetings and discussions on integration related topics.
Now, at a macro level I understood the concept of integration & APIs, what do they do and why they are required. But at a Micro level, I did not know & understand how exactly it worked. How do you make API calls, how do you query, insert, update, delete records in Salesforce through APIs. Client’s integration team was not familiar with Salesforce and being a technical architect on the project, the onus was on me to guide them through. But because of my limited knowledge of Salesforce APIs, I often found myself feeling unconfident & uncomfortable, pretending to be understanding things that were talked about and avoiding asking questions. In other words, I was being an imposter.
At one stage, it became so frustrating that I decided to do something about it. So, for next 3-4 weeks, I spent a lot of time and energy in figuring out the basics of how exactly APIs works in Salesforce. How do you connect to Salesforce, how do you make API calls to query, create, update, and delete records? And it wasn’t an easy journey. I had to struggle to figure out even the most basic things.
Long story short, once I figured out how Salesforce APIs work, the restrictions & limitations, those meetings started becoming easier to handle and even enjoyable. I particularly remember one troubleshooting discussion where the integration team reported that they were not able to retrieve more than a certain number of records from Salesforce through an API call and I advised them that Salesforce will return a maximum of 2000 records in one call. If there are more than 2000 records based on the query conditions, the response will contain an indicator and a link to retrieve the next batch of records. It was liberating.