data modeling best practices in force.com

29
Data Modeling Best Practices in Force.com Mary Scotton Developer Evangelist salesforce.com @rockchick322004 Carolyn Adams VP of Client Services Outbox Systems @CarolynBAdams

Upload: mary-scotton

Post on 14-Apr-2017

1.984 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Data Modeling Best Practices in Force.com

Data Modeling Best Practices in Force.com Mary Scotton Developer Evangelist salesforce.com @rockchick322004

Carolyn Adams VP of Client Services Outbox Systems @CarolynBAdams

Page 2: Data Modeling Best Practices in Force.com

Data Modeling Best Practices in Force.com What is up with Standard & Custom Objects? Mary Scotton Developer Evangeist salesforce.com @rockchick322004

Carolyn Adams VP of Client Services Outbox Systems @CarolynBAdams

Page 3: Data Modeling Best Practices in Force.com

Safe Harbor Safe harbor 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.

Page 4: Data Modeling Best Practices in Force.com

Agenda • Overview • Modeling People • Modeling Events • Modeling Revenue • Modeling New Business Functions • Q&A

Page 5: Data Modeling Best Practices in Force.com
Page 6: Data Modeling Best Practices in Force.com

Custom Objects

You’re on your own

Standard Objects

Salesforce does the work for you

Page 7: Data Modeling Best Practices in Force.com

Consideration Standard Custom

Availability

•  All Salesforce instances

•  Platform Users: Accounts & Contacts only

•  Just your Salesforce instance

•  Platform Users: All custom objects

Relationships

•  Built-in relationships (e.g., Opp and Forecasts)

•  Can’t be the Detail object in a Master-Detail

•  More flexibility when adding fields and relationships

AppExchange

•  Consumer: Many extensions to standard objects

•  Publisher: All customers have standard objects

•  Consumer: Less apps available

•  Publisher: More control over the object behavior

Standard vs Custom Objects What are the differences?

Page 8: Data Modeling Best Practices in Force.com

Use to introduce a

demo, video, Q&A, etc. Use Case: Event Management

Mother-Son Bowling

Page 9: Data Modeling Best Practices in Force.com
Page 10: Data Modeling Best Practices in Force.com

Modeling People

Contacts

Mary & Noelani Scotton

Gabriel Scotton

Household Form # Custom Obj Accounts

Page 11: Data Modeling Best Practices in Force.com

Data Model: People

Contacts

Mary Scotton Noelani Scotton Gabriel Scotton

Accounts “1 household has many people”

Scotton Household

Page 12: Data Modeling Best Practices in Force.com

Accounts & Contacts Always use these. Always. Really.

• Salesforce1 Mobile App powers • Name & Address fields • Send an Email, Mass Email • Activities:

–  WHO (Contact, Lead) –  WHAT (Account, Custom Obj, others)

Page 13: Data Modeling Best Practices in Force.com

Modeling Events

PTA Events Activities (Events) Custom Obj Campaigns

Contacts

Page 14: Data Modeling Best Practices in Force.com

Data Model: Events

Contacts

Mary Scotton Noelani Scotton Gabriel Scotton

Campaign

“1 event has many attendees”

Campaign Member

“1 contact can attend many events”

Mary Scotton | MSBowling 2014 Noelani Scotton | MSBowling 2014 Gabriel Scotton | MSBowling 2014

MSBowling 2014

Page 15: Data Modeling Best Practices in Force.com

Campaigns & Campaign Members These make event attendee management easy.

• Start & End Date • Member Management • Built-in List View Filter on Contacts • Can populate them directly from reports (on Contacts or Leads, using Standard Report Types)

Page 16: Data Modeling Best Practices in Force.com

Use to introduce a

demo, video, Q&A, etc. Demo

Mother-Son Bowling

Page 17: Data Modeling Best Practices in Force.com

Place Customer or

Partner logo in white area of

slide, centered horizontally

Carolyn Adams VP of Client Services

Page 18: Data Modeling Best Practices in Force.com

Use to introduce a

demo, video, Q&A, etc.

Use Case: Managing Recurring Revenue in Salesforce From Bookings, to Scheduled Revenue, to on-going Asset management

Page 19: Data Modeling Best Practices in Force.com

What is Recurring Revenue? Is my company in a recurring business model?

Examples: • Subscription-based Products (software licenses)

• Recurring Services (support plans, maintenance contracts, retained professional services)

New Business

Page 20: Data Modeling Best Practices in Force.com

Modeling Recurring Revenue How do I manage my recurring business?

Managing a recurring revenue model brings a lot of questions:

• Where do we track current versus expired subscriptions?

• How do we quote subscriptions, especially on a line-by-line basis (i.e. individual devices or memberships)?

• What is the process for upgrades and add-ons? • How can sales stay on top of the upcoming renewals?

Page 21: Data Modeling Best Practices in Force.com

Data Model: Recurring Revenue Let’s stick to out-of-the-box functionality

Opportunities can have product lines attributed to them so you know what is being sold.

Those lines can be scheduled to be fulfilled over time.

Those products and schedules can update Assets on the Account which represent the customer’s full portfolio of products owned.

Accounts

Opportunities

Opportunity Products

Product Schedul

es

Assets

Page 22: Data Modeling Best Practices in Force.com

Use to introduce a

demo, video, Q&A, etc. Demo

Product Schedules

Page 23: Data Modeling Best Practices in Force.com

Would custom objects work for recurring revenue?

• Yes However, they have limited customizations (e.g., can’t add custom fields or customize the related list)

*Recurring Revenue in Salesforce is ingrained in many other aspects *Deviating from the standard functionality will limit your Salesforce potential

–  Limit ability to use other standard features: forecasting, etc. –  Can’t use AppExchange packages that rely on standard objects –  You’re off the release train…

*

Page 24: Data Modeling Best Practices in Force.com

Use to introduce a

demo, video, Q&A, etc. Use Case: New Business Function

OK, now it’s a good time for custom objects

Page 25: Data Modeling Best Practices in Force.com

Modeling New Business Functions Yes, this is a good time to create custom objects

•  Projects •  Invoices •  Job Openings •  Expenses •  Surveys •  Proposal Forms (RFP’s)

Page 26: Data Modeling Best Practices in Force.com

Use to introduce a

demo, video, Q&A, etc. Extra Credit

Adding more power to your data model

Page 27: Data Modeling Best Practices in Force.com

Record Types FTW !

• Create subcategories for your data

• Allow different views, processes & picklists for different records

• Only available in Enterprise Edition and above

Page 28: Data Modeling Best Practices in Force.com

Rename Tabs and Labels

• Make standard objects match your business terminology

• Supports all (supported) languages

• WARNING: Does not change object names in Setup (confusion may and will occur)

Page 29: Data Modeling Best Practices in Force.com

Mary Scotton Developer Evangeist salesforce.com @rockchick322004

Carolyn Adams VP of Client Services Outbox Systems @CarolynBAdams