Deepak
IndividualForum Replies Created
-
Utility classes are helper classes that consists of reusable methods. From triggers we can call methods in such public classes. This helps to reduce code with in trigger and make it more structured.
-
REST API has no has no official standard at all because it is an architectural style. SOAP API, on the other hand, has an official standard because it is a protocol. REST APIs uses multiple standards like HTTP, JSON, URL, and XML while SOAP APIs is largely based on HTTP and XML.
-
A "Connected App" is an application that can connect to salesforce over Identity and Data APIs. Connected Apps use the standard OAuth 2.0 protocol to authenticate, provide Single Sign-On, and acquire access tokens for use with Salesforce APIs.
-
Setup Audit Trail tracks the recent setup changes that you and other admins make to your Salesforce org. Audit history is especially useful in orgs with multiple admins. To view the audit history, from Setup, enter View Setup Audit Trail in the Quick Find box, then select View Setup Audit Trail.
-
Methods defined with the @testSetup annotation are used for creating common test records that are available for all test methods in the class.
-
If we are processing 10,000 records and batch size is 100 then number of times a batch's execute method will be called is 10000/100 = 100 times. This number comes from chunking on Salesforce side which is called as retrieveChunkSize.
-
A case assignment rule in Salesforce is really a grouping of rules that will help you automatically assign cases throughout your support organization based on criteria captured on the case records. Each assignment rule can have multiple rule entries.
-
Conditional Highlighting in Salesforce Report is used to highlight field values on summary or matrix reports based on ranges and colors you specify. To enable conditional highlighting, your report must contain at least one summary field or custom summary formula.
-
Chatter is an enterprise collaboration platform from Salesforce, a cloud-based customer relationship management (CRM) vendor. Chatter can be used as a company intranet or employee directory. Like Facebook and LinkedIn, Chatter allows users to manage their feeds and control how notifications are received.
-
AMPscript is a scripting language that you can embed within HTML emails, text emails, landing pages, SMS messages, and push notifications from MobilePush. The system processes the script at the point where you include it in the message to render content on a subscriber-by-subscriber basis.
-
A custom setting is very similar to a custom object, the main difference is that the custom setting is cached. It is especially useful to store information that will be often accessed from Apex code as it will perform better than a custom object as it doesn't have to be queried, it is also easier to manage it.
-
You cannot call another future method from a future method. As per Salesforce documentation, You cannot call a method annotated with future from a method that also has the future annotation. If you do not have dependency between f1 & f2, you can call both methods one by one from original class.
-
Apex test classes are placed in the Apex job queue for execution. The maximum number of test classes you can run per 24-hour period is the greater of 500 or 10 multiplied by the number of test classes in the org.
-
Virtual class are functional classes and can be instantiated or extended without then need of overriding methods. virtual class. child class interact with parent class using extend keyword.
-
Custom labels are text values stored in Salesforce that can be translated into any language that Salesforce supports. Use custom labels to create multilingual applications that present information (for example, help text or error messages) in a user's native language.
-
Only global admins can create org-wide teams and currently an org-wide team is limited to organizations with no more than 5,000 users.
-
This error usually generates when variables are not initialised.You have to initialised a variable.
-
A duplicate record set is a list of items identified as duplicates. It's created when a duplicate rule or job runs. Let your Lightning Experience users merge duplicates by granting them access to duplicate record sets.
-
You can create up to 5,000 custom labels for your organization, and they can be up to 1,000 characters in length. Custom labels from managed packages don't count toward this limit.
-
A Report is a document which contains data in an organized tabular or graphical format prepared for a certain period of time. Salesforce report is a list of data generated based on the criteria defined. Reports have access to Salesforce data and can be used to display in terms of rows and columns.
-
A dashboard shows data from source reports as visual components, which can be charts, gauges, tables, metrics, or Visualforce pages. The components provide a snapshot of key metrics and performance indicators for your organization. Edit Dashboards in Accessibility Mode in Salesforce Classic.
-
MetaData is simply Data that describes other Data.
For e.g.
For an object account, Create a new record of Account with name ‘Algoworks’ where name is MetaData and Algoworks is data. -
Salesforce Lightning Bolts are Industry solution templates built by an ecosystem of partners, helping you get to market faster. Lightning Bolts contain industry process flows, Apps, Lightning Components, and Communities, all integrated seamlessly with the Salesforce platform and CRM.
-
With Customer 360 Data Manager, you can map data between your connected data sources and the Cloud Information Model. The mapping sets you create between schemas in Customer 360 Data Manager can align and transform data across sources, making the data available through data federation services for your implementation. The Cloud Information Model is a schema used to communicate between connected data sources with different data structures and formats. It defines the standard subject areas, entities, and attributes for Salesforce clouds.
To get started with data mapping, you first add a connected data source to Customer 360 Data Manager. After you connect sources, Customer 360 Data Manager can access that source schema so that you create mapping sets between objects and fields within it and the Cloud Information Model.
Mapping Sets
A mapping set in Customer 360 Data Manager is a group of related objects that you want to transform with part of the Cloud Information Model. Each mapping set includes a source schema and a target schema. For example, a mapping set can map the Account object in Service Cloud and the Individual entity in the Cloud Information Model. You can then edit mapping sets by adding other related objects and fields. Search for objects within the data source schema to add them to the mapping set. Then map individual fields, or attributes, between your data source and the Cloud Information Model.
Identify Data to Map
You can use Customer 360 Data Manager mapping sets to create integrated experiences with your connected data sources. For example, you can use mapped data to create person accounts in your Salesforce org. When you’re working in Service Cloud, you can query mapped Commerce Cloud person account order data. Before you get started with these integrated experiences, review these mapping requirements.
Create a Mapping Set
A mapping set is a group of mappings and data filters between a data source schema and the Cloud Information Model. Salesforce provides mapping set templates that include default mappings. After you connect a data source in Customer 360 Data Manager, you can select mapping set templates to create and edit.
Remove a Mapping Set
If you no longer need a mapping set in Customer 360 Data Manager, you can delete it. Deleting a mapping set doesn’t affect any external objects or components that use the mapping set unless you activate a mapping version with your changes.
Create a Mapping
Map a data source schema attribute with an attribute in the Cloud Information Model in Customer 360 Data Manager.
Add and Configure Object Data
To customize and enhance your mapping sets in Customer 360 Data Manager, add objects. When you add objects, you can map that data between the data source and the Cloud Information Model.
Set a Fixed Value
To consistently set a field data value for a mapping in Customer 360 Data Manager, use fixed values. For example, you want to map a fax name from the Account object in Service Cloud with the Contact Point Phone field in the Cloud Information Model. You can set a fixed value of Fax for the PrimaryPhoneTypeID to identify the type of phone number.
Remove a Mapping
You can remove an existing mapping between your data source attribute and the Cloud Information Model in Customer 360 Data Manager.
Remove an Entity
With Customer 360 Data Manager, you can use mapping sets to map data across your data sources in a way that is most meaningful to your organization. As you customize your mapping sets, you can remove entities from your previously mapped data source or data target. For example, you can remove a contact point instance that you mapped on the Cloud Information Model from the mapping set.
Refresh Schemas
To ensure that your mapping sets use updated data source schemas, you can refresh the schemas in Customer 360 Data Manager. For example, if you add an object or field to Service Cloud, refresh the schemas to access the new object in your mapping sets.
Activate a Mapping Version
When you’re ready to use data from one data source in another data source, such as displaying order information from Commerce Cloud in a Service Cloud component, you activate a mapping version in Customer 360 Data Manager. This process saves a version of your mapping sets that are used by components that you set up. Any changes you make to mapping sets, such as adding objects or deleting mappings, aren’t applied to components until you activate a new mapping version.
Revert Mappings
To restore the original mappings provided in the default Customer 360 Data Manager mapping sets, you can revert mapping sets. Any changes you make to mapping sets, including this revert process, aren’t applied to the components until you activate a new mapping version. -
The SOAP API is focussed towards accessing data and manipulating records, whereas the Metadata API focusses on Metadata. This API is uses to manipulate layouts, visualforce pages, apex triggers and classes- pretty much everything that you can do from the browser interface. Metadata API is not just used to fetch.