MOHIT
IndividualForum Replies Created
-
A Cross-object formula is a formula that spans two related objects and references merge fields on those objects. A cross-object formula can reference merge fields from a master (“parent”) object if an object is on the detail side of a master-detail relationship. A cross-object formula also works with lookup relationships.
-
Provides row-based access to metadata about standard and custom objects.
This object is available in API version 32.0 and later. -
To set cacheable=true, a method must only get data. It can’t mutate data.
-
To improve runtime performance, set @AuraEnabled(cacheable=true) to cache the method results on the client. To set cacheable=true, a method must only get data. It can’t mutate data.
Marking a method as storable (cacheable) improves your component’s performance by quickly showing cached data from client-side storage without waiting for a server trip. If the cached data is stale, the framework retrieves the latest data from the server. Caching is especially beneficial for users on high latency, slow, or unreliable connections such as 3G networks. -
Salesforce allows a maximum of 10 unique relationships per object in cross-object formulas. The limit is cumulative across all formula fields, rules, and lookup filters. For example, if two different formulas on opportunities reference two different fields of an associated account, only one unique relationship exists (from opportunities to accounts).
-
Difference between Customer and Partner Portal
Partner Portal Shows the Leads and Opportunity objects whereas the Customer Portal does not. ... Customer Portal is more focused on support needs, so your customers can interact with cases. -
A campaign hierarchy allows you to group campaigns together within a specific marketing program or initiative, which enables you to analyze related marketing efforts more efficiently.
-
Always use the pre-built Visualforce list controller called ‘StandardSetController’, it prevents list view from displaying unbounded data. It allows the developer to configure list view to display up to 100 records at a time, but by default it returns 20 records on the page.
-
You can Use readonly attribute to display more than 1000 records.
-
We can display up to 2000 records on a page. If more records are there to display we cannot see those through user interface. If you export the records to a excel sheet then you can export all records.
-
Email services are automated processes that use Apex classes to process the contents, headers, and attachments of inbound email.
You can associate each email service with one or more Salesforce-generated email addresses to which users can send messages for processing. -
We should always use Component Events whenever possible this is because Component events can only be handled by parent components so the components in picture are only those components which need to know about them.
-
Lightning:actionOverride interface Enables a component to be used as an override for a standard action. We can override the View,New, Edit, and Tab standard actions on most standard and all custom components. The component needs to implement the interface Lightning:actionOverride after which the component appear in the Lightning Component Bundle menu of an object action Override Properties panel.
-
We recommend that you use different lead record types and page layouts to differentiate leads that convert to person accounts from those that convert to business accounts. Specifically, remove the Company field from the page layouts for leads that convert to person accounts. Then, make the Company field required on the page layouts for leads that convert to business accounts.
If you convert a lead that someone else owns and attach it to a person account that you own, the lead owner becomes the person account owner. -
A Regular Contact (business contact if you will) cannot be related to a Person Account using the default Account Name lookup field on the contact object.
However, Technically, you could create a custom lookup field on the contact object to a Person Account and using a lookup filter set to filter only on person accounts -
Person accounts store information about individual people by combining certain account and contact fields into one record. Business Contact Sharing for Orgs That Use Person Accounts. Orgs that use person accounts can modify the Organization-Wide Sharing Default for Contacts.
-
Data cleansing should be regular
70% of CRM data becomes obsolete each year, so regular data cleansing should become your routine. The most evident way to maintain data timeliness is to ensure that your in-house administrator or Salesforce support vendor regularly provides data cleansing with dedicated tools. Another measure you can take to fight obsolete data is to enforce weekly data cleansing activities to employees. For example, sales reps may clean up expired opportunity close dates and other CRM data, which is no longer relevant.
Data cleansing should be complemented with measures on sales-related processes improvement
Keeping your sales data clean is not a merely technical activity. It requires reviewing lead and opportunity management processes to unify standards for data input for different systems used in a company. For instance, sales reps use Salesforce Sales Cloud integrated with a marketing automation platform. If sales reps and marketing specialists do not have unified standards for data input (unified lead and opportunity name format, phone number format, etc.), duplicated data in CRM will be a result.
Data cleansing should be supported with proactive technical measures
According to 1-10-100 Rule, it takes $1 to verify a CRM record when it is initially inputted, $10 to clean it later, and $100 to do nothing (a result of lost opportunities and wasted time). To prevent the revenue drain caused by discordant sales data, you should take proactive technical measures to maintain data quality. For instance, an in-house Salesforce administrator (or the one from a Salesforce support service provider) can enable automated deduplication with Salesforce duplicate rules that help to identify and manage (delete, merge, etc.) duplicate records. The administrator can also introduce validation rules. They prevent the entry of data not compliant with the internal quality standards of the sales data in your company. For instance, a rule can validate that the opportunity’s close date isn’t prior to the current day or that the opportunity amount is a positive number. -
Custom objects in Salesforce are the database tables that help users to collect the information that is unique to the organization.
-
In Enterprise Edition, Unlimited Edition, and Performance Edition, you can schedule dashboards to refresh daily, weekly, or monthly. You can also set up Salesforce to send an email with an HTML version of the dashboard when the refresh completes. For email applications that don’t support HTML, the email includes text and a link to the dashboard. Each dashboard has a running user, whose security settings determine which data to display in a dashboard.If the running user becomes inactive, the report is not run. The system administrator receives an email notification to either activate the user, delete the report schedule, or change the running user to an active one in the scheduled report.
If you schedule a dashboard to refresh on a specific day of every month, it only refreshes on months that have that specific day. For example, if you schedule a refresh for the 31st of every month, the dashboard won’t refresh on 30-day months. To refresh on the last day of every month, choose “Last” from the On day of every month drop-down list.
Dashboards won’t refresh as scheduled if the running user doesn’t have access to the dashboard folder.
If a dashboard has filters, only the unfiltered version is refreshed.
You can’t schedule refreshes for dynamic dashboards. They must be refreshed manual -
It is not possible to re-parent or update an attachment's ParentId field via Data Loader to transfer attachments to other object's records. However, workarounds are available in order to move attachments to new or different records.
-
Salesforce Einstein Analytics (formerly known as Wave) is a cloud-based platform for connecting data from multiple sources, creating interactive views of that data, and sharing those views in apps. It's a better way to distribute insight to business users so they can understand and take action on changing information.
-
Salesforce Analytics Cloud, also known as Wave Analytics, is a cloud-based business intelligence (BI) system that provides an interactive platform to access and share business trends. The software provides data insights and helps to uncover new business opportunities.
-
Bucketing is a report and documentation feature in Salesforce. This feature allows you, the user, to easily and quickly categorize the records of different reports. This allows you to do just that without having to create a custom field or creating a formula.
-
<aura:attribute name="numbers" type="List"/>
<lightning:button onclick="{!c.getNumbers}" label="Display Numbers" />
<aura:iteration var="num" items="{!v.numbers}">
{!num.value}
</aura:iteration>/** Client-side Controller **/
({
getNumbers: function(component, event, helper) {
var numbers = [];
for (var i = 0; i < 20; i++) {
numbers.push({
value: i
});
}
component.set("v.numbers", numbers);
}
}) -
String myStr = 'abcdef’;
Integer result = myStr.length();