MOHIT
IndividualForum Replies Created
-
No, you should continue to use your current Marketing Cloud username and password to log in. Your Salesforce.com credentials will not work for the Marketing Cloud.
-
A sender profile specifies the from information for a send ie., ‘From Name’ and ‘From Email Address’, in a central location which can be used across multiple sends without the user needing to select it each time.
In a delivery profile, you specify the IP address and choose the header and footer to be used for a send. A delivery profile, similar to the sender profile, can be reused across multiple sends. -
AuraDefinitionBundle
Represents an Aura definition bundle. A bundle contains an Aura definition, such as an Aura component, and its related resources, such as a JavaScript controller. The definition can be a component, application, event, interface, or a tokens collection. -
Implements is use to refer platform interfaces which enables a component to be used in different contexts or to grant access to extra context data, a component can implement more than one interfaces.
-
A native app is an app for a certain mobile device (smartphone, tablet, etc.) They’re installed directly onto the device. Users typically acquire these apps through an online store or marketplace such as The App Store or Android Apps on Google Play.
When we talk about mobile web apps in this article, we’re referring to Internet-enabled apps that have specific functionality for mobile devices. They’re accessed through the mobile device’s web browser (i.e. on the iPhone, this is Safari by default) and they don’t need to be downloaded and installed on the device. -
Hi,
The benefits include an out-of-the-box set of components, event-driven architecture, and a framework optimized for performance.
Out-of-the-Box Component Set -: Comes with an out-of-the-box set of components to kick start building apps. You don’t have to spend your time optimizing your apps for different devices as the components take care of that for you.
Rich component ecosystem-: Create business-ready components and make them available in Salesforce1, Lightning Experience, and Communities.
Performance – :Uses a stateful client and stateless server architecture that relies on JavaScript on the client side to manage UI, It intelligently utilizes your server, browser, devices, and network so you can focus on the logic and interactions of your apps.
Event-driven architecture -: event-driven architecture for better decoupling between components
Faster development – : Empowers teams to work faster with out-of-the-box components that function seamlessly with desktop and mobile devices.
Device-aware and cross browser compatibility – : responsive design,supports the latest in browser technology such as HTML5, CSS3, and touch events. -
Consider the following before implementing the triggers.
Upsert trigger fires on 4 different events :- before(insert, update), after (insert, update)
Merge trigger are fired on both events on delete
Field history is updated after the trigger has successfully finished processing data.
Any callout should be asynchronous so that trigger does not have to wait for the response.
A trigger cannot have a static keyword in its code.
If a trigger completes successfully the changes are committed to the database and if it fails the transaction is rolled back. -
The BackgroundOperation object lets you view the job status for write operations via the API or SOQL. Monitor job progress and related errors in the org, extract statistics, process batch jobs, or see how many errors occur in a specified time period.
-
ContentDistribution represents information about sharing a document externally. It contains ContentVersionID which links the contentVersion object.
-
On the property record page in your org, click alt text: Setup Icon and select Edit Page.
Click on our new Lightning component to select it, then click alt text: Delete component to remove it from the page.
Click Save and then Back to return to your property detail page.
We’re now ready to use the component as a button override, so there’s no need for it to be on the page anymore.
In the Developer Console, switch back to the PropertyDialog component.
Add lightning:actionOverride to the list of interfaces in the aura:component tag. It should now look like this:
<aura:component implements="flexipage:availableForRecordHome,force:hasRecordId,lightning:actionOverride" access="global" >
Save the file.
It doesn't matter what order the interfaces appear in. lightning:actionOverride is the magic interface that instructs Lightning Experience to let us use this component to override a standard button or action.
Set Up the Override
Back in your org, click alt text: Setup Icon and select Setup.
Click Object Manager.
Click Property.
Click Buttons, Links, and Actions.
Click alt text: Dropdown menu icon next to New and select Edit.
Select Lightning Experience Override as Lightning Component.
Select c:PropertyDialog as the bundle to override with.
The select list will list all of the components in your org that have the lightning:actionOverride interface declaration.
Click Save.
Click alt text: App Launcher icon and select Dreamhouse Lightning, then click Properties.
Refresh this page, and then click New to create a new property.
And there it is! You've overridden the standard New button on the Property object with a Lightning component.
Note: If you don’t see your new form, then you may need to refresh your page again. Click Properties, refresh the page, and then click New. -
External IDs are commonly used to store unique record identifiers from external systems and allow for routinely loading data into Salesforce without having to prepare your import file with existing or related Salesforce record IDs each time.
-
Global search is always within easy reach at the top of the page so you can quickly find any searchable object in Salesforce. In Salesforce Classic, you can also use the sidebar search or advanced search.
Know which object you want to search for? In Lightning Experience, select the object in the dropdown list next to the global search box. You can also type the name of the object at the top of the dropdown list. If you don't want to limit your search to a specific object, type your search term in the search box.
As you type, you see suggested records.
Recently accessed items (in Salesforce Classic and Lightning Experience)
Items with matches on the name field (in Lightning Experience only)
Options to limit your search to a specific object (in Lightning Experience only)
We might also apply advanced search features to your search results.
Nicknames—Similar names are returned, like Mike for Michael.
Spell correction—Spell-corrected versions of search terms are returned, like widget for widgte.
Lemmatization—Similar words are returned, like sell, selling, sold.
Expanded query—Records whose name contains the term you entered are returned, like laptop for lap.
Special characters—When your search contains punctuation or special characters, records with similar names are returned, like 1234.SILVER for XYZ-1234-SILVER.
Your admin might have also set up synonym groups, which return records with similar words that have been grouped. For example, USB drive, flash drive, and memory stick.
On the search results page, your most relevant records appear first. The order of results depends several factors, such as how often your search term appears in a record, whether there's an exact match, how unique your search term is, and how much you've interacted with the record. We display only what you have access to. -
FieldDefinition. Represents a standard or custom field, providing row-based access to field metadata.
-
It indicates all object names from our org. in Salesforce.
-
Sf is used to indicate SalesForce.
-
Platform Cache is a memory layer that stores Salesforce session and org data for later access. When you use Platform Cache, your applications can run faster because they store reusable data in memory.
-
Track the Delivery Status of an Outbound Message. To track the status of an outbound message, from Setup, enter Outbound Messages in the Quick Find box, then select Outbound Messages.
-
A WSDL is an XML-document which contains a standardized description on how to communicate using a web service (the Salesforce API is exposed as a web service). The WSDL is used by developers to aid in the creation of Salesforce integration pieces.
-
Open the Developer Console.
Select Developer Console from the Your Name or the quick access menu (Setup gear icon).
Open the New Lightning Bundle panel for an Aura component.
Select File | New | Lightning Component.
Name the component.
For example, enter helloWorld in the Name field.
Describe the component.
Use the Description field to add details about the component.
Add component configurations to the new component.
You can select as many options in the Component Configuration section as you wish, or select no configuration at all.
Click Submit to create the component.
Or, to cancel creating the component, click the panel’s close box in the top right corner. -
An app is a collection of items that work together to serve a particular function. Salesforce apps come in two flavors: Classic and Lightning. Classic apps are created and managed in Salesforce Classic. Lightning apps are created and managed in Lightning Experience. You can customize both types of app to match the way your users work.
-
Objects are database tables that allow us to store data specific to the organization in salesforce.
-
No, we can't assigned two profiles to the same user in Salesforce.
-
Change Data Capture is a streaming product on the Lightning Platform that enables you to efficiently integrate your Salesforce data with external systems. With Change Data Capture, you can receive changes of Salesforce records in real time and synchronize corresponding records in an external data store.
-
an object of type Schema.DescribeSObjectResult that contains all the describe properties for the sObject or field. Describe result objects are not serializable, and are validated at runtime. This result object is returned when performing the describe, using either the sObject token or the describeSObjects method.
-
A roll-up summary field calculates values from related records, such as those in a related list. You can create a roll-up summary field to display a value in a master record based on the values of fields in a detail record. The detail record must be related to the master through a master-detail relationship. For example, you want to display the sum of invoice amounts for all related invoice custom object records in an account’s Invoices related list. You can display this total in a custom account field called Total Invoice Amount.