Data Modeling Made Easy by Selina Suarez, Tal Gozhansky & Wes Weingartner
•Download as PPTX, PDF•
0 likes•142 views
This document provides an overview and best practices for data modeling. It includes information about: - Forward-looking statements and risks associated with projections - Introductions of the authors and their roles at INVISR - Tips for scoping requirements such as capturing entities before relationships and expecting to design models offline - Examples of different types of relationships like one-to-many, lookups, and hierarchical relationships - Tips for determining when a lookup versus joiner object is needed based on flexibility required - Examples of standard and custom joiner implementations
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Data Modeling Made Easy by Selina Suarez, Tal Gozhansky & Wes Weingartner
Similar to Data Modeling Made Easy by Selina Suarez, Tal Gozhansky & Wes Weingartner (20)
More from Salesforce Admins
More from Salesforce Admins (20)
Recently uploaded
Recently uploaded (20)
Data Modeling Made Easy by Selina Suarez, Tal Gozhansky & Wes Weingartner
- 1. Data Modeling Made Easy Best Practices and Helpful Tips hello@invisr.com @teamINVISR Tal Gozhansky, Wes Weingartner, Selina Suarez INVISR
- 2. Forward-Looking Statements Statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
- 5. Selina Suarez @SelinaSFDC Director, Edtech Products INVISR
- 7. “Listen, and take notes!” - Said Someone
- 8. Top Scoping Tips Take notes efficiently and accurately Capture “entities” before relationships Understand the business Expect to design “Offline”
- 10. One to Many Lookup Master-Detail Hierarchical Many to Many Not supported natively in Salesforce Requires Joiner Object One to One Not supported natively in Salesforce
- 11. “Will a lookup give you enough flexibility?”
- 12. Examples
- 13. One-to-Many – Standard Salesforce One Account has many Contacts
- 14. Joiners – Simple / Custom Many different Cases can be linked to many different Bugs
- 15. Joiners – Standard Salesforce Many different Users can be linked to many different Accounts
- 16. Joiners – More Complex Many students apply to many different colleges *Each app is tailored
- 17. Joiners – Even More Complex WOAH! • Referral • Loan Relationship • Application • Application Member is a joiner hooked up to another joiner!
- 18. Single-Source Referrals vs Multi-Source Referrals
- 19. Q & A
- 20. Thank Y u
Editor's Notes
- Key Takeaway: We are a publicly traded company. Please make your buying decisions only on the products commercially available from Salesforce. Talk Track: Before I begin, just a quick note that when considering future developments, whether by us or with any other solution provider, you should always base your purchasing decisions on what is currently available.
- 30 second intro by Wes
- Master-Detail is a special type of lookup 1) Cascade Delete 2) Rollup Summaries 3) Mandatory Hierarchical is only available on User Object.
- 20 seconds
- 1 minute
- 30 seconds
- You could add % and other attributes to the referral object without working very hard and creating lots of new fields. Etc…
- Remaining Time