0 comments on “Working with Large Data and Transaction Volumes”

Working with Large Data and Transaction Volumes

This is mostly about improving performance. If there is large data or transaction volume, it can impact: reports/dashboard performance, import speed, search speed, sharing rules performance, list views.

In order to optimise performance you can:

  • Create custom indexes to speed up queries and reports
  • Use mashups to show data stored in external systems as if in Salesforce
  • Large volumes of data can be segmented with divisions 
  • Skinny tables (?) can improve system performance
  • Change sharing rules off work hours so as not to affect user experience
  • Use report filters to improve performance
  • Use bulk API/asynchronous parallel processing when loading large data volumes (avoid governor limits?)
  • Archive records not being used
0 comments on “Data Migration”

Data Migration

Data migration process:

  1. Identify stakeholders. Create data map for them, communication with them is important.
  2. Data analysis. Identify data to be migrated, correct approach for migrating data, whether it requires cleaning, how it should be stored in Salesforce.
  3. Data and system preparation. Data cleaned and converted in CSV files. Order of migration considered. Customise meta-data in Salesforce where required.
  4. Data migration testing. Test data migration in sandbox. First with a subset of data then full migration of data. Identify and rectify any hiccups.
  5. Data migration and validation. Create backup of existing data in production. Migrate data into production. Check data with various users to validate it. Communicate with stakeholders.

Data Import Wizard vs Data Loader. Depends on the size of import and the objects involved. Generally, Import Wizard is preferable but Data Loader can support more?

Migration order of objects:

  1. Users
  2. Accounts
  3. Contacts
  4. Opportunities
  5. Products
  6. Product Line Items
  7. Cases
  8. Leads
  9. Campaigns
  10. Campaign Members
  11. Contracts
  12. Assets
  13. Solutions
  14. Custom Objects
  15. Activities


0 comments on “Integration Patterns with External Systems”

Integration Patterns with External Systems

This post details some common integration patterns. An integration pattern is the way of integrating Salesforce with external systems. Sales Cloud integration patterns include:

  • Asynchronous update
  • Real-time update
  • Batch data synchronisation
  • Remote update
  • User interface update
  • Mashup

Batch data synchronisation. This is where certain changes in Salesforce or an external are exported into the other, on a regular basis such as weekly or nightly. It has the benefit of not disrupting operations during business hours.

Real-time update. As the name suggests, this happens in real time. Changes are made in Salesforce or an external system, upon the request of the other. For example at the click of a button. Waits for a response back: “request and reply”.

Asynchronous update. Similar to above but doesn’t doesn’t wait for a response back: “fire and forget”.

Remote update. An external system can access Salesforce through the use of APIs and query, update or update records in Salesforce. Can access metadata.

User Interface Update. Events in Salesforce trigger real-time updates in user interface of external system. Doesn’t require screen refresh (which might lose unsaved work). For example use to notify a Sales manager in external system when a deal is clsoed.

Mashup. Make things connected to external systems look like they’re part of Salesforce.


0 comments on “Sales Cloud Analytics”

Sales Cloud Analytics

Five main options: standard reports, custom reports, reporting snapshots, app exchange dashboards and historical trend reporting.

Standard sales reports:

  • Active, neglected or new accounts/contacts
  • Opportunity reports
  • Lead reports (how long to respond, neglected leads etc)
  • Forecast reports
  • Campaign reports

Custom sales reports and dashboards

Reporting snapshots

  • Report on historical data
  • Saves to a custom object

AppExchange sales dashboards

  • Marketing executive dashboard
  • Sales executive dashboard
  • Sales manager dashboard
  • Salesperson dashboard

Historical trend reporting

  • Highlight changes between five snapshot dates
  • Day-to-day or week-to-week trends

Some common sales metrics:

  • Sales by lead source
  • Total closed opportunities
  • Revenue per sale
  • Percentage of leads converted
  • Win rate

Impact of Multi-Currency on Sales Analytics:

  • Amounts in reports can be shown in any active currency
  • The primary currency reflects either the default corporate currency or the record currency
  • The secondary currency reflects either the user’s default currency or the currency in the filter criteria
  • Dashboards just use the currency that the report uses
  • Converted column shows user’s currency by default but can be changed (how is this different to secondary currency?)
0 comments on “Use Cases and Considerations of Communities and Sites”

Use Cases and Considerations of Communities and Sites

Customer Community:

  • Customers share experiences
  • Provided access to their data
  • Find information about products
  • Sales reps can refer customers to the community
  • Give customers access to knowledge base

Partner Community:

  • Helps partners collaborate with employees
  • Manage opportunities
  • Gain access to leads
  • Register deals in the works (this can be useful to know)
  • Onboarding
  • Create quotes
  • Reports and dashboards

Employee Community

  • Employees can ask questions
  • Collaborate with sales reps
  • Access to knolwedge base and training materials
  • Accessed by mobile
  • Payroll, benefits information etc can be made available

Ideas Community

  • Post, vote for and comment on ideas
  • Allows outsiders to see innovation
  • Add or subtract 10 points if someone votes on idea
  • Groups of ideas called zones

Force.com Sites

  • Display Salesforce data in a branded, public website

Considerations of Communities

  • Once enabled, can’t be disabled
  • Community builder vs workspace?
  • Contact records are assigned as community users by assigning them a license
  • Access communities through the global header or the app launcher
  • Create communities from templates
0 comments on “How to Drive and Measure Sales Cloud Adoption”

How to Drive and Measure Sales Cloud Adoption

How to drive adoption?

  • Training is very important for driving adoption
  • Give users access to certain reports and dashboards
  • Utilise automation capabilities to make their jobs easier (when using Sales Cloud)
  • Improve data quality
  • Gamification and rewards
  • Adoption evangelists

How to measure adoption?

  • Metrics related to usage, data quality and business performance
  • Administrative reports to identify users who have been logging in
  • Measure usage of key Sales Cloud objects
  • Salesforce adoption dashboards
  • Business performance measures
2 comments on “Tools for Driving Sales Productivity”

Tools for Driving Sales Productivity

Salesforce1 has many tools which can drive productivity:

  • Access to records
  • Lead conversion
  • Quick Actions
  • Chatter
  • Approvals
  • Access reports and Dashboards

Email productivity tools:

  • Email integration tools such as lightning for outlook/Gmail
  • Lightning sync contacts and events can be synced between email and Salesforce
  • Can access certain records related to emails directly from email
  • E-mail to Salesforce allows emails from external email apps to be related to certain Salesforce records
  • Email templates and mail merge
  • Mass emails

Chatter tools:

  • Follow records
  • Groups
  • Publisher actions (post, poll, files, questions)
  • @Mentions
  • Private messages

Work.com tools:

  • Feedback
  • Goals
  • Recognition
  • Skills
  • Coaching
  • Rewards

Content vs Chatter Files