On last 17th of March, we gathered to celebrate Happy Birthday of Salesforce and Spring17 Release Party. Started with Intros and watched keynote featured by Marc Benioff. Followed by Pre-show with special guests & Keynote with Product managers.


Discussed some most awaited feature of Spring17 and watched some videos shared by Community team. Then had a Trivia, ended with some Prizes.




Awesome and Super Yummy cupcakes are waiting for us, all had a Super Fun together with a Big Shout out of  'Happy Birthday Salesforce'.
















A Big Thanks to Salesforce Team for all the Helps and swags & all. Last but not least thanks very much everyone to join us.

Your Org has tens of thousands of users, tens of millions of records, or hundreds of gigabytes of total record storage, have to follow best practices. Few Considerations:

Skinny Tables
Recommended to make your query fast. Important for batches taking long time to execute.

Indexes
Use index fields in where clause of Query. Multiple indexed field in query make it more faster. Even use Two-Column Custom Indexes. Two-column index is more efficient than single indexes on same fields.

Divisions
Partitioning the data of large deployments to reduce the number of records returned by queries and reports. For example, a deployment with many customer records might create divisions called US, EMEA, and APAC to separate the customers into smaller groups that are likely to have few interrelationships.

Mashups
One approach to reducing the amount of data in Salesforce is to maintain large data sets in a different application, and then make that application available to Salesforce as needed.

Deleting Data
Delete unused or unnecessary data. Use Bulk API's hard delete option, which allows records to bypass the Recycle Bin and become immediately available for deletion.

Search
When large volumes of data are added or changed, the search system must index that information before it becomes available for search by all users, and this process might take a long time.

Indexing with Nulls
Idea to reduce Null values, replace with NA or blank. Either use formula field to set value and index formula field.

API Performance
Add addition filter in rest API's query, so they dont scan all salesforce data.

Sort Optimization on a Query
Add a limit or sort order in query to make it fast and scan a limit of data only.

1. Checkbox
2. Date
3. Date and time
4. Email
5. Number
6. Percent
7. Phone picklist
8. Picklist (multi-select)
9. Text
10. Text area
11. Text area (long)
12. URL

Lightning Experience is a modern CRM user interface optimized for speed. A component-based framework that allow you to build reusable components to customize the Lightning Experience. Drag-and-drop technologies for fast and easy app building & customization. You can create a custom Lightning tab that points to your component and include that tab in your Salesforce1 Mobile navigation. We already have Visualforce components, they are page-centric and most of the work is done on the server. Lightning is designed from the component up, rather than having the concept of a page as its fundamental unit. Lightning Components are client-side centric, which makes them more dynamic and mobile-friendly. You can also use Lightening Components in Visualforce Pages, see this.
From Setup in Salesforce Classic, click Lightning Experience. On the Lightning Experience Migration Assistant page, click the Lightning Experience button to set it to Enable.

The Concurrent Apex Limit exceeded issue is big issue in large data Orgs or implementations without following best practices. Exception generally received by end user or Admin:

"Unable to Process Request. Concurrent requests limit exceeded.
To protect all customers from excessive usage and Denial of Service attacks, we limit the number of long-running requests that are processed at the same time by an organization. Your request has been denied because this limit has been exceeded by your organization. Please try your request again later."

Salesforce Developer Blog Says:

The multitenant Force.com platform uses governor limits to ensure that system resources are available to all customers and to prevent any one customer from monopolizing them. If a governor limit is exceeded, the associated execution governor limit issues a runtime exception that cannot be handled. When you design your applications, you can help plan for their growth by keeping these limits in mind.

One of the limits customers frequently reach is the concurrent request limit. Once a synchronous Apex request runs longer than 5 seconds, it begins counting against this limit. Each organization is allowed 10 concurrent long-running requests. If the limit is reached, any new synchronous Apex request results in a runtime exception. This behavior occurs until the organization’s requests are below the limit.

Ultimately, this limit is in place to protect the user experience. Would you want your users waiting 5 seconds or more for a page to load?

So how would you know which operation is taking time? Even you can track it through Debug logs using many filter Extensions like 'Salesforce Debug Logs Analyzer'. One more level is Salesforce Event Log, obviously you should have access of it.

Go to https://salesforce-elf.herokuapp.com/

Login with your Salesforce Sandbox or Production login. Select dates range and apply, now you can download Salesforce Event Log File by Event Type.

Open in excel and Sort by Execution Time and see where its taking time, optimize that using best practice or adjusting business rules.

If the cause was a high callout time, you can filter your ApexExecution file based on QUIDDITY (E, H, M, R, V, W, X, L, K, or I) and CALLOUT_TIME (>5000), both of which were added in the Spring '16 release.

The values for quiddity in the logs include:

A - Legacy Batch Apex
C - Schedule Apex
E - Inbound Email Service
F - Future
H - Apex REST
I - Invocable Action
K - Quick Action
L - Aura
M - Remote Action
Q - Queuable
R - Synchronous
S - Serial Batch Apex
T - Apex Tests
TS - Synchronous Apex Tests
TA - Asynchronous Apex Tests
V - Visualforce
W - SOAP Webservices
X - Execute Anonymous

Guest site user debug is not showing in debug log, it is related to Winter 17 change. Now need to set a special cookie from their side so that Salesforce will generate logs only when that user accesses the site.

Public users generate a large volume of events, which can quickly fill up your debug logs. For this reason, logs are collected for site visitors who are using your Guest User license only when a public user’s browser has a special cookie. This feature is available in both Lightning Experience and Salesforce Classic.

The debug logs are collected for site visitors who are using the Guest User license only when a public user’s browser has a special cookie.

The value of the cookie should be
Name : debug_logs
Value: debug_logs
domain: .force.com

To set this cookie via Chrome, Navigate to the Site URL,
Go to Developer tools and then to Console tab, Execute the below java-script
document.cookie ="debug_logs=debug_logs;domain=.force.com";

Also if you access the site using API, you can set the cookie in the same format. For example, when connecting to the site using JAVA, you can
use URLConnection class and set the cookie value as below

URL url = new URL("http://*********-developer-edition.gus.force.com/");
URLConnection con = url.openConnection();
con.setDoOutput(true);
con.setRequestProperty("Cookie", "debug_logs=debug_logs,domain=.force.com");
con.setRequestProperty("Content-Type", "text/plain; charset=utf-8");
con.connect();

General Enhancements