Skip to main content

Audit Fields and it's Detailed Description

Audit Fields:
CreatedByIdreferenceID of the User who created this record. CreatedById fields have Defaulted on create and Filter access.
CreatedDatedateTimeDate and time when this record was created. CreatedDate fields have Defaulted on create and Filter access.
LastModifiedByIdreferenceID of the User who last updated this record. LastModifiedById fields have Defaulted on create and Filter access.
LastModifiedDatedateTimeDate and time when a user last modified this record. LastModifiedDate fields have Defaulted on create and Filter access.
SystemModstampdateTimeDate and time when a user or automated process (such as a trigger) last modified this record. In this context, "trigger" refers to Salesforce code that runs to implement standard functionality, and not an Apex trigger. SystemModstamp fields have Defaulted on create and Filter access.
  • The only audit field you cannot set a value for is systemModstamp.
  • If you import data into Salesforce and want to retain the audit field values of the source system, you can set the values for audit fields on the following objects: Account, ArticleVersion, Attachment, CampaignMember, Case, CaseComment, Contact, ContentVersion, Contract, Event, Idea, IdeaComment, Lead, Opportunity, Question, Task, Vote, and custom objects.
    1. From Setup, enter User Interface in the Quick Find box, then select User Interface under Customize.
    2. Under Setup, select Enable “Set Audit Fields upon Record Creation” and “Update Records with Inactive Owners” User Permissions.
    3. In the permission set or profile that you want to set audit fields with, enable the permission Set Audit Fields upon Record Creation.
    4. Using the API, create a record and set its audit fields.
Not all standard objects have all audit fields. Check the Enterprise WSDL to verify which audit fields are available for a given object.

This is not possible on update, only insert. You can promote the idea on updating the existing records audit fields in Ideas.

Stepwise Explanation:


Popular posts from this blog

Platform Developer I Certification Maintenance (Winter '23)

 Maintain Your Platform Developer I Certification for Winter ’23 1. Field update actions have changed in API Version 54.0. Which record-triggered flows do field update actions now execute? Answer: Before-Save after After-Save 2. Which Apex class is used to determine the hostnames for the domains that Salesforce hosts for your org? Answer: System.DomainCreator 3. Which modules can be used for notifications in a Lightning web component instead of native APIs? Answer: LightningAlert, LightningConfirm, and LightningPrompt 4. What determines an org’s “shape” in Salesforce? Answer: Features, settings, edition, limits, and licenses 5. Which lightning-modal-* component is required to create a modal? Answer: Body 6. How do you call an invocable action from Apex code? Answer: Reference Invocable.Action Get Hands-On With Apex Assertions 1. Create Two Apex class: Copy and Paste below codes (A.) TestFactory @isTest public class TestFactory {    public static Account getAccount(String accountName, B

Custom Table In LWC

I'm assuming you've Basic understanding of Lightning Web Component, I'll be explaining you the syntax that will be generic. HTML: < template > <!-- Header Part -->      < lightning-card   title = "Custom Data table in Lightning Web Components" >          < div   class = "slds-grid slds-gutters" >              < div   class = "slds-col" >                  < span ></ span >              </ div >              < div   class = "slds-col" >                  < span > <!--A Button For extra feature-->                      < lightning-button   label = "Show Selected Contacts"   onclick = {showContacts}   style = "margin-left: 40%"   variant = "brand" > </ lightning-button >                  </ span >              </ div >          </ div >< br />

LWC js-meta.xml Configuration File Tags

Each Lightning web component folder must include a configuration file named <componentName>.js-meta.xml. The configuration file defines the metadata values for the component, including the design configuration for the Lightning App Builder and Community Builder. Some Standard Key metadata values: apiVersion : A double value that binds the component to a Salesforce API version. isExposed : If isExposed is false, the component is not exposed to Lightning App Builder or Community Builder. To allow the component to be used in Lightning App Builder or Community Builder, set isExposed to true and define at least one <target>, which is a type of Lightning page. Some Standard Optional metadata values: description : A short description of the component, usually a single sentence. masterLabel : The title of the component. Appears in list views, like the list of Lightning Components in Setup, and in the Lightning App Builder and in Community Builder. targets : Specifies wher