C5 Insight: Salesforce - Technical

Check-out our on-demand events at C5Tube.com

Sat, 26 May 2012 00:00:00 +0000

Available 24/7, watch on-demand events about Microsoft SharePoint, Dynamics CRM, and Salesforce at C5Tube.com and check successaccelerators.com often for updated events and webcasts.

Application Data Integration – Part Three, Timing and the Rules

Tue, 03 Apr 2012 18:00:00 +0000

This is my third blog in a series concerning data integration. In my first two blog entries we overviewed some of the data integration hurdles as well as some of the common methods used to discover the net-change data that will need to be translated. Here in my third blog I’ll discuss some of the benefits of not integrating in real-time, but creating a batch job to perform the integration. We’ll also look at the Business Rules that may need to be applied within the integration process.

They say ‘timing is everything’. I don’t necessarily agree that it’s everything, but it is an important ingredient in the design of your integration. It’s always my first reaction to go ‘real-time’ with an integration project. Scoping and requirements gathering will then bring me to a place where a part of the integration may not work designed to run as real-time. Every business is built on processes that serve them well, or at least served them well back in the day. There are times when transaction volume will preclude using real-time methods for translation. Running the process, because of the volume, may have such an impact on the system, that user can not tolerate the sluggishness of the system during business hours. Perhaps there is a business process that does not make data available until after business hours. There can be any number of business process scenarios that would dictate utilizing a batch integration process rather than a real-time integration process.

Business processes are not the only consideration when designing your integration. The environment, and specifically the hardware that the integrated systems reside on, can play a key role in determining the integration process to use. For example, if your integration design requires polling a record set for the net-change data, that polling can effect performance. But to a greater extent, the record set that is returned will typically populate any RAM that is available, and if there is not enough RAM to hold the entire return record set, then it will occupy static drive space. Depending on how large the net-change record set is, that’s been returned, stealing all available RAM can seriously impact performance of the system. Conversely, you may have designed a multi-threaded integration process, such as utilizing a message queue as a pickup point for the extracted net- change data. Where running a multi-threaded process, you are able to translation a larger volume of data in a shorter period of time, but, that process will be very CPU intensive.

So, when developing your integration design, keep in mind that batch processing is memory intensive and multi-threaded processes are CPU intensive. Depending on the environment you’re working in, you may have the inclination to build one type of integration process, but the impact of that process would be too costly in terms of system performance and end-user satisfaction.

Ok, so you have one part of your integration setup, great. You’re integrating customers from your CRM system to your ERP system, fantastic. You turn on the integration, and not too long afterward, folks from the finance group are complaining that there are customers in ERP that don’t belong in the system. “What’d?, you say. I thought you wanted customers integrated in both system?”. The response from finance is that some of these aren’t customers, they are only prospects. Ah, so not all customers are the same in the CRM system.

This is a very typical scenario. The CRM system breaks down ‘customers’ into different customer types. Only ‘customers’ that have actually bought something are to be integrated into the ERP system. So, you need to be able to filter records in order to meet the requirements of this business rule . That filtering can take place in two different places, a) at the time of discovery of the net-change data or, b) during the translation process of the net-change data. If you have used a query to discover the net-change data, you may only need to add something to the WHERE clause of the query, to ensure that only records that meet the business rule criteria are discovered. If the application has it’s own net-change method, but cannot be modified to filter the records, you will need to build the filtering into the translation process rather than in the discovery process. There can, however, be some advantages to filtering at the integration process level. Let’s say that you only want purchasing customers being integrated into you ERP system, but you would like to see an aggregated view of all new customers that have been added to the either system. When you filter out the customers at the translation point rather than the discovery point, you have the records discovered in the net-change process, so, the entire record set can be used to create customer, by type, reporting.

Another. more complex example would be; sales orders being placed in the ERP system and then translated to one of several warehouse systems for processing. In this case, you not only have to filter the record set, but you also have to determine what translation processes will be used to ensure the sales order record is consumed by the correct warehouse system. As you can see, business rules will have a huge impact on how you might design your integration process. The entire solution may incorporate many different net-change discovery methods as well as many different data translation methods. Don’t get caught building a useless solution, wasting time and money. Dig deep into the requirements in order to develop the best integration processes for the given scenario your are working under.

As promised, this series is intended to be somewhat high level, but, I hope through some of the topics covered you have become a little more familiar with Application Data Integration. It can be tricky stuff to get your hear around; there are a lot of issues to consider. Not digging deep enough for the requirements can be very costly, not only monetarily, but also with adoption by your end-users if your integration is tied to a new business system implementation. Knowledge is power, so I hope I’ve charged your batteries a little.

Application Data Integration – Part Two, Net-Change

Wed, 28 Mar 2012 22:30:00 +0000

In my previous blog focusing on the hurdles of real-time, two-way data integration, I highlighted the hurdle of how to discover the data you need translated. In most cases, discovering the net-change data is all you want to translate on a real-time basis. Remember, a two-way integration means net-change data going in two directions or more (depending on the number of systems you’re integrating) at a rate determined by how many end-users there are on each of the systems being integrated. Business systems with a significant amount of end-users can create substantial volumes of net-change data.

In order to manage the volume of data flowing between systems, you must choose a net-change model to discover just the data that needs to translate. There are traditionally four basic models to choose from, one of which will discover the net-change data. They are not all equal though, so choosing will depend somewhat on the system(s) you’re working with and somewhat depend on the data model of the system(s) with which you’re working.

The four methods are as follows, in best practice order:

Application Method – this method is the most reliable and system efficient. It relies on the system, or application, to find the net-change data and produce it in a format that is easily translated and consumed by other systems. Some of the advantages of the Application Method are;
a) It typically can support deletes. In other words, records deleted by end-users can be traced to the other integrated systems, and if the business rules permit, will delete those records as well.
b) It is more likely to produce the net-change data in the order in which it was changed. This could become important if the net-change data is being produced in logical but separate extracts. One example would be if the system that is producing the net-change data, splits a sales order into a header file and a detail file. The consuming system will likely have referential integrity rules that would not allow details to be consumed before the header.
c) It has, typically, very little impact on the producing system, providing an un-noticeable effect to the end-users.
d) Reliability is a key factor. If the application is running, then net-change is being discovered and made consumable for other systems.
Tracker-Table Method – Also known as the shadow table method, the tracker-table method is somewhat invasive, but is very useful in cases where the data model does not always supply a last modified date/time stamp on each record. The tracker-table method does just what it says, it tracks the records that have had a change made to them. It is invasive because it requires creating objects in the database of the system. The idea being, create a table with at least three columns (ObjectName, RecordId,ChangeType). This is the tracking table. Then, place triggers on the tables which you are interested in seeing the net-change. The triggers are designed to modify the tracker-table in the following ways;
a) If there is an insert on the table (a new record created), the trigger will add a record to the tracker-table with three values; 1 - the table name where the changes came from, 2 – the recordId that was created when the record was committed, 3 – an identifier of the type of action that was performed (i.e. I = insert, U = update, D = deleted).
b) If there is an update made on the table, the trigger will search the tracker-table to find the ObjectName/RecordId that corresponds to the record that was updated. When the match is made, the trigger then adds a ‘U’ to the ChangeType column indicating that the record corresponding to the recordid in the tracker-table, has been updated..

Now that the net-change has been identified in the tracker-table, a mechanism needs to be developed (or a third-party tool employed i.e. Scribe or Informatica), to poll the tracker table for records with an ‘I’, ‘U’ or ‘D’, then join the recordid to the base table and retrieve the record that was changed. Once retrieved, set the ‘ChangeType’ in the tracker table back to NULL. Then simply choose the frequency that you want to poll the tracker–table for ‘I’, ‘U’ or ‘D’.
Last Update Date Method – This method is non-invasive and can be as reliable as the Application and Tracker-Table methods. With this method you simply create a mechanism (or a third-party tool employed i.e. Scribe or Informatica) to poll the data-object for records that are new, or have an last update date/time stamp that is greater than the last time you polled the data-object. There are a few other caveats to the WHERE clause but, essentially that’s all there is to it. Here’s the kicker. The reason that this method is 3rd in the best-practice ranking is because it is dependent on the clocks being used in the comparison, being synchronized. If for some odd and perplexing reason one of your applications is getting it’s date/time from the desktop clock (or some other unreliable source), you would most likely end up with records falling through the cracks. You must make sure the clocks you are using to compared and stamp are reliable.
Comparison Method – If you must discover your net-change records, and none of the first three methods can be applied, this may be your last option. The Comparison Method (or snapshot method) consists of making a copy of the recordset in which the net-change data resides. Then at some point after that first copy, take another copy of the object and compare each row/column for the differences. This is an extremely laborious method, but at times, desperate men must do desperate things.

Lastly, what to do with concurrent updates to a record. End-user #1 in sales, opens John Smith’s contact record to add a new cell number. At the same moment End-user #2 in finance, opens John Smith’s record to update the billing address. With applications like Dynamics CRM, Salesforce and SharePoint, the application logic will manage the concurrent changes and will make sure both are recognized and able to be discovered as net-change, and translated. Other than that, it’s the ‘last out wins’ method.

In my next post in this series, we’ll take a look at working the business process rules and application rules, into the integration process, and, at what frequency should the integration run.

Application Data Integration – Part One, Overview

Tue, 20 Mar 2012 19:17:00 +0000

In some cases, if not all too some extent, integration between Dynamics™ CRM, Salesforce® or/and SharePoint® with your back-office system is the key to user adoption. Real-time, two-way data integration allows all segments of the business to access the very latest transactional data, and the information that the data contains. One example might be the keying of a ‘large’ order by a sales representative into CRM or Salesforce. Having real-time, two-way data integration in place, that order would go directly from the crm system to your ERP/MRP system for processing. That in turn will reduce inventory and alert the operations team, signaling the purchasing department that orders need to be placed to backfill inventory and, signaling the operation manager that they will need to increase production to fulfill the ‘large’ order. In some cases the integration of data can trigger an alert that will notify outside vendors directly that inventory needs to be replenished.

With access to current inventory levels within a sales rep’s CRM or Salesforce system, sales reps can make better informed customer promises with regard to when items will ship and/or if ordered items will be backordered. This greatly improves customer satisfaction and adoption of the new CRM or Salesforce system. Other advantages (among a plethora) is integration into SharePoint as well, where lists can be compiled to help make better business decision as well as having vital documents at your fingertips, which ever application you are currently using.

This is just one small example of how application data integration can improve adoption, and also improve the client’s business prospects. My purpose in this blog is not to discuss the business benefits of data integration, but explore some of the architectural hurdles in designing the real-time, two-way data integration processes. In a short series of blog entries, we’ll examine:

How data is discovered for translation

When to discover data for translation

What data to discover for translation

How to handle concurrent data modification

How to incorporate the client’s and the application’s
business rules into the integration processes

We will, by no means, cover all the detail that goes into data integration, but will cover, at a high level, some of the hurdles and how to overcome them. In some cases, there will be a choice of methods to accomplish a task, so, we’ll also talk about the best method to use in particular situations. Some methods are tool agnostic, some will highlight how a tool like Scribe Insight provides easy access to data and the business rules around the data. We’ll also see that many of the methods are application agnostic, meaning they can be applied to any system to system integration.

Data integration can be tricky stuff if it’s your first time tackling the subject. Whether you are implementing a solution, or just need to talk comfortably about integration, there are several things to be careful of, but having said that, like anything else, it’s just a matter of experience before your comfort level is one that keeps your knees from shaking and your palms from sweating.

Salesforce Tip: Map a Lead Field to Two Places

Fri, 13 May 2011 18:30:00 +0000

On a recent Salesforce implementation, we identified a need to map a single lead field to two different fields - one on the contact and one on the opportunity.

My initial thought was to create a trigger to fire on lead conversion that would populate the second field. However, I always try to look first for a non-coding solution. Which brought me to the fairly simple idea of creating a second field that would use a workflow field update to copy the value of the original field. The new field would be hidden from the users, but would be used for the sole purpose of mapping to the second destination field. I thought I'd found the perfect "clicks not code" solution ...

until I realized my field was a lookup field, a field type that can't be updated by workflow. Drat.

So, I did need a bit of coding in order to update the second, hidden field with the value of the original field. I created a very simple trigger to set the value of the second lookup field to match the first.

trigger CopyCampaignSource on Lead (before insert, before update) {

for (Lead l : Trigger.new) { l.c5_Campaign_Source_Opp__c = l.c5_Campaign_Source__c; } }

Would I have been better off going with my first instinct, which was to create a trigger to fire on lead conversion?

In hindsight, maybe. But, this method was still simple and effective, and I think it's always worth it to explore non-coding solutions first - especially knowing that most implementations will ultimately be maintained by non-developers and, therefore, should be as admin-friendly as possible.

CRM Overview - Salesforce.com

SuperUser Account — Tue, 15 Feb 2011 19:35:30 +0000

A quick overview of Salesforce.com - all of the basics in less than 4 minutes!

Get Social: More Options for Following Us

Fri, 11 Feb 2011 08:40:00 +0000

Some Background

At the beginning of 2010, our two companies (StreamLogic and Customer Connect) merged to become C5 Insight. One company focused on Microsoft SharePoint and cloud application development. The other company focused on CRM (Dynamics CRM and Salesforce.com) and sales and marketing strategy.

When we merged our blogs, we started to receive feedback that we were providing an overwhelming amount of information. Our blogs included high level strategic and best practice information, as well as detailed technical tips for developers and administrators. They also included information on all of the different solutions that we support. So most of those who were following us found that they were getting some information that wasn’t useful for them. In addition, options for following us were limited to email or RSS feeds.

Something had to change!

The Social Channels

So we decided to take a page out of our own Social CRM playbook (it was a typical case of, “the cobbler’s children are the ones with no shoes.”) At a later date, we’ll share details about Social CRM and our specific strategy as a separate blog. For now, suffice it to say that:

We took feeds from our: Blog Site, On Demand Video Site and Live Event Site.
We then parsed them out by role and solution type.
And we made them available across the most popular social channels.

Voila – a lot of blood, sweat and tears for us delivered a much more relevant way to consume the information that you want. And it’s all free to you (we guarantee that you’ll get your money’s worth).

If you want to learn a bit more about Social CRM, check out this video.

Current C5 Followers

If you’re currently following one of the older C5 Insight feeds, we encourage you to look at the new options. You will find that you can filter what you’re receiving to just the information that is most relevant to you. Plus, some of our old channels will soon be discontinued – so take the time to sign up for one of the new ones.

www.c5insight.com/follow

The Free Giveaway

Another exciting bit of news at C5 Insight – we have just completed authoring a book, “Microsoft Dynamics CRM 2011 Administration Bible.” There’s even a special appendix on advanced SharePoint integration. To celebrate the book and our new social channels, we’re giving away 5 free copies of the book.

Where do you sign up? I’m glad you asked. We’re going to give away the 5 free copies by randomly drawing from a list of all of our followers once we reach 200 new followers across all of our social channels (or on March 21, 2011 – whichever comes first). So be sure to sign up to follow us by March 21!

Or, if you’re in a hurry to get the book, go ahead and click the image to order it from Amazon.com. If we draw your name as a winner, you can get a signed copy to treasure for generations to come!

So, be sure to sign up for the social channel of your choice today!

www.c5insight.com/follow

A few pointers about Salesforce for Outlook

Thu, 10 Feb 2011 21:36:00 +0000

We've recently had a few questions from power administrators about how to enable Salesforce for Outlook for their organizations. There are two basic steps: - First, the administrator needs to create at least one Outlook Configuration by going to Setup > Administration Setup > Desktop Administration > Outlook Configurations. Additional configurations can also be setup, if groups of users within the organization should have different settings. - Users can then download Salesforce for Outlook by going to Setup > Personal Setup > Desktop Integration > Salesforce for Outlook. Salesforce for Outlook is significantly different than the previous product (Connect for Outlook), so there are a few important things to keep in mind: For full instructions on using Salesforce for Outlook, go to the Help & Training section in Salesforce. HOWEVER: if you simply enter Salesforce for Outlook as your search terms, you'll get a confusing ...

An Overview of Salesforce.com Chatter

SuperUser Account — Thu, 03 Jun 2010 00:00:00 +0000

Social media tools such as facebook have made an impact on the business world. Those same concepts, applied to businesses internally, are about to cause a revolution in business collaboration. This video is an overview of how Salesforce.com's Chatter works.

May 2010 - Side-by-Side: What Makes Microsoft CRM and Salesforce.com Different?

SuperUser Account — Sun, 23 May 2010 23:16:36 +0000

A unique opportunity to see an objective comparison of the two most popular and most powerful CRM applications on the market today.

Upcoming Cloud Computing Event

Thu, 25 Mar 2010 00:30:00 +0000

I wanted to let all of our readers know about a cloud computing event that will be held in 4 cities along the East coast. I admit, it is my company that is hosting the “4-City Tour” but this really is a going to be a good way to see many cloud platforms at work.

Highlights:

    Parallel sessions on Microsoft CRM, Salesforce.com, SharePoint, and Unified Communications
    Integration luncheon showing a live demo of integration between CRM, SharePoint, and UC
    Exclusive research on the top cloud challenges from CFOs and CIOs
    Exclusive demos of SharePoint 2010
    Exclusive session showing Microsoft CRM and Salesforce.com in a live side-by-side comparison

Cities:

    May 4 – Charlotte, NC
    May 6 – Washington, DC
    May 11 – Raleigh, NC
    May 13 – Atlanta, GA

Demo Dynamics CRM, SharePoint and Salesforce.com

Sat, 30 Jan 2010 09:07:00 +0000

Looking for a fast way to get a demonstration of Dynamics CRM, Microsoft SharePoint or Salesforce.com? A new site: demos.c5insight.com has been setup for just this purpose. You'll find a variety of demos on the site for different types of users including:

* Fundamentals of CRM, Document Management and Business Process Automation

* Integrating SharePoint and Dynamics CRM

* Comparing Microsoft CRM and Salesforce.com

Looking for a demo that's not available? Post a comment in response to this blog and we'll try to follow-up on requests that we're seeing most frequently.

Salesforce.com Chatter API

Sat, 21 Nov 2009 01:20:00 +0000

Announced only a couple days ago, Salesforce.com has plans to release Chatter. Chatter is a new enterprise social engine. I like to think of it as a combination of IM and RSS feeds into a single platform that's security controlled and handled inside the Salesforce.com Cloud. So, it's more secure and allows the organization to communicate freely internally without risking exposure of confidential information. Developers are going to like the new Chatter API. On the surface it seems to be fairly straightforward with only 5 different objects in the data model (User, FeedPost, NewsFeed/Object, FeedTrackedChanges, & FeedComments). Chatter will support adding content to the messages sent as well as sending messages from Profile/User, objects and feeds. The next release Spring '10 is slated to include User Profiles, Post, Comments, & Feeds, Subscriptions, and Chatter only licenses ($50/month/user). Future releases should include Questions & Answers and ...

Batch APEX

Sat, 21 Nov 2009 01:19:00 +0000

What is Batch APEX?

Batch APEX is a way to run code in a batch in Salesforce.com. It can be scheduled or called to run asynchronously. Batch APEX has three primary asynchronous methods: Start(), Execute(), and Finish() that handle all of the processing in the batch.

Batch APEX also provides a way to query the status of a Batch using both Visual Force an in the UI in Setup. It's a great way to handle mass data updates of up to 50 million records at a time.

Updates from DreamForce 2009 - The Bulk API

Sat, 21 Nov 2009 01:18:00 +0000

Have you ever had to move a lot data into Salesforce really fast? Well, unfortunately, I think a lot of us have been in that situation and the store in the past wasn't all that great. When I first started working with Salesforce, I wrote an API tool that would replicate the entire Salesforce object structure on SQL Server with picklists. It was a pretty cool application. I later extended it to bring down all the data as well, but was really disappointed when I realized how long it takes to pull down several hundred thousand records. So, I ended up leveraging Cast Iron and the Data Loader to solve some of my integration problems. The Data Loader was a real life saver, but it had some severe limitations. First, it was slow. One thing I used to do was split my loads into 3 to 5 batches and run each batch in a seperate Data Loader instance at the same time. While this works, it can get kind of crazy when there are a lot of files to load and spl ...

Salesforce.com - a new UI????

Sat, 21 Nov 2009 01:17:00 +0000

Announced at Dreamforce is a new UI for Salesforce! This new UI will of course be optional, but addresses a number of issues with the current UI. What I've seen so far is impressive. It definately looks cleaner and does a better job of presenting data to the user. One of my favorite features was an enhancement to add a few indicators at the top of the opportunity (I'm hoping it will be available for all objects) to show the most important data about that record. In just a few seconds, you can easily see what's going on with the record. They call this new feature the "Deal View" and it will be customizable. The Related Lists have also been moved over to one side and make for a much cleaner interface and usability. For developers who've built custom UI to look and feel like Salesforce outside of the standard Visual Force pages are going to have some issues as well as those who've built Flex UI to match. However, standard Visual Force pages will easily adopt ...

Dream Force - Sales Cloud 2

Sat, 21 Nov 2009 01:16:00 +0000

So, what's new in the Service Cloud 2? Well, a lot of things are new, but I thought the big ones are the Real Time Quoting, Salesforce for Outlook, and especially the new Report Builder. Let's not forget Chatter which I'll touch on later. Salesforce released in Winter '09 the Real Time Quoting functionality that allows organizations to build a quote from an opportunity, print as a PDF and send along with other packaged content to the customer via email. Very nice feature and will definately have a net positive impact with many customers out there! This was a significant step forward for sure. The new Salesforce for Outlook is going to make a lot of folks real happy as it solves some of the old problems with the Outlook client integration. My favorite new features (beside's Chatter) has to be the Report Builder enhancements. Coming in one of the next releases is a new capability to design reports using real data pulled directly from the objects so you see in real time as ...

Dream Force 2009 - The Service Cloud 2

Sat, 21 Nov 2009 01:15:00 +0000

So what's new in the Salesforce Service Cloud 2? Well, for starters I was really surprised by the statistic quoted by Salesforce that 55% of the market is held by thier very own Service Cloud! That's huge, but then who would doubt that was the case with a solid platform such as Salesforce? There are a number of great features that have been in the Service Cloud for some time such as the CTI screen pops, integrations with Google Maps, etc., but this year, they really blew the wheels off this jet with the introduction of the new KB engine. For instance, the new KB's support rich media. What's more cases can be initiated in many different ways including a customer posting a question right over Twitter or Facebook. Salesforce has opened up a whole new set of channels for handling and managing cases directly over the internet that leverage the application platforms their customers are already familiar with and trust. There's a whole new functionality that is in the works that'll sup ...

DreamForce 2009

Sat, 21 Nov 2009 00:54:00 +0000

Wow! That word hardly describes the DreamForce event this year. SalesForce really did it up nice, although the food could have had a few more selections. SalesForce has finally passed the $1B mark in sales and it was clear by the attendance (19,000!!!!) that they've garnered a lot of support by businesses both large and small. I thought for sure the economy would have had a bigger impact on the event, and maybe it did, but attendance was exceptional regardless. One of the best signs I saw this year is that the Force.com and Sites message is really hitting home. What's more CIOs and CTOs are embrasing the technology and saving money. Marc Benioff touted the following from an IDC report - 54% savings ($), 5 times faster (time to implementation). Having worked with the platform and delivered in excess of 40 full lifecycle projects myself, I have seen similar results. What's more, a lot of companies are realizing how much more quickly changes can ...

What is all the Chatter about?

Fri, 20 Nov 2009 01:05:00 +0000

In short, Chatter is a social networking application that is built into Salesforce.com. It is structured to be an "internal social networking" application but can also be easily linked to public facing social networking sites. Some of the highlights: It can work very similarly to Facebook.com - you can post comments to the site and others in the organization can view the comments that their friends post. Visually, it looks similar to a Facebook page. Individuals can add comments to posts that they see on Chatter. But the real strength is that any record on any object in Salesforce.com can be Chatter enabled. What's more, it includes fairly sophisticated filtering functions. So (note: some of this is guesswork as I don't have a working copy of Chatter yet): A manager can get Chatter notices whenever one of their reps opens a new opportunity. An executive can get a notification whenever a case to a top 10 client is ope ...

Debugging APEX

Sat, 17 Oct 2009 23:54:00 +0000

Let's face it. Salesforce.com and Force.com are new kids on the block. They're growing up fast, and establishing their territory, but they've still got some maturing. Most languages these days have an interactive debugger. However, APEX is the exception. If you're new to APEX coding, I recommend you take a look at three things to help you overcome this hurdle: 1) Debug Logs, 2) Running tests in Eclipse, 3) Running tests in Salesforce.com. Since there is no interactive debugging with APEX, you've got to find ways to identify how far your code ran and what it did when it got there. One thing I do while writing code is to add debug logs to indicate the values I'm testing and to tell me that things ran up to that point. If you write good test methods, you should know what to expect at each point in your code. system.debug("checking value: " + myvar); When the debugger passes this point, a statement is logged with the value and if ...

Locking records down to editing in Salesforce

Sat, 17 Oct 2009 23:53:00 +0000

One common thing we run into in Salesforce.com is having to lock a record down to editing to certain groups once a certain stage or status is reached. There are two different schools of thought on the best approach to doing this. The first is to use record typing. For instance, let's say you're working on an opportunity and want to lock down the record so that changes can't happen after it reaches a Closed Won stage. The easy way to do this is to create a new record type "Read Only", create a new layout for that record type and then set all of the fields to Read Only that shouldn't be edited. Then you'd want to create a workflow that sets the record type based on the stage of the opportunity. It's all pretty easy, but you'll still need to address training issues at the start with users to be sure they don't create records with a "Read Only" record type. One other nice thing about this approach is that you can assign the noral record type that's Read/Write based o ...

Amazon S3 Integration with Salesforce.com

Thu, 15 Oct 2009 23:52:00 +0000

We recently had an opportunity to do some work to integrate S3 Amazon Web Services into Salesforce.com. Salesforce.com provides some sample code that was very useful in getting the S3 services to work. However, along the way I ran into a number of challenging issues that I'm sure many other developers have tackled. The first big issue was that we would be dealing with very large files, greater than 2GB in some cases. Unfortunately, the Salesforce.com web services can't handle large files (>100k) via their web services, but the S3 services can handle up to 5GB. Salesforce.com had some sample code that leveraged POST directly to the S3 service via a Visual Force page. This was all good, but it took a bit of work getting everything customized and working correctly. One of the most challenging parts was figuring out how S3 handles access because we didn't want our customer's files being shared with the rest of the world. There is a mechanism for controlling access, but if ...

Customer Portal Access

Thu, 15 Oct 2009 23:51:00 +0000

Every day I'm amazed by the new features in Salesforce.com. Over the past week, I've been working with a customer to get their Customer Portal setup and functioning. We're building some very cool functionality using the Force.com platform to expose some custom objects to their customers. However, we ran into a situation where sharing rules needed to be setup and the UI is just a bit more than we really like our users to have to take in. Sharing is a great feature, but the last thing anyone wants is to have a customer looking at someone elses data because a user didn't really understand what they were doing or was simply confused when they setup sharing. This is where APEX sharing comes in. The Force.com platform has a very cool feature where an APEX developer can write a class to handle complex sharing rules. When I read the documentation it's relatively easy to setup, but of course like a lot of Salesforce APEX trigger code, it's imperative that it's designed to work ...

Connecting Microsoft Outlook to your Salesforce.Com Test or Sandbox Instance

Fri, 09 Oct 2009 23:48:00 +0000

After downloading the Salesforce.Com Connector for Outlook I noticed that it was hardcoded to what SFDC server I could connect to. I needed to do some testing and struggled to find where I could change the URL. My end goal was to change the Server URL to point to https://test.salesforce.com/services/soap/c/10.0 After poking digging around in the registry I found a place that this could be changed. If you open your registry and go to “HKEY_CURRENT_USER/Software/Salesforce.Com/SM” you will see an entry called “Server URL.” There you can change that link to point to your sandbox instance. Once you have done that you can re-open Outlook and type in your login credentials. Make sure that when you login you also add your Salesforce.Com token to your password. Hope this helps you save some time!

Salesforce.com and Microsoft CRM: Side-by-Side Demo

SuperUser Account — Sun, 24 May 2009 00:00:00 +0000

An exclusive side-by-side demo of Microsoft Dynamics CRM and Salesforce.com! If you're considering a CRM solution, this is a can't miss session. Be sure to the second version of this unique webinar - delivered in May of 2010!

Users can't access Visualforce pages?

Fri, 17 Apr 2009 23:47:00 +0000

A coworker came to me yesterday with a frustrating question - why can't non-system adminstrator users see a new Visualforce page that had just been created? Instead they see the "Insufficient Privileges" error. I remembered struggling with the exact same problem when I first started working with Visualforce. The answer is available in the Visualforce discussion boards, but is difficult to find. So, here is a quick summary: Access to Visualforce pages and Apex classes is determined by user profile. There are two ways to change the access levels. 1 - To view or change the access levels for a single profile, go to the view screen of the profile and scroll down to find the following two related lists: Enable Apex Class Access and Enable Visualforce Page Access. 2 - Or, set the access level for multiple profiles by going to the Apex class and Visualforce page lists in Setup. Click the Security link beside each class or page name and select the profiles that need ...

Integration and Outbound Messaging

Wed, 04 Feb 2009 00:23:00 +0000

Outbound Messaging in Salesforce.com is an incredibly powerful feature for doing integration, but it does have a few drawbacks. Before I get into the negative points, I want to point out some of the good. The outbout messaging feature has two capabilities which are extremely important for integrating Salesforce.com with other systems. First, it insure messages get sent immediately after the workflow fires, and second, it insures delivery of your message. However, during a recent integration I quickly realized that insuring delivery of messages meant that my receiving system HAD to consume them and return a response message confirming that the data was consumed. At one point during my integration development a large number of new records were added to the system for migration testing and all of these records fired outbound messages. (Think 1M records added or updated each taking about 1s to process.) Another issue I quickly ran into after we went live is that my integr ...

Are you using Email to Salesforce?

Mon, 20 Oct 2008 23:20:00 +0000

I recently did an informal poll of a handful of Salesforce.com users and realized that NONE of them were even aware of Email to Salesforce. Trust me ... it's something worth knowing about and, most likely, something you'll want to think about implementing in your organization. After enabling Email to Salesforce, you can add a Salesforce-provided email address to the bcc line of any email you send and the email will appear in the activity history related list of the correct lead or contact in Salesforce. What if there isn't a match? No problem - a task will be created instead, which you can then handle in Salesforce. To learn how to easily setup this functionality, just search for "email to salesforce" in the Help and Training section of Salesforce. And Outlook users can even take it one step further ... some simple code can added that will eliminate the need to add the address to the bcc line - instead, each time you send an email, you'll receive a message asking "Add to Salesforce?". C ...

Getting Started with Summer '08 ... Cross-Object Formulas

Mon, 16 Jun 2008 23:19:00 +0000

Check out your new orange creamsicle logo in Salesforce! I'll highlight some of the updates in the Summer '08 release in the next few blog entries. One of the highest impact features is the ability to create Cross-Object Formulas - meaning you can use parent record fields on a child record. FINALLY! Prior to this release, various workarounds had to be used ... such as creating workflow to copy a value over, embedding an s-control, etc. Now cross-object formulas will solve the problem. Some standard real-world examples of this functionality are placing the Account Number on the Opportunity, or creating a Discounted Amount formula on the Opportunity referencing a Discount Percentage on the Account. Here's a cross-object formula I just created for a client. They used a different commission percentage based on whether the account was a new or repeat buyer. So, on the commission custom object, I referenced the "# of Opportunities" roll-up summary field on the Account to determine whether or not t ...