Skip to main content

Know More About Person Account (B2C Account)

 Enable Person Accounts

1. Make sure you meet the following prerequisites.

    • The account object has at least one record type.
    • User profiles that have read permission on accounts have read permission on contacts.
    • The organization-wide default sharing is set so that either Contact is Controlled by Parent or both Account and Contact are Private.

2. From Setup, enter Account Settings in the Quick Find box, and then select Allow Customer Support to enable Person Accounts.
Salesforce will verify your org meets the prerequisites, then send you an email with additional information. If you don’t see a message verifying you meet the prerequisites, go back to first step.

3. Contact Salesforce Customer Support by logging a case to enable Person Accounts.
Refer to the email we sent about what to include in the case.

4. After Person Accounts is enabled, a person account record type is created. You can create additional record types for person account if needed.

5. Assign the person account record type to user profiles.

Note: Once Person Account enabled you cannot disable it. So read the consideration Carefully.

Remember Person Account data are stored in Account and Contact, but you will not see Contact data of Person Account from UI. To access Contact in Automations use PersonContactId(Field API name).

If you have any questions regarding Person Account please Comment below. 
 

Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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 />
Post a Comment
Read more

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
Post a Comment
Read more

Translate