Dreamforce: My Highlights as a Newbie

Dreamforce. Keynote. Dreamforce. Presentation. Dreamforce. Sessions. Dreamforce. Swag Dreamforce. Comfy Shoes. Dreamforce. Agenda Builder. Dreamforce. Saasy. Dreamforce. Dreamforce. Dreamforce.

For the past few months, as excitement for Dreamforce 15‘ grew, these are just some of the ideas and terms floating around the cloud. The countless article, blog posts, tweets and videos could not do enough to prepare me for #DF15.

Because, after all. Dreamforce is Dreamforce.

***********

Admin Zone Theater
Admin Zone Theater

#1 – Admin Zone Presenter

Yup! Aside for being a newbie to Dreamforce, I was a first time presenter. My Wednesday started with a quick registration check-in and then I headed to the Admin Zone (Lodge) for a smashing presentation (full post on that coming up). I was honored to share my thoughts and tips with such a great crowd. Having received so much from the wonderful Salesforce Community, it felt good to be able to give back. I was double honored with the flow of questions at the end and being approached for tips on how to get certified.

#2 – Apex 4 Admins

This was my-must-attend-session and thankfully, I was able to attend! I arrived 35 minutes early to ensure entry – and good thing I did because I was the last person admitted to the class. It was truly a sad moment to watch over 150 people be turned away. From Apex Classes, to Lists, to SOQL, Leah McGowen-Hare rocked the room as she eloquently and humorously guided us through different Apex concepts. There were several “Aha!” moments that will help propel me in my journey to learn Apex.

Swaaag
Swaaag – Day 1

#3 – Swaaaaag

Because I wouldn’t be a good blogger if I didn’t talk about the Swag. My closet now boasts to many T-shirts to number, sweaters and a few other prized goodies (think selfie-sticks, remote-controlled Ferrari, Quadcopter) . It’s not often I can go away for a week and come back with presents for the little ones without even stepping into a store.

#4 – The People

Meeting my colleagues from Cloud 4 Good was definitely the greatest highlight. Working remotely, it’s not often we see past each other’s shoulders (webcam). Having these few days together was a real treat of fun. Through sessions, booth duty, and keynotes (not to mention evening parties and Dreamfest!), I really got to see and appreciate even more how close we are as a team.

It was also incredible to meet with so many people that I know virtually or not. Every moment was a surprising new encounter, relationships forged and strengthened.

#5 – The Everything

There are too many awesome moments to expound on them all;  GirlForce Meetup was a beautiful event to meet and connect with fellow women in the nonprofit tech world, the various zones and expos were great learning opportunities as were the many sessions, keynotes and events over the week, Dreamfest has no words (and left many with no voice), Dreampark was stolen moments of relaxation and HOTs are just about the best thing out there. On top of that, San Francisco is a beautifully place to be and the weather cooperated wonderfully.

A most inspiring, exciting and exhilarating week.

Because, after all. Dreamforce is Dreamforce.

Lookup Vs. Master-Detail: The Real Difference

I have a confession:

For a long time, I never really understood the difference between a “Lookup” field and the “Master-Detail” lookup field. Whenever I needed to create a field that referenced another object, I would read over the Salesforce explanation and then randomly chose one field.

Lookup...or...Master-Detail
Lookup…or…Master-Detail

Over time I discovered various nuances, but the real “Aha!” moment was when I really, really got it.

Simply put, a Lookup field connects 2 objects to each other. For example, a customer can be linked to a store they frequently shop at. This relationship, while helpful to know, does not intricately bind the customer and store to each other. If the store closes down, the customer will still be around and shopping – but in another store. The relationship ends with no affect on either end.

Let’s use a Parent-Child analogy to explain the Master-Detail relationship:

Parent & Child
Parent & Child Relationship

MasterDetail is like a human parent child relationship. Just like a child can not exist without a parent, a Detail (child) record MUST have a Master (parent) record. This strong relationship makes the relationship field required on all records. As well, the child record inherits the same ownership and security (think DNA) as the parent record. Should the Master record be deleted, all the Detail records will be deleted with it (think of going back in a time machine – before the parent was born = no parent, no children).

Similarly, going back to our store, the inventory can have a MasterDetail relationship to the store. If the store closes down, the inventory has no use and and can be deleted. You might chose to send the merchandise to another store which would be called Reparenting in Salesforce (sorry, not detailing that here!).

Hope this helps you navigate object relationships in Salesforce!

Wishing you a wonderful, relaxing, long weekend,
Rachel