1 / 29

@archladies archladies

@archladies archladies.com. PLATFORM DEVELOPER I Certification Study Group Week 2 Led by: Blanca V. Leon-Carter bvleoncarter@gmail.com. #LBAjourneytoPD1. Week 1 Reflection and Brief Q & A. Resources here, resources there, where oh where do we start?.

rock
Download Presentation

@archladies archladies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. @archladiesarchladies.com PLATFORM DEVELOPER ICertification Study Group Week 2 Led by: Blanca V. Leon-Carter bvleoncarter@gmail.com #LBAjourneytoPD1

  2. Week 1 Reflection and Brief Q & A Resources here, resources there, where oh where do we start? • Start with Trailhead’s Trailmix: “Prepare for Your Salesforce Platform Developer I Credential” • Our weekly content schedule in the homework area. Usually one or two readings or videos. Trailhead badges Brooke pulled for us that are not already in the above trailmix. • Additional resources list in our weekly content schedule for specific support with specific areas you feel need more understanding. Usually links point to Salesforce Documentation. Look at what is relevant to your needs in our LBA: PD1 Study Group- Study Resources sheet. • Hands-on and real business scenarios look at other online learning platforms, blogs, and Salesforce Developer resources and recordings.

  3. Week 2 Objectives Data Modeling & Management • Given a set of requirements, determine the appropriate data model. • Describe the capabilities of the various relationship types and the implications of each on record access, user interface (UI), and object-oriented programming. • Describe the impact of schema design and modifications on Apex Development. • Describe how to visualize and create entity relationships. • Describe the options for and considerations when importing and exporting data into development environments.

  4. Salesforce Terminology This Excel spreadsheet is a table, in Salesforce tables are Objects. Columns are Fields Rows are Records Image Source: Salesforce, Understand Custom & Standard Objects

  5. Data Modeling What is data modeling? • We use objects and fields to setup an application in Salesforce. • Data models can include: Standard Objects Custom Objects Standard Fields CustomFields Standard Fields CustomFields Examples of a custom objects: Your company needs to track real estate properties and creates an object specifically to hold real estate property records/data Examples of Salesforce standard objects: Accounts, Contacts. Opportunities

  6. How do you edit a Data Model? • In Setup > Object Manager > - Create fields on objects that already exists (standard objects) - Create new objects (custom objects) - Create new fields (custom fields) within the standard and custom objects - Set up relationships between objects & fields • Use a nifty built-in Salesforce tool called the Schema Builder • Force.com home page > Schema Builder under Quick Links Can be found under Setup > in Quick Find box type “Schema” and there it is!

  7. Schema Builder You can: • View the data model • Make editsvery quickly • See a collection of objects and fields and how they relate to each other

  8. What is a data model relationship? • Relationships are how we represent and link different objects within our data model • Used to link standard and custom objects • Used to link two custom objects • Used to link external objects and Salesforce objects

  9. Relationship Types • Lookup Loosely links two different objects and doesn’t effect deletion or security of records. • Master-Detail Closely links two different objects and will delete child records automatically when parent records are deleted. Parent controls who can view the detail’s data. • Many-to-Many Links a record of one object to multiple records of another object and vice-versa with junction object • Hierarchical Links one user with another user via lookup field

  10. External Object Relationship Types • External Lookup Links a child standard, custom, or external object to a parent external object using the standard External ID field. • Indirect Lookup Links a child external object to a parent standard or custom object through a custom unique External ID field.

  11. Relationship Types & Data Model Considerations Lookup • Loosely links two different objects and doesn’t effect deletion or security of records. • Are not automatically required • Data from one object can appear as a custom related list on another object • An object can be linked with itself Source: Focus on Force, Platform Developer 1 Course

  12. Relationship Types & Data Model Considerations Master-Detail • Closely links (tight relationship) two different objects and will delete detail or child records automatically when parent records are deleted. • Parent controls who can view the detail’s data. • The detail or child records get sharing and security settings from the master (parent) record. • Can be defined between 2 custom objects, or 1 standard and 1 custom object where the standard object is the master (parent). • Roll-up summary fields are supported by this type of relationship and can be created on the master object to summarize detail records. Source: Focus on Force, Platform Developer 1 Course

  13. Relationship Types & Data Model Considerations Many-to-Many • Links a record of one object to multiple records of another object and vice-versa with junction object. • Use Junction Object when a relationship linking 2 master-detail records together. • When records from either master-detail records are deleted, the records in the Junction Object are deleted as well. • Access to Junction Object records is controlled by a user’s sharing access to both of the master-detail records. • Roll-up summary fields are supported by this type of relationship and can be created on both master object to summarize data from the junction object. Source: Focus on Force, Platform Developer 1 Course

  14. Object Types & Supported Relationships Standard & CustomObjects • Lookup • Master-Detail • Many-to-Many • External Lookup • Indirect Lookup ExternalObjects • Lookup • Indirect Lookup UserObjects • Hierarchical Relationships

  15. Relationship Types & Implications Lookup • Cannot be used to link an object to itself when it is the User Object. • Related lists are added to the lookup object. • Access is independent from child to parent records. • Allow data from 2 related objects to be joined in 1 report. • Standard report types are created for each relationship. • Fields from this type of relationship can be added when creatinga custom report type.

  16. Relationship Types & Implications Master-Detail • Junction object sharing access is controlled by a user’s access to both object records, as well as on the sharing setting option on the relationship field. • When sharing setting is Read/Write on both master records, the user needs Read/Write to the junction object records. • When sharing setting is Read Only on both master records, the user needs to have Read Only to both in order to get Read/Write on the junction object records. • 2 standard report types are provided by this type of relationship which join the master records in the junction object.

  17. Relationship Types & Implications Many-to-Many • Junction objects sharing access is controlled by a user’s access to both master records, as well as the sharing setting option on the relationship field. • When sharing setting is Read/Write on both master records, the user needs to have Read/Write to both in order to get Read/Write on the junction object records. • When sharing setting is Read Only on both master records, the user needs to have Read Only to both to get Read/Write on the junction object records. • 2 standard report types are provided by this type of relationship which join the master records in the junction object.

  18. Data Model Scenario My organization is using nonprofit success pack to track accounts, contacts, opportunities, and campaigns. However, we also need to track facilities that our programs run out of and clinics that we run. What type of objects and fields does my data model require? Why?

  19. Data Model Scenario Can you provide an example of when a lookup relationship is needed?

  20. Data Model Scenario Can you provide an example of when a master-detail relationship is needed?

  21. Data Model Scenario Can you provide an example of when a many-to-many relationship is needed?

  22. Impact of Schema Design and Modifications on Apex When changes to objects and relationships are made we need to take into consideration what does that mean for Visualforce and Apex. • Custom objects referenced in Apex → cannot be deleted. • Any new objects and fields are accessible in Apex. • SOQL queries rely on data model and relationships. • Changes to schema relationships → means we have to make code modifications to reflect what we changes wemade to the schema relationships.

  23. Impact of Schema Design and Modifications on Apex When changes to fields are made we need to take into consideration what does that mean for Visualforce and Apex. • Custom fields referenced in Apex → cannot be deleted. • Data types of referenced fields → cannot be changed. • Some field changes can also change the logic in our code. • If we have required fields with missing values → It throwsan exception. • Changing roll-up summary fields can change what receive as output. • Changing length and decimal places → can cause data loss.

  24. How to Visualize & Create Entity Relationships Great exercise is on Trailhead called “How to work with schema builder”

  25. Schema Builder Limitations • Cannot create geolocations • Cannot create external lookup relationships • Cannot create indirect lookup relationships • Cannot create encrypted fields • Cannot create external objects • If you create custom objects from the object manager and not from within the Schema Builder tool, you will not automatically see those custom objects displayed

  26. Platform Developer I Certification Study Group Got questions?Unmute your line to speak or type into the chat box.

  27. Platform Developer I Certification Study Group *Schedule: June 28 – September 6, 2018 *Schedule was updated on 7/18/2018 Upcoming EventsWIT Success: July 27 - 28Forcelandia: August 8 - 9*

  28. PluralSight 30-Day Passes & Related Channels • Salesforce MVP 5x • Technical Educator & Certified Instructor • Pluralsight Producer, Author & Training Partner • Team Lead - mentoring worldwide in the cloud • Forcementor.comCourses in the Play By Play series are not structured towards or directed at any Salesforce certifications. Their design is primarily and intentionally informational, educational and expositional around real world challenges and topics.  Don Robins@donrobins

  29. Resources & Homework • Prepare for Your Salesforce Platform Developer I Credential • Badges listed under the “Salesforce Fundamentals” and the “Data Modeling & Management” task areas part of the trailmix linked above. • Add to our Study Group Resources Google Sheet for Flashcards • Please use hashtag #LBAjourneytoPD1 on social media 7/26/2018 Live Session Recording is available on YouTube

More Related