Pages

July 26, 2017

Divisions let you segment your organization's data into logical sections, making searches, reports, and list views more meaningful to users. Divisions are useful for organizations with extremely large amounts of data.

Divisions can be assigned to users and other kinds of records. For example, you can create a report to show the opportunities for just the North American division to get accurate sales numbers for the North American sales team.

Record-level division - Division is a field on individual records that marks the record as belonging to a particular division. A record can belong to a division created by the administrator or the standard “global” division. The standard global division is created automatically when your organization enables divisions. A record can belong to only one division at a time.

Default division - Users are assigned a default division that applies to their newly created accounts, leads, and custom objects that are enabled for divisions.

Working division - If you have the “Affected by Divisions” permission, you can set the division using a drop-down list in the sidebar. Then, searches show only the data for the current working division. You can change your working division at any time. If you don’t have the “Affected by Divisions” permission, you always see records in all divisions.

Divisions are not available by default in Salesforce. Contact Salesforce support to enable Divisions in your organization.

Enabling Divisions have prerequisites. Check the below link for the prerequisites

BigObjects let you store and manage large amounts of data on the Salesforce platform.
Within Force.com, objects are used to store and access data. Different kinds of objects are provided with different capabilities to align with different use cases. Standard Objects store data as defined by Salesforce while Custom Objects are created to store information unique to your organization. External Objects are provided to connect to data that is stored outside of your Salesforce organization.

July 23, 2017

If you navigate elsewhere in the UI while the asynchronous code is executing, the framework un renders and destroys the component that made the asynchronous request. You can still have a reference to that component, but it is no longer valid.

The cmp.isValid() call returns false for an invalid component.

If you call cmp.get() on an invalid component, cmp.get() returns null.

If you call cmp.set() on an invalid component, nothing happens and no error occurs. It’s essentially a no op.

In many scenarios, the cmp.isValid() call isn’t necessary because a null check on a value retrieved from cmp.get() is sufficient. The main reason to call cmp.isValid() is if you’re making multiple calls against the component and you want to avoid a null check for each result.

Help support agents decrease customer frustration, and improve support. Community 360 shows support agents working in the console whether customers have already looked at pertinent documentation and if they’ve already filed any cases before calling support. Agents don’t suggest articles customers have already accessed, or open duplicate cases. This feature is new in Lightning Experience.

To use Community 360, contact Salesforce to enroll in the public pilot program. Then you can enable it in the communities where you want to gather information and give the profile permissions to your support agent.

To enable it in the community, select Gather Community 360 data preference in the Administration workspace.

Lightning for Gmail is now generally available, and with our latest features, your team gets a boost in productivity. And reps get to relate emails to Salesforce before sending them. Crafting emails is faster with the use of Lightning email templates.

Salesforce introduces the Embedded Login feature to authenticate your website’s visitors. Your web developers can add login capabilities to the website with just a few lines of HTML. Embedded Login connects your website with Salesforce. This feature works for communities created with either our Communities or Salesforce Identity products. This feature is new in both Lightning Experience and Salesforce Classic.

July 16, 2017

Commerce Cloud is one of the eight product clouds that make up the Salesforce Intelligent Customer Success Platform.

With Commerce Cloud, retailers and brands can cater to their customers’ individual needs whether that’s online or in person. Commerce Cloud sites can be used across different devices and can personalize each shopper’s experience with dynamic content on web and mobile sites and smart product recommendations. If you shop online, you’ve probably used several Commerce Cloud sites without even knowing it!

July 15, 2017

Used to Deploy Metadata from Non-Certified Package Versions via Apex. By enabling this setting, ISVs can test managed packages that aren’t yet certified, and enterprises can use managed packages to test or update their apps. But as long as it’s turned off for your org, you can rest assured that no uncertified package can modify your org.

July 6, 2017

PK stands for Primary Key — the object’s record ID — which is always indexed. With this method, customers first query the target table to identify a number of chunks of records with sequential IDs. They then submit separate queries to extract the data in each chunk, and finally combine the results.

With the arrival of the Spring ’15 release, we’re pleased to announce that PK Chunking is a supported feature of the Salesforce Bulk API. Now you can get the performance benefits of PK Chunking without doing all the work of splitting the queries into manageable chunks. You can simply enter a few parameters on your Bulk API job, and the platform will automatically split the query into separate chunks, execute a query for each chunk and return the data.

July 4, 2017

When updating the role hierarchy or group membership through integration or the administration console, customers might occasionally receive a “could not acquire lock” error and have to repeat the operation. This error occurs because the sharing system locks the tables holding group membership information during updates to prevent incompatible simultaneous updates or timing issues, both of which could lead to inaccurate data about users’ access rights. Typically, these locks are held only very briefly, so most customers will never see a lock conflict error. In some scenarios—such as a change in role triggering a sharing rule recalculation—locks might be held for a longer time, and conflicts might occur.

Customers who experience these locking errors are typically executing large-scale data loads or integrations with other internal systems that are making changes to a role and group structure, user assignments to roles and groups, or both. When these processes are running—and an administrator tries to change a user’s role, or the customer tries to provision a new portal user—one of these simultaneous operations might be unable to secure the lock it requires. The most likely time for this failure to occur is during periodic organizational realignment events, such as end-of-year or end-of-quarter processing, where many account assignments and user roles are changing.

14. What is the advantage of using JavaScript Remoting over apex:ActionFunction?

Use JavaScript remoting. Unlike the <apex:actionFunction> component, JavaScript Remoting does not require a form component. This technique doesn’t reduce the overall view state of a page, but your page generally performs better without the need to transmit, serialize, and deserialize the view state. The tradeoff is the loss of the re-render attribute and the additional JavaScript code to handle callbacks.15. “could not acquire lock” error in Salesforcehttp://www.infallibletechie.com/2017/07/could-not-acquire-lock-error-in.html

16. What happens to files related to a lead after converting it?

Files will be in the related list of Account, Person Account(if used), Contact and Opportunity.

Salesforce customers who manage large data volume in their orgs must architect record ownership carefully to ensure peak performance. When you have a large number of records owned by a single user in Salesforce, we call that an “ownership skew”.

One of the common patterns involves customers concentrating ownership of data so that a single user or queue, or all the members of a single role or public group, owns most or all of the records for a particular object.

If the user(s) must have a role in sharing data, we recommend that you:

1. Place them in a separate role at the top of the hierarchy
2. Not move them out of that top-level role
3. Keep them out of public groups that could be used as the source for sharing rules