Dear all,
Are you able to share any expected final release date for dark mode? My Org won't allow using it since it is in Beta.
There is no final date announced yet. It can be enabled in your org bet version. What issue are you facing?
https://www.salesforce.com/blog/salesforce-dark-mode/
Hi everyone,
We are working with Salesforce Agentforce Employee Agent, and we need to store the conversations that users have with the agent for auditing and analytics purposes.
Our goal is to save:
We would like to know if there is any standard or recommended Salesforce configuration to store the full conversation between the user and the Employee Agent, so we can later perform analysis on those conversation records.
We are especially interested in understanding:
Has anyone implemented this successfully or can share the recommended pattern? @* Customer Success * @* Known Issues * @* Salesforce Administrators * @Salesforce Flow Automation @* Salesforce Developers * @Design Trailblazers @Slack + Agentforce
Hi, Keep in mind that Event logs store information for seven days and consumes Data 360 credits. Enable it with below steps:
I'm getting an error when trying to send an email from a Case using a Chatter component.
What’s curious is that even if I use files with different names, I still get the same error.
The error message is:
Has anyone experienced this before or knows what could be causing it?@* Customer Success * @* Salesforce Administrators * @* Known Issues * @* Salesforce Developers * @Design Trailblazers
Forum Ambassador
In Salesforce, each file share to a user, group, or record counts toward a limit, with a default maximum of 2,000 shares per file. If your current limit is below 2,000, Salesforce Support can restore it to the default without additional review. Check this help article for more info -
Increase the Maximum File Shares Limit in Salesforce FileHi Trailblazers! The design systems team is recruiting a limited cohort for two upcoming SLDS 2 pilots and want you involved! The two pilots are:
Pilot participants get direct access to the SLDS 2 product team and early configuration support. To join the pilot:
Spots are limited so please enroll by May 22nd!
Hi, When converting a Lead into a Contact, the Contact was assigned the “Student” record type, but it should not have happened that way.
The expected behavior is for the Contact to be created with the “Applicant” record type.
Where can I configure the default record type for Contact during Lead conversion, without modifying the standard conversion component, since the conversion is being done through the standard Salesforce process?
The curious part is that this only happens in the UAT environment.
In Production, when converting the Lead using the standard Salesforce conversion process, and without explicitly selecting a specific record type, the Contact is correctly created with the “Applicant” record type.
However, I cannot find where this behavior is defined at the configuration level, and I would like to understand what setting controls this default assignment.
Simply navigate to the user's Profile in the UAT environment, go to the Contact Object Settings, and change their Default Record Type from 'Student' back to 'Applicant'."
After enabling SLDS2, we observed a styling inconsistency in form labels: combobox labels render in bold by default, whereas checkbox labels remain normal. In SLDS1, both were rendered with normal font weight.
Hi @Brinda Popat @Shubham Navale, I have confirmed that for the Records page the bolding of the checkbox label is by design to ensure consistency with the rest of the fields & labels on the Records page. You can find a full set of checkbox examples in our storybook, which can also be accessed from our design system website
I understand dark mode is still in beta so I'm just passing along the feedback. We've noticed that some PDFs don't render correctly when viewed in dark mode. This seems to be particularly an issue when a table is present in the PDF.
Hi @Jason Mott please share more information to reproduce or screenshots of what you are seeing. PDF view in Salesforce should not have any dark mode styles.
We have one org with multiple business processes and development teams supporting each process. Can we switch one app over to SLDS 2 while keeping the other ones on SLDS 1?
Hi @Jakko Kleijnen Short answer is No.
Since SLDS is delivered as a core part of the Lightning Experience (LEX) platform, it is a global environment setting
. When Salesforce rolls out a major version update to the design system—such as the transition from SLDS 1.0 to the simplified, component-based architecture of SLDS 2.0 (or future iterations)—those changes affect the underlying CSS variables and global styles across the entire org.
That said, you could have
Strategies for "Phased" Migration
While you can't flip a switch for one app, you can manage the risk using these consultant-level strategies:
Consultant's Recommendation
If you try to maintain two versions of SLDS simultaneously via static resources, you will significantly increase your technical debt and page load times (as users will be downloading two heavy CSS libraries).
I recommend aligning all teams to a single migration window. Use Design Tokens instead of hardcoded CSS classes wherever possible; this makes your UI "version-agnostic" so that when Salesforce updates the underlying SLDS, your components adapt automatically.
Hey Design Trailblazers! 👋
We'd love your feedback on the SLDS 2 transition.
Whether you're in the process of analyzing custom components, testing SLDS 2 in sandbox, or using an SLDS 2 theme in production, please take 5 minutes to fill out this survey.
Your feedback directly shapes how we improve the experience for everyone transitioning to SLDS 2.
Thank you in advance!
We have noticed that some text in emails and comments section of cases are hard to read when the text there is black or gray. Users have to switch to light mode to read that.
Hi @Jeremy York, I'm the PM for Dark Mode & SLDS 2. You are correct Dark Mode is currently in beta, so thank you for reporting this bug. I was able to reproduce this issue in a test org on the chatter feed, so I will get this triaged in our backlog to fix. Let me know if you have encountered any other Dark Mode issues!
