#CRM Configuration43 personnes en discutent

Hey Chandra, 

1. From Setup, enter Session Settings in the Quick Find box, then select Session Settings.
2. Review the default settings for Lightning Login.
   1. Make sure that Allow Lightning Login is enabled.You can disable Allow Lightning Login at any time to switch users back to username and password logins.
   2. Decide if you want to make Lightning Login available to all users or only users with the Lightning Login User permission.
   3. Confirm that a Standard session security level is appropriate for this login method.Lightning Login establishes a Standard security level for the user’s session. Standard is the default security level for the Username Password method that Lightning Login typically replaces. If needed, you can change the security level to High Assurance.
3. Assign the Lightning Login User permission to users in the user profile (for cloned or custom profiles only) or permission set. Lightning Login isn’t supported for external users.

The algorithms that are used vary depending on if you're using the standard matching rules or custom matching rules and what fields you are matching on. It's been a long time since I dived into this, but the documentation was pretty helpful here:  

-

-

@SYED ZAIN This is not helpful. The configuration you show above cannot be saved, or you have a custom lookup named "Case" which is why you're seeing that. It looks like you just typed "Cases" and didn't actually try to save the record, as that's a non-existent relationship and cannot be saved as shown.  

@Jafar Shaikh The reason the Cases related list doesn't appear on Opportunity using the standard lookup field (even thoughthe Classic UI shows it as being on the page) is because there is no direct relationship between Case and Opportunity: Cases are related to Contacts or Accounts, not Opportunities. 

The article How to Show Account-Related Cases on the Opportunity Page Layout in Salesforce is factually correct but further misleading and needs updating: The instructions are to use the Lightning UI to update the Classic Page Layout, but it still isn't possible to add Cases as its own related list or custom tab on Opportunity (it will only appear in the legacy "Related List" panel with every single related list). 

The workaround is to create a custom lookup on Case, named Opportunity (name the Related List Label "Case" also), then if you drag that one into the layout, you can use it in Lightning Record Pages and Dynamic Forms. 

Add this to this list of # stupidsalesforcebugsthatwillneverbefixed.

Hello @Shiva Yadav

When an object is migrated to Dynamic Forms, the "classic" Page Layout editor no longer dictates the fields displayed on the Lightning record page. Even if you add the field to the classic layout, the Lightning page must be updated manually.

Recommended Troubleshooting Steps

Check for Dynamic Forms: Navigate to a record of the object, click the Gear icon (top right), and select Edit Page to open the Lightning App Builder. If the page uses Dynamic Forms, you will see a Field Section component where you must manually add the new field to the canvas.

Verify Field Visibility Filters: Within the Lightning App Builder, select the field you added. Check the right-hand panel for any Set Component Visibility filters. If a filter exists, it may be hiding the field based on the values of other fields.

Clear Browser Cache: Salesforce Lightning frequently caches UI metadata. If you recently made changes, they may not reflect immediately. Try refreshing your browser (or using an Incognito/Private window) to rule out caching issues.

Check Record Type Assignments: Ensure the record type you are using is assigned to the correct page layout and that your profile has access to that specific record type.

Verify Deployment Status: Check that the object's Deployment Status is set to Deployed (and not "In Development"), as "In Development" status can restrict visibility to system administrators only. 

Hello Galina,

Currently, in Salesforce, the Contact Suggestions component is available only on the Seller Home page and isn’t exposed as a reusable Lightning component. Because of this, it can’t be added to a custom Home page using the Lightning App Builder.

The Seller Home page is a specialized system page designed for sales users and has limited customization options. Salesforce has not made the Contact Suggestions widget available for use on other Lightning pages, which is why it doesn’t appear as an option in the App Builder when configuring a custom Home page.

As a workaround, you could consider creating a custom Lightning Web Component (LWC) that displays suggested contacts based on criteria such as recent activities, upcoming tasks, or contacts associated with open opportunities. This custom component can then be added to a custom Home page. Another simpler option is to create a report or dashboard component highlighting relevant contacts and place it on the Home page.

At the moment, using Seller Home is the only way to access the standard Contact Suggestions component directly. 

References:

• Seller Home Overview – Salesforce Documentation 

• Lightning App Builder Overview – Salesforce Help 

I hope this provides some clarity on the current behaviour and possible alternatives.

Hi Alex,

In my case the OWDs are currently set to Public/Read/Write. I already have a Profile added to the user with "Read" on the relevant objects and "Edit" on Opportunities. My user is at the bottom of their Role Hierarchy branch. Sharing Rules & Permission Sets serve to further broaden visibility, so I am not yet sure how these will help get to the ideal state of my user only being able to see & edit records they own. Can you elaborate?

@Sara Reiss Steps to follow:

1.  Go to Setup
2.  Search for Activity
3.  Open Activity object 
4.  Go to List View Button Layout
5.  Edit the layout 
6. Uncheck “Assign Label”
7.  Save

The Assign Label button will be removed from:

•  Task list views

Before Changes:

After Changes:

Hope this helps! If it solved your problem, feel free to accept the answer - it might help someone else too 😊 

@Jon Guliker

Every time an Enhanced Notes is edited → a

•  You can see: 
  •  Who modified it 
  •  When it was modified 
•  Users can manually open previous versions 

This is the closest “audit” you get for Notes out of the box