Here is a great solution by Chris Bonacore

Some of you have asked for details on importing attachments via the Data Loader so I thought it may help for everyone.

If you want to migrate from one org to another, then you first need to get a Weekly Export Service download.  Make sure you check the "Include attachments" box. You will get an attachments.csv and the actual attachments.

The key to importing attachments is a little known feature inside Data Loader. The part that is not documented is that the import wants the actual filename in the BODY field. So for example, the attachments themselves have a ID name, let's say its 123456789 and it is on your hard drive in the C:\Export folder. So in the BODY field you need to put C:\Export\123456789.

Here is a great solution by Chris Bonacore

Some of you have asked for details on importing attachments via the Data Loader so I thought it may help for everyone.

If you want to migrate from one org to another, then you first need to get a Weekly Export Service download.  Make sure you check the "Include attachments" box. You will get an attachments.csv and the actual attachments.

The key to importing attachments is a little known feature inside Data Loader. The part that is not documented is that the import wants the actual filename in the BODY field. So for example, the attachments themselves have a ID name, let's say its 123456789 and it is on your hard drive in the C:\Export folder. So in the BODY field you need to put C:\Export\123456789.

There’s a great post on the message boards about adding products to a standard price book using Ron Hess’s Excel Sforce Connector.

The highlights are below but you can also click here to read the full thread.

To add products to the Standard Price Book, you have to add entries to the 'PricebookEntry' table.

The table contains three id fields:
Price Book Entry ID
Price Book ID
Product ID

The Pricebook ID is of the Standard Price Book which you can get from querying the Pricebook2 table. The Product ID is of the Product you want to add and you can get that from the Product2 table. The Pricebook Entry ID value is 'new'.

Fill out the rest of the table as needed (List Price, Active, Use Standard Price, Currency). If you need a product with 2 currencies, add the product again to the PriceBook Entry book and just change the currency field.

There’s a great post on the message boards about adding products to a standard price book using Ron Hess’s Excel Sforce Connector.

The highlights are below but you can also click here to read the full thread.

To add products to the Standard Price Book, you have to add entries to the 'PricebookEntry' table.

The table contains three id fields:
Price Book Entry ID
Price Book ID
Product ID

The Pricebook ID is of the Standard Price Book which you can get from querying the Pricebook2 table. The Product ID is of the Product you want to add and you can get that from the Product2 table. The Pricebook Entry ID value is 'new'.

Fill out the rest of the table as needed (List Price, Active, Use Standard Price, Currency). If you need a product with 2 currencies, add the product again to the PriceBook Entry book and just change the currency field.

Update: We have created a new discussion board to discuss this product:The Excel Connector Discussion. The AppExchange Data Loader is another tool that is helpful when doing similar tasks.

---

For those of you who haven’t discovered the Sforce Excel Connector built by Ron Hess, it’s a fantastic open source tool.

The connector allows you to import records from Excel directly into Salesforce.com. It also allows you to perform mass updates which can be very handy for data cleansing projects.

The Sforce Connector uses the API and is therefore only available to Enterprise Edition Customers. While this tool is easy to install and easy to use, you need to be careful anytime you’re manipulating large amounts of live data. Click on the links below to learn more.

Excel Sforce Connector | Best Practice Presentation by Ron Hess | The Excel Connector Discussion

Update: We have created a new discussion board to discuss this product:The Excel Connector Discussion. The AppExchange Data Loader is another tool that is helpful when doing similar tasks.

---

For those of you who haven’t discovered the Sforce Excel Connector built by Ron Hess, it’s a fantastic open source tool.

The connector allows you to import records from Excel directly into Salesforce.com. It also allows you to perform mass updates which can be very handy for data cleansing projects.

The Sforce Connector uses the API and is therefore only available to Enterprise Edition Customers. While this tool is easy to install and easy to use, you need to be careful anytime you’re manipulating large amounts of live data. Click on the links below to learn more.

Excel Sforce Connector | Best Practice Presentation by Ron Hess | The Excel Connector Discussion

For the past several months salesforce.com has been traveling the country holding local events where customers speak about what’s made their CRM implementation a success. Today at the city tour event in New York, Rob Grossberg, the VP of Sales Operations at DoubleClick was presenting and he put the following quote on the screen.

The thought is that if you can transform your culture into this mindset; collaboration takes off, data quality improves, and executives have newfound visibility into their business.

This theme has become so pervasive amongst successful salesforce.com customers than when John Merrill from Cablevision saw the quote he turned to the person sitting next to him to say, “That’s on my presentation too.”

If your organization lives by a similar saying we'd love to hear how it's changed the corporate culture. To tell your story, add a comment below.

Download the image for your PowerPoint presentation

For the past several months salesforce.com has been traveling the country holding local events where customers speak about what’s made their CRM implementation a success. Today at the city tour event in New York, Rob Grossberg, the VP of Sales Operations at DoubleClick was presenting and he put the following quote on the screen.

The thought is that if you can transform your culture into this mindset; collaboration takes off, data quality improves, and executives have newfound visibility into their business.

This theme has become so pervasive amongst successful salesforce.com customers than when John Merrill from Cablevision saw the quote he turned to the person sitting next to him to say, “That’s on my presentation too.”

If your organization lives by a similar saying we'd love to hear how it's changed the corporate culture. To tell your story, add a comment below.

Download the image for your PowerPoint presentation

Salesforce.com supports importing of Accounts through its import wizard. During this process it can associate accounts in a hierarchical relationship by matching a parent account name in the import file to an existing account. However, frequently data is linked in other systems using another relationship e.g. an id and parent id field. In this situation, there is no easy way to make the import wizards set up the hierarchy correctly.

A solution is to run the import without mapping the parent account name and then updating the records in Salesforce after the import. In order for the update to occur, you must import the extra fields which link the accounts. These values can be stored in standard fields such as ACCOUNT_NUMBER and SIC_CODE or into custom fields.  

Once the data is imported, the update can be performed. One quick and easy way to do this is using Excel and the Sforce connector for Excel. The steps are:

1/ Run an Account query using the connector to retrieve all accounts

2/ Use the Excel VLOOKUP function to populate the parent account according to your preference

3/ Update the Accounts back to Salesforce using the connector update 

The hardest part of making this work is understanding the VLOOKUP function. The documentation in Excel for this function is fairly clear but here is an example

=IF(ISERROR(VLOOKUP(D5,A:B,2,FALSE)),"",VLOOKUP(D5,A:B,2,FALSE)) 

The core of this function is the VLOOKUP(D5,A:B,2,FALSE) expression. This means find the value in D5 in the A column and, if a match is found, return the value in B5. As you paste this function into other rows, the relative references will update i.e. D5 becomes E5

Sometimes this function will not return a match and then returns an error which breaks the Salesforce update. The solution is to enclose the VLOOKUP with an ISERROR check so that a non-match will return the empty string and this then updates the Salesforce field correctly. 

This is a fairly simple example where the hierarchy is controlled by separate ids but it can be extended to implement any relationship. Happy importing…

Steve Buikhuizen | Sales Engineer | Salesforce.com Asia Pacific

Salesforce.com supports importing of Accounts through its import wizard. During this process it can associate accounts in a hierarchical relationship by matching a parent account name in the import file to an existing account. However, frequently data is linked in other systems using another relationship e.g. an id and parent id field. In this situation, there is no easy way to make the import wizards set up the hierarchy correctly.

A solution is to run the import without mapping the parent account name and then updating the records in Salesforce after the import. In order for the update to occur, you must import the extra fields which link the accounts. These values can be stored in standard fields such as ACCOUNT_NUMBER and SIC_CODE or into custom fields.  

Once the data is imported, the update can be performed. One quick and easy way to do this is using Excel and the Sforce connector for Excel. The steps are:

1/ Run an Account query using the connector to retrieve all accounts

2/ Use the Excel VLOOKUP function to populate the parent account according to your preference

3/ Update the Accounts back to Salesforce using the connector update 

The hardest part of making this work is understanding the VLOOKUP function. The documentation in Excel for this function is fairly clear but here is an example

=IF(ISERROR(VLOOKUP(D5,A:B,2,FALSE)),"",VLOOKUP(D5,A:B,2,FALSE)) 

The core of this function is the VLOOKUP(D5,A:B,2,FALSE) expression. This means find the value in D5 in the A column and, if a match is found, return the value in B5. As you paste this function into other rows, the relative references will update i.e. D5 becomes E5

Sometimes this function will not return a match and then returns an error which breaks the Salesforce update. The solution is to enclose the VLOOKUP with an ISERROR check so that a non-match will return the empty string and this then updates the Salesforce field correctly. 

This is a fairly simple example where the hierarchy is controlled by separate ids but it can be extended to implement any relationship. Happy importing…

Steve Buikhuizen | Sales Engineer | Salesforce.com Asia Pacific

If you have Enterprise Edition, you could use the sforce Connector to do this type of transfer.

Say Ralph1 and Bob2 were the original sales team, with Ralph1 the primary one. Now they've been replaced with Mary1 and Sue2. The reassignment of accounts from Ralph1 to Mary1 could also transfer all the contacts owned by Ralph, in his accounts, to Mary. You're left with some other contacts owned by the old Bob2.

You could produce a report of contacts owned by Bob2 (possibly limited to accounts owned by Mary1). Then change the owner of these contacts to either Mary or Sue, as desired. The change is done by overlaying the Bob2 ownerid with Mary1, highlighting these cells, and requesting "Update selected cells". -Scot

http://forums.crmsuccess.com/sforce/board/message?board.id=discuss&message.id=620#M620

If you have Enterprise Edition, you could use the sforce Connector to do this type of transfer.

Say Ralph1 and Bob2 were the original sales team, with Ralph1 the primary one. Now they've been replaced with Mary1 and Sue2. The reassignment of accounts from Ralph1 to Mary1 could also transfer all the contacts owned by Ralph, in his accounts, to Mary. You're left with some other contacts owned by the old Bob2.

You could produce a report of contacts owned by Bob2 (possibly limited to accounts owned by Mary1). Then change the owner of these contacts to either Mary or Sue, as desired. The change is done by overlaying the Bob2 ownerid with Mary1, highlighting these cells, and requesting "Update selected cells". -Scot

http://forums.crmsuccess.com/sforce/board/message?board.id=discuss&message.id=620#M620

A recommendation I wanted to share on a best practice for Opportunity Naming is that you include the Account Name in the Opportunity naming. An example would be:

"Account Name"-"Opportunity Identifier"

The Opportunity Identifier would be something that would help identify what this specific deal is for (i.e., product name + quantity, order date, service name). So your Opportunity Name might look something like:

Company A - 20 Widgets
Company A - June Order

The reasons why this is recommend are as follows:

Multiple Opportunities: if you have more than one opportunity with an account (i.e., 2004 order/2005 order, product a/service a) you will literally have to click into each Opportunity to find the information about it to understand what it is for

Search and Navigation: if you look on your recent items tab, and you name your Opportunities by product/service only, you will see a bunch of Opportunities named the same, and will not be able to easily find the one you are looking for

Reporting: for Summary and Matrix reports, you have a limited number of “Group By” options (3 on Summary Reports, 2 on Matrix reports). This is more relevant for Matrix reports, if you wanted to see Pipeline by Rep, Account and Opportunity – or Rep, Account, Product … you can’t. With only two Group By filters, you won’t be able to display all this information on one report

Forecast: the forecast tab displays the Opportunity name only, so in order to know which deal is which, you will have to click into each, unless of course you can identify which is which by the Opportunity Name

Lead Conversion: when converting a Lead record, the system defaults the Opportunity Name to be created to “(Account Name)-“, helping you enforce this type of naming convention.

View Post

A recommendation I wanted to share on a best practice for Opportunity Naming is that you include the Account Name in the Opportunity naming. An example would be:

"Account Name"-"Opportunity Identifier"

The Opportunity Identifier would be something that would help identify what this specific deal is for (i.e., product name + quantity, order date, service name). So your Opportunity Name might look something like:

Company A - 20 Widgets
Company A - June Order

The reasons why this is recommend are as follows:

Multiple Opportunities: if you have more than one opportunity with an account (i.e., 2004 order/2005 order, product a/service a) you will literally have to click into each Opportunity to find the information about it to understand what it is for

Search and Navigation: if you look on your recent items tab, and you name your Opportunities by product/service only, you will see a bunch of Opportunities named the same, and will not be able to easily find the one you are looking for

Reporting: for Summary and Matrix reports, you have a limited number of “Group By” options (3 on Summary Reports, 2 on Matrix reports). This is more relevant for Matrix reports, if you wanted to see Pipeline by Rep, Account and Opportunity – or Rep, Account, Product … you can’t. With only two Group By filters, you won’t be able to display all this information on one report

Forecast: the forecast tab displays the Opportunity name only, so in order to know which deal is which, you will have to click into each, unless of course you can identify which is which by the Opportunity Name

Lead Conversion: when converting a Lead record, the system defaults the Opportunity Name to be created to “(Account Name)-“, helping you enforce this type of naming convention.

View Post

Preparing and Improving Data Quality
Phil Barker  (salesforce.com), Carol Parker (Orange), Jodi Hrbek (Protivity)

Filtering Out Dirty Data
Phil Barker (salesforce.com), Chris Badger (Inside Scoop), Trevor Wilmont (Sirva)

Filtering Out Dirty Data (R)
Phil Barker (salesforce.com), Glenn Wilson (CRMfusion), Theresa DeRycke (salesforce.com)

Naming Convention Best Practices
This worksheet provides guidelines for corporate names and abbreviations so you can establish consistent data which will help with searching and reporting....

Below are three partner solutions that I'd highly recommend for imporving data quality.

Data Quality: Inside Scoop

Mass Update: Demand Tools

Lead De-Dupe: Ringlead

 

View All Data Services / Data Quality Partners

Preparing and Improving Data Quality
Phil Barker  (salesforce.com), Carol Parker (Orange), Jodi Hrbek (Protivity)

Filtering Out Dirty Data
Phil Barker (salesforce.com), Chris Badger (Inside Scoop), Trevor Wilmont (Sirva)

Filtering Out Dirty Data (R)
Phil Barker (salesforce.com), Glenn Wilson (CRMfusion), Theresa DeRycke (salesforce.com)

Naming Convention Best Practices
This worksheet provides guidelines for corporate names and abbreviations so you can establish consistent data which will help with searching and reporting....

Below are three partner solutions that I'd highly recommend for imporving data quality.

Data Quality: Inside Scoop

Mass Update: Demand Tools

Lead De-Dupe: Ringlead

 

View All Data Services / Data Quality Partners

CRM can add significant value to an organization, but many implementations fail due to a few basic mistakes. This presentation addresses ten of the most common pitfalls companies face and provides guidance to help ensure your CRM rollout is a success.

This presentation is available in Breeze (13 mins), PowerPoint and PDF format.

CRM can add significant value to an organization, but many implementations fail due to a few basic mistakes. This presentation addresses ten of the most common pitfalls companies face and provides guidance to help ensure your CRM rollout is a success.

This presentation is available in Breeze (13 mins), PowerPoint and PDF format.

Strong user adoption is critical for any CRM initiative because it directly impacts collaboration, data quality, and executive reporting. This presentation presents techniques for administrators and executive sponsors to help them drive adoption across their organizations. 

This presentation is available in Breeze (9 mins).

Strong user adoption is critical for any CRM initiative because it directly impacts collaboration, data quality, and executive reporting. This presentation presents techniques for administrators and executive sponsors to help them drive adoption across their organizations. 

This presentation is available in Breeze (9 mins).

Administrators need to find tangible metrics to help monitor and improve user adoption across their organizations. This presentation shows you how to set up dashboards in salesforce.com to track user logins, call activity, and data quality. 

This presentation is available in Breeze (8 mins).

Administrators need to find tangible metrics to help monitor and improve user adoption across their organizations. This presentation shows you how to set up dashboards in salesforce.com to track user logins, call activity, and data quality. 

This presentation is available in Breeze (8 mins).