Feed

Hi Shekhar,

You're running into a known incompatibility issue with the Chrome Beta channel release!

Salesforce UI elements like the "My Settings" lightbox popup rely heavily on specific JavaScript event handlers that often break or behave unexpectedly when Google updates pop-up/overlay rules in Chrome Beta or Developer builds.

Here are the best steps to fix and work around it:

1. Switch to Chrome Stable: Switch back to the stable release of Chrome (or use Firefox/IE temporarily) to confirm that the popup renders normally.
2. Direct URL Access: If you need to access your settings immediately in Chrome Beta without relying on the popup script, you can navigate directly to the URL by adding /ui/setup/Setup or /setup/personal/PersonalInformationPage to the end of your Salesforce instance domain URL in your address bar.
3. Disable Extensions: Occasionally, popup blockers or ad-block extensions in Chrome Beta interfere with Salesforce modal scripts, so try testing in an Incognito window with extensions disabled.

Hi Aruna,

Yes, there are a few built-in ways to identify records created or imported via Data.com

/ Jigsaw: 

1. Check the Created By or Last Modified By User When records are imported via Data.com, Salesforce automatically sets the record creator/modifier to the user who ran the import. However, if you are using automated sync/enrichment, they will often show as created by the Data.com System User or Jigsaw System User. You can filter reports where Created By: Name equals "Data.com

" or "Jigsaw". 

2. Look for the Data.com / Jigsaw Key Field Salesforce automatically populates unique Data.com identifiers on imported records:

• Query or report on the Jigsaw Company ID (or D&B Company ID / Data.com Key) field on the Account object.
• If Jigsaw Company ID Is Not Null / Is Not Blank, that Account originated from or was matched with Data.com!

3. Create a Report or List View

• Go to Reports > New Report > Accounts.
• Add a filter: Jigsaw Company ID greater than "" (or Is Not Blank).
• This will instantly give you a complete list of all Accounts created via or linked to Data.com.

Hope this helps you isolate those accounts!

Hello @Aur Fr

, 

Can you give us more details about the process who create the Work Plan when the SA status change ? 

Thank you. 

Alain

Hi Matt,

The standard QuoteNumber field in Salesforce is an auto-number field, which means its format is fixed across the entire object and can't dynamically change based on Opportunity criteria.

However, you can easily achieve this by creating a Custom Formula Field on the Quote object! Here's how:

1. Create a Custom Formula Field

• Go to Setup > Customize > Quotes > Fields and create a new Formula field (Text output type) named "Formatted Quote Number" (or similar).
• Use a formula like this to prepend your prefix/suffix based on the related Opportunity's Type:

IF(TEXT(Opportunity.Type) = "Special Category", "A-" & QuoteNumber, QuoteNumber)

(Replace "Special Category" with your specific Opportunity Type and "A-" with your required letter).

2. Update your Quote Template

• Go to your Quote Templates and replace the standard Quote Number field with your new custom formula field (Formatted Quote Number).

This keeps your underlying sequential auto-number intact while displaying the custom letter formatting whenever PDF quotes are generated!

Hi Robert,

This is a classic symptom of a sharing setting vs. list view filter conflict in Partner Portals!

Since the user can access the individual cases directly via direct URL, your underlying Sharing Rules and OWDs (Organization-Wide Defaults) are correct. The issue is strictly how the List Views and Related Lists are filtering the records.

Here are the most common causes and fixes:

1. Filter Scope on the List View Check the scope setting on those List Views. If the view is set to "My Cases", Salesforce evaluates "My" based on the logged-in Partner user as the Case Owner. If the Cases are owned by an internal user, queue, or different account, "My Cases" will filter them out, even if the partner has read access.

• Fix: Change the view scope to "All Cases" or "My Account's Cases" (if available) and filter by specific criteria instead.

2. Portal User Visibility Settings Go to Setup > Digital Experiences / Portals > Settings and verify:

• Portal User Visibility is enabled so partner users can see other records owned by users within their same account hierarchy.
• Double-check if Account Teams or Case Teams are involved in granting the direct URL access, as standard List Views don't always evaluate team-based access in the same way direct record access does.

Changing the List View filter scope from "My Cases" to "All Cases" usually resolves this immediately!