Welcome back to another episode of “Cooking with Code” where I introduce delectable bite-sized topics related to coding in Salesforce.

Today, we are concluding our satisfying sampler of Salesforce Object Query Language (SOQL) with Part Three of this three part series.

My first post introduced the basics of SOQL statements, including the following concepts and keywords: SELECT, FROM, LIMIT, ORDER BY, basic WHERE conditions, and basic operators. My second post showed how to pull data from related standard and custom objects.

Share this:

Welcome back to another episode of “Cooking with Code” where I introduce delectable bite-sized topics related to coding in Salesforce.

Today we are getting into a sweet subject that I can’t wait to share with you! This is the first of three posts where together we’ll tackle the basics of SOQL, or Salesforce Object Query Language. SOQL is used to pull data sets from Salesforce and can be used in both Apex and Visualforce. Fantastic stuff for Salesforce Admins to learn, because we’re all Data Geeks at heart. (Data Nerds Unite!)

In my last blog post, Iwrote about variables, and in particular, primitives. Today I’m going to expand on variables and talk about the oh-so-powerful idea of “collections.”

Unlike Java, which only has one type of collection (Arrays, also know as a Lists), Apex has three to choose from: Lists, Sets, and Maps. Together, we’ll go into each of these types of collections and show you what they are best used for, and how to use them when you start coding.

Share this:

Thinking about variables makes me hungry. That might be taking things a little far, but I’ve been preoccupied with cooking and coding recently, so they seem to be merging in my mind. I think this stuff can be fun, and for me, silly analogies make it all easier to understand. Hopefully by the end of this post you’ll agree!

I’m working with a couple of different groups on various projects to learn and teach two related Object-Oriented Programming (OOP) languages: Apex and Java.

One of the big stumbling blocks for beginners is understanding OOP terminology and concepts. In this blog post, I’m taking the opportunity to gain better understanding of the terminology, by explaining it to you.

Share this:

I completed the available Salesforce Trailhead modules last Friday with mixed feelings. I’m really pleased to have checked all the boxes and gained all the badges, but I’m more than a little sad that I’m done (for now).

I wanted to give back some love to the Salesforce Developer Relations group by writing a review. You can probably guess that I loved it, but I hope to say more on why, and better yet, get you to check it out for yourself. Plus some tips on how to best use the tool, and advice on what you might want to skip over if you’re short on time.