New Sales Cloud Features for Salesforce Spring 14

As a continuation in the previous post about Salesforce Spring 14, we will highlight the new sales cloud features that will surely help in improving the profit of the company. Spring 14 offers new and exciting Sales cloud features that will help you easily manage your users and leads. 1. With Salesforce Spring 14, you can now link your Leads, Accounts, and Contacts to their Twitter profiles using Salesforce1. This will give you the ability to have more information about your customers and prospects, and will enable you to easily contact them. Moreover, Spring 14 can now give you the ability to call, log calls, and send emails to your Leads.

2. Multi-monitor components allow you to drag any portion of a console, and move it to any location. This allows multi-view of a user's interface, which allows you to easily edit a user's information.

3. Salesforce Spring 14 also gives you task flexibility as it offers repeating tasks feature. Once a task is completed or marked, it will recur depending on the number of days specified.

4. Salesforce for Outlook side panel can now give you the ability to create cases.

5. New custom object has been introduced, which is Orders. The object can be either added to a Contract or an Account. With this custom object, you can now process order management in Salesforce.

6. The forecasting feature has also been improved as it enables you to view up to four types of forecasts; namely, Opportunity splits based on revenue, Opportunities based on revenue, quantity, or both, and Product families based on revenue, quantity, or both.



Common Data Loader Errors


Data Loader helps in mass updating, inserting, upserting, deleting, and exporting your data. It is ideal for any organization that manages more than 50,000 records. As compared to Import Wizard, Data Loader supports more objects and can process more records. However, Data Loader is only available for Enterprise editions and above.

One of the most common cases being submitted to support pertains to common data loader errors. It is important to be familiarized with these common data loader errors in order to prevent it from impacting your business. For data that require immediate processing, it is pertinent to know the initial steps needed to be done.

Here are some of the common data loader errors:

1. Error: Row is larger than header - this means that there is a data in a field that has no header to be mapped. To resolve the issue, please make sure that your import file has a header, and map it to appropriate field upon doing the import.

2. Error: System.Exception: Too many SOQL queries - the error means that there is a trigger on the object and it is currently exceeding the governor limits. To resolve the issue, you can either modify the trigger or have support increase your API calls.

3. Error: Duplicate value found - this means that you are attempting to update a unique field. To resolve the issue, please ensure that the field/s you're attempting to update is/are not unique field/s. If they are unique fields, then you must enter a unique or different value. You can also consider temporary removal of a field's uniqueness while doing the update by clicking: Name | Setup | Customize | Object | Field | Click Edit on the field | Un-check "Do not allow duplicate values" | Save

4. Error: Owner ID: ID value of incorrect type - unlike Import Wizard, Data Loader requires Owner ID and not the record name to map the record owner.

5. Error: [INVALID_CROSS_REFERENCE_KEY].Messae [Customer Record Type: id value not valid for the users profile: xxxxxxxxxxxxx] - this error message usually appears when you are the record type being assigned to a user is not yet active on his profile. To resolve the issue, the following steps should be done: Click on Setup | Manage Users | Click on the profile that the record type needs to be added to | Scroll down to the Record Type Settings section | Click Edit on the Object | Select the specific record type in the list "Available Record Types" and add it to "Selected Record Types | Save

These are just one of the most common data loader errors. If you have other error messages to report, please feel free to comment on this website or contact us at


Although the standard Salesforce features are helpful and efficient, it is sometimes required for you to create custom Apex codes in order to improve system performance and triggers that are currently not possible with your standard Salesforce functionality. In order to avoid  apex code error messages that could potentially impact your business, it is pertinent for you to be familiarized with these common errors and get to know how to resolve them. REQUEST_LIMIT_EXCEEDED

This is one of the most common Apex code error messages, and it often appears when your API call limit for your organization has been already exceeded due to huge number of integration with third party applications.

When integrating with third party applications, it is important to consider how would these applications affect your API call limit. It is important to plan and evaluate how these applications would be used in order to prevent the limit from being exceeded.

The best way to monitor API usage is either to run an API usage report or monitor your limit under Setup | Administration Setup | Company Profile | Company Information.


Validation Rules are helpful, but could also be painful, if not correctly used or deployed. In order to avoid this error, Validation Rule should be created based on your business needs, and make sure that it would not conflict with other triggers or rules. Rules should also be assessed periodically to make sure that they are still needed in the organization, if these rules are deemed unnecessary for the org, then the rules could be modified or deleted already.

One of the best ways to deal with this error is to make the class calls a DML operation, specially when deploying a batch class. The opt_allOrNone shouls also be set to False. This workaround would allow saving of the record even though it fails to meet the Validation Rule/s.


This error usually occurs when the length of the entered text is longer than the field length limit. The field length can be modified by going to Name | Setup | Customize | Object Name | Field | Click Edit on the field being modified | Change the length | Save.


Improving your Apex codes and modifying your current customization are necessary to properly deploy Apex codes and avoid encountering errors. If you would like to know more about custom Apex code creation and integration, you may contact us for assistance at

Local Name Fields - What Are They?

“Local Name field” is one of the least commonly used functionality in Salesforce. Some of the users might not be aware of it and its functionality. Although it is not commonly used, it could be considered in your organization for efficiency purposes. Here are some of the advantages of the feature:

  1. Local Name fields are additional standard fields that allow a translated version of text fields to be manually defined. These fields will remain unchanged even after changing your language. For example, when you changed your organization’s language from English to Spanish, these fields will remain in English.
  2. It helps in categorizing records in order to properly pull them up either via Search or Report. These fields could be used to filter the records for reporting purposes.
  3. It allows records to have two names. For example: Record A has local name field value of Record B. Whether you search for Record A or Record B, it will still pull up the same record.

Local Name fields are only available under Accounts, Contacts, and Leads; specifically, Account Name, Contact First Name, Contact Last Name, Lead Company Name, Lead First Name, and Lead Last Name.

These fields need to be enabled by Support. If you’re interested in maximizing the feature, then feel free to get in touch with Support. Once the feature is enabled, these fields are not visible by default, and needs to be manually added to the Page Layout and be visible by Field Level Security.

If you have further questions on how to maximize Local Name fields for your organization, feel free to contact us at

Salesforce Spring 14 is Coming!


In order to provide customer satisfaction, Salesforce continuously provide quarterly releases in order to introduce new features and functionality depending on the needs and demands of their customers. Spring 14 release is scheduled to start on February 7, 2014. In order to maximize the new features and to prevent potential data issues, it is important to be prepared and familiarized with the latest Salesforce release.

Sandbox Preview

If you have refreshed your Sandbox before January 3, 2014, then you would have the chance to maximize the Sandbox Preview instance in order for you to test new Salesforce features. It would also prevent your organization from potential data loss. Moreover, this will aid in familiarizing yourself with the latest features without the worry of having your records and customization affected.

To know more about the Sandbox Preview instruction, please refer to this link:

Plan Accordingly

It is the time to determine how the end users would be trained regarding the newest features. You may also need to figure out which of the new features would give more benefits to your organization. You may also need to export your records in order to prevent potential record deletion upon rolling out the latest release. You could also consider reading the release notes at in order to prevent worries if ever you would see some changes on your Salesforce account.

Highlights of the Release

Here are some of the features that would be introduced on Salesforce's Spring 14 release:

1. Skills and Endorsements (Pilot) – Skills reference data (ProfileSkill) can now be added and associated with People (ProfileSkillUser). Chatter profile will display the skills profile of the user. These skills can also be "endorsed" by other users. Chatter and Setup Pages are the places where the skills can be managed.

2. Feed-Based Page Layouts – This feature would provide convenience and efficiency as it makes Case Feed available also for Account, Contact, Opportunity, Lead, and Custom Objects.

3. API Limit App Quotas (Pilot) - Standard, bulk, and streaming API consumption now have 24 hour API quotas for Connected Apps.

4. Canvas apps can now be placed into the Salesforce1 navigation menu.

5. Spring 14 also introduces a useful administrator feature that would let you view and manage user sessions.

6. Permission Sets can now be massively assigned.

7. Sharing Sets Enhancements (Pilots) - this would allow indirect lookups from one object to another. This would allow you to access second level of related records.

8. A New User Interface is also introduced to allow you to view and cancel running deployments.

The Future of Salesforce

As Salesforce continuously improve their features, it is no doubt that it would be the next leading CRM tool in the future. Managing your database would be easier as it adapts to the changes and releases. It is always best to be updated with the current trends in order for you to maximize your business and to closely interact with your employees, clients, and customers.

To know more about Spring 14 release, you may check these links:

Spring 14 release video -

Spring 14 release notes -

Major Release Schedule -

If you need assistance with preparing your organization for the Spring 14 release, please feel free to contact us at

Tips and Tricks: Unable to Process Request Error When Editing a User


You might receive this “Unable to Process Request” error message whenever you attempt to edit a user’s information under Name | Setup | Manage Users | Users. The error may appear regardless of the information you’re trying to edit, and this could potentially impact your business.

The truth is, this “Unable to Process Request” issue has already been listed as a Bug, and Salesforce’s R&D Team are already working on it in order to provide a permanent fix to the issue.

While they can’t provide a permanent fix yet to the issue, there is a workaround available in order enable you to edit and save your user’s updated information. The workaround is to disable the Feed Tracking of Address Field on User Object.

Here are the needed steps:

  1. Click Setup | Customize | Chatter | Feed Tracking
  2. Click User
  3. Uncheck Address
  4. Click Save

This workaround can temporarily be considered while there is no permanent fix yet.

Keep yourself updated with the latest Known Issues with suggested workarounds at or get in touch with this website’s administrator at to seek help and assistance.

Tips and Tricks: Resolving Common Salesforce Problems


Salesforce Support has always been helpful in dealing with their customers' concern. However, there are issues that could easily be dealt without waiting for 24-48 hours for a Salesforce Support to respond. It is also important to be familiar on the initial steps that should be taken into consideration for common Salesforce problems, especially for business impacting features. Here are some of the common Salesforce problems that should be considered before logging a support case:

1. Cache and Cookies

Cache and Cookies store some information from the internet; however, these information could also affect system performance. It is important to make sure first that your issue is not something related to cache and cookies.

You might experience log in issues; your interface might not display correctly; or some features might not properly work. These issues are not necessarily Salesforce-related .

The steps on how Cache and Cookies can be deleted can be found here:

2. Supported Browsers


You should also consider the compatibility of your browser's version with Salesforce. When browsers do an update to their version, some Salesforce features may not be compatible to the version yet. It usually takes few weeks or months before the compatibility is fixed.

As of today, here are the supported browsers:

a. Internet Explorer - versions 7,8,9, and 10.

b. Mozilla Firefox - most recent stable version.

c. Google Chrome - most recent stable version

d. Apple Safari - versions 5.x and 6.x on Mac OS X

3. Salesforce Edition

60-80% of the issues being received by Salesforce Support are Edition-related limitations. If it seems that you're missing some features and functionality, or if your 3rd party applications from the Appexchange fail to install, then you might want to check first if they are supported with your edition.

Here are the common issues that are reported and found to be Edition-related:

a. Custom Profile - Cloning or Customizing Profiles are not available for Professional Editions and below.

b. Mass Email - This feature is only available for Professional Editions and above.

c. Permission Sets/ Sharing Rule - Although Account and Contact Sharing Rules are available in Professional editions, sharing rule to other objects are only available for Enterprise Editions and above. Consequently, Permission Sets are only available for Enterprise editions and above.

d. Workflow and Approvals - Although this feature may also be available for Professional Editions with additional cost, it is only available by default for Enterprise editions and above.

e. API - Some applications might require you to have an API enabled. API is only enabled by default for Enterprise editions and above.

To get the complete list of features and limitations, please check this documentation:

4. Unable to Receive Emails from Salesforce

If you aren't receiving important emails from Salesforce, like Password Rest emails, you should initially check if your network setting is blocking any IP addresses coming from Salesforce. To determine: Name | Setup | Email Administration | Test Deliverability | Enter your Email Address | Click Send. You should receive a total of 52 emails. If you receive less than that, then you confirm that you are blocking IPs from Salesforce.

To check the IP addresses that need to be whitelisted, please refer to this site:

5. Setup Audit Trail

Salesforce Support is also receiving lots of cases regarding the questionable changes in the customization of their organization. These changes are not always Salesforce-related, most of the time Support would just figure out that one of the company's System Administrators were the one who did the change. Setup Audit Trail could help you in determining the configuration changes that had happened in the past 180 days. To run an audit: Name | Setup | Security Controls | View Setup Audit Trail.

6. Recycle Bin

For missing records, you may want to check if they were just accidentally deleted by one of your users. Your recycle bin stores deleted records for 15 days.

7. Blogs, Community Pages, and Help and Training Portal

You could also consider finding your answers first from one of Salesforce experts in different blogs in the internet. Most of your answers could also be found on the Help and Training portal. These resources are readily available and should be maximized to find answers to your questions.

If all of these recommendations fail, then you might want to consider logging a Support Case. In order to resolve issues that could potentially impact your business, you should be familiarized on the first steps that should be taken into consideration. As you become expert in handling these common issues, soon you will turn into a walking Salesforce encyclopedia!

Minimize Clicks with Publisher Actions in Salesforce1

Publisher Actions - OverviewSalesforce1 is the new feature introduced by Salesforce during the last DreamForce. It is an advanced mobile application that will particularly benefit developers who would like to integrate Visualforce onto their end-users' mobile dashboard.

It comes with enticing new features; improved interface, layout, and graphics. One of the highlights of Salesforce1 application is the Publisher Action, which is designed to have a one-click interface that easily allows users to create and update records.

Using the Feature

Publisher Actions
Publisher Actions

By just clicking on the  icon on the lower right side of the screen, the Publisher Action interface will be shown to let you update your Chatter posts, create new records, new tasks, share a link, or even create a poll in just one interface; thus, minimizing clicks.

publisher interface
publisher interface

Publisher Action is available on both Standard and Custom Objects where the Chatter feed is enabled. To verify if Chatter feed is enabled on your objects: Name | Setup | Customize | Chatter | Feed Tracking | Navigate on Each Object to ensure that "Enable Feed Tracking" is checked | Save.

Enabling Publisher Action

The feature is enabled by default in Salesforce1. However, the feature will not work if Chatter feature is disabled under Name | Setup | Customize | Chatter | Settings.


As Salesforce continues to improve Salesforce1 features, the integration of Publisher Action is a huge milestone in maximizing the use of mobile and smart phones for your business.  The feature is ideal to every organization as it will increase productivity by minimizing clicks and navigation.

Visualforce page could also be integrated in order to customize how you want your Publisher Action to work.

To know more about Salesforce1's features, you may watch the Salesforce1 demo on

Scheduled Report - Missing Users

No Report Recipients
No Report Recipients

Have you ever encountered a scenario where you would like to send a scheduled report to a specific user but they are not in the list of options? This is  mainly because the user doesn't have access to the report because of the report folder settings.

In order to solve this issue, we just need to do the following steps:

  1. Pick a time when there are lease number of people using the system since we will
  2. Go to the report folder where the report to be sent is stored and then change the setting to "This folder is accessible by all users, except for portal users"
  3. Go back to the scheduler page of the report and you should be able to see all the users in the system
  4. As soon as the report is scheduled, go back to the report folder settings and then put back the old security settings

The process is a bit kludgy but its the only way to do it at this time until Salesforce fixes the issue.

Formula: Business Days between dates

Have you ever needed to get the number of business days between two dates? Here is a quick formula for you to do this.

Weekday Count Formula:

  CASE(MOD( StartDate__c - DATE(1985,6,24),7), 

  0 , CASE( MOD( EndDate__c - StartDate__c ,7),1,2,2,3,3,4,4,5,5,5,6,5,1), 
  1 , CASE( MOD( EndDate__c - StartDate__c ,7),1,2,2,3,3,4,4,4,5,4,6,5,1), 
  2 , CASE( MOD( EndDate__c - StartDate__c ,7),1,2,2,3,3,3,4,3,5,4,6,5,1), 
  3 , CASE( MOD( EndDate__c - StartDate__c ,7),1,2,2,2,3,2,4,3,5,4,6,5,1), 
  4 , CASE( MOD( EndDate__c - StartDate__c ,7),1,1,2,1,3,2,4,3,5,4,6,5,1), 
  5 , CASE( MOD( EndDate__c - StartDate__c ,7),1,0,2,1,3,2,4,3,5,4,6,5,0), 
  6 , CASE( MOD( EndDate__c - StartDate__c ,7),1,1,2,2,3,3,4,4,5,5,6,5,0), 
  (FLOOR(( EndDate__c - StartDate__c )/7)*5) 

Weekend Days Count Formula:

  CASE(MOD( StartDate__c - DATE(1985,6,24),7), 
  0 , CASE( MOD( EndDate__c - StartDate__c, 7),1,0,2,0,3,0,4,0,5,1,6,2,0), 
  1 , CASE( MOD( EndDate__c - StartDate__c, 7),0,0,1,0,2,0,3,0,4,0,5,2,2), 
  2 , CASE( MOD( EndDate__c - StartDate__c, 7),0,0,1,0,2,0,3,1,2), 
  3 , CASE( MOD( EndDate__c - StartDate__c, 7),0,0,1,0,2,1,2), 
  4 , CASE( MOD( EndDate__c - StartDate__c, 7),0,0,1,1,2), 
  5 , CASE( MOD( EndDate__c - StartDate__c, 7),0,1,2), 
  6 , CASE( MOD( EndDate__c - StartDate__c, 7),6,2,1),
  (FLOOR(( EndDate__c - StartDate__c )/7)*2)


Credits to Julie Nguyen from the answers community for the tip.