SALESFORCE #TIPS – Root Certification change from Digicert G1 to G2

Publié le par
Répondre

You have probably received a Salesforce notification about Digicert Root Certification change (from Digicert G1 to Digicert G2) on Salesforce side. Don’t throw this email !

Salesforce is about to impact its security certification structure, meaning that you will not be able to connect / interact with your Salesforce instance anymore, if your system or data integration chain is not prepared for this change.

Salesforce notification on the certificate change

Who is impacted by this change ?

You may be impacted, by the certificate change, in the following cases :

  • you use Salesforce through an outdated computer and web browser, or through a custom app whose code is not properly managed or contains hard-coded connectivity information.
  • your Salesforce instance is connected to other servers (for data synchronisation)
  • your Salesforce instance is connected to middleware solutions or integration platforms (for data synchronisation)

If you are in this case, and do not audit your connections / applications before February 5th, your users may experiment connectivity issues when trying to logging to / reaching out your Salesforce instance.

If you have developed custom applications, or data synchronisation processes / flows, make sure that you have not hard-coded certificate-related information in your code, due to either a lack of best practices, or because you have implemented certificate pinning on « to-be-expired » certificate for security purpose.

Am I concerned if I am a Salesforce user ?

To be able to connect to Salesforce (User interface, or technical one), you must ensure that your server / custom application / web browser trusts the Digicert G2 Root Certification.

Most users accessing Salesforce, through their web browsers, are already up-to-date, if they regularly update their browser application, when requested to do so. Indeed, all recent and browsers already includes this certification in their trust store.

To test its presence on your browser, you can either :

  • Or access directly your Chrome Root Store through your Chrome System page by navigating to : chrome://system. Click « Expand… » button on the chrome_root_store line :
Digicert G2 Root certificate – Access your Chrome trust store

You can also find the certificates handled by Chrome in the following document : https://chromium.googlesource.com/chromium/src/+/main/net/data/ssl/chrome_root_store/root_store.md

As you can see in the screenshots above, both G1 and G2 Root certifications are present in this Chrome trust store. Even G3 Root certification is present 🙂

Subject
CN=DigiCert Global Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US
CN=DigiCert Global Root G3,OU=www.digicert.com,O=DigiCert Inc,C=US

SALESFORCE #TIPS – How to manually create a case to Salesforce support without Agentforce

Publié le par
Répondre

A couple of months ago, I found a workaround link to be able to keep on creating cases to Salesforce support (https://help.salesforce.com), the good old way, with no Agentforce in the loop, knowing that I was able to correctly describe it.

https://help.salesforce.com/s/case-submission

By clicking this link, you land on a page that allows you to manually create your case :

SPRING’26 – Updated Label Translations

Publié le par
Répondre

Spring’26 release brings some new translations on standard labels for a few languages. Here is a very condensed table with all main tabs / names / labels that are changed :

Even if this change seems minor, do not forget to inform your change management team, about this change to allow them to communicate towards your final end-users.

In case you are forced to stick to the current name (that is not what I would recommend), and not switch to the new one, you would need to create a custom name (given the fact the new label will become the standard one, the former one should become a custom one..).

For information, you will find the full list below in the Review Spring ‘26 Updated Label Translations help article from Salesforce.

Language ↑English TermExisting TranslationProposed TranslationObject API NameTerm typeChange reasoning
Chinese (Simplified)Personalization Point个性化积分 / 个性化点个性化点PersonalizationPoint
PersonalizationPointDef		Object/TabTranslations fixed for consistency
Chinese (Traditional)visualization視覺化/視覺效果視覺效果OtherMajor style change
Chinese (Traditional)agent工作人員 / 智能體智能體AgentWork
AgentWorkActionVisibility
AgentWorkSkill
AiAgentUiConfig
CallCtrAgentFavTrfrDest
LiveAgentUserConfig
AiAgent
AiAgentVariable
AiPlannerRelatedAgent
MessagingBilledAgentMetric		Object/TabTranslations fixed for consistency
Chinese (Traditional)Journey流程/旅程旅程Global changeTranslations fixed for consistency
Dutchpredict jobvoorspellingstaak/taak van voorspellingvoorspellingstaakMktMLPredictionJob
MktMLPredictionJobDef
MktMLPredictionJobInput
MktMLPredictionJobOutput
MktMLPredJobOutputConfig		Object/TabTranslations fixed for consistency
FinnishComplianceVaatimustenmukaisuusMääräystenmukaisuusOtherTranslations fixed for consistency
FinnishMarketing IntelligenceMarketing Intelligence / Älykäs markkinointiÄlykäs markkinointiMktIntelSemanticModel,
MktIntelSchemaDataTemplate,
MktIntelSchemaObject,
MktIntelSchemaField,
MktIntelCampaignAttribution,
MktIntelAttribution,
MktIntelAttributionDs,
MktIntelAttributionIr,
MktIntelAttributionDashboard,
MktIntelAttributionDlo,
MktIntelAttributionDmo,
MktIntelAttributionWebSdk,
MktIntelAttributionSdm,
MktIntelAttributionModel,
MktIntelAttributionCrm,
MktIntelAttributionCalc,
MktIntelCampaignSummaryMetric,
MktIntelDataPipelineRun,
MktIntelDataPipeline,
MktIntelDataLakeObject,
MktIntelDataStream,
MktIntelDataTransform,
MktIntelSegInt,
MktIntelSegIntCrmCon,
MktIntelSegIntDataStream,
MktIntelAppTemplate		Global changeTranslations fixed for consistency
FinnishIdentity ResolutionIdentity-ratkaisu / Identiteetin ratkaisu / IdentiteettiratkaisuIdentiteettiratkaisuIdentityResolution
IdentityResolutionDefinition		Object/TabTranslations fixed for consistency
FinnishSegment IntelligenceSegmentin älykkyys / Älykäs segmentointiÄlykäs segmentointiMktIntelSegInt
MktIntelSegIntDataStream
MktIntelSegIntCrmCon		Object/TabTranslations fixed for consistency
FinnishExperimentKoe / KokeiluKokeiluAbnExperimentScndMetricDefObject/TabTranslations fixed for consistency
FinnishMetricsMetriikka / Mittataulukot / Tilasto / TilastotTilastotAdQuoteLinearMetrics
ComplianceUsgMetrics
InsPolicyMetrics
GroupBenefitUsageMetrics
CollectionPlanUsageMetrics
ClmMgmtCrUseMetrics
IntegrationEnvApplnMetrics
CmsnStmtLineItemUsageMetrics
ContentMetrics
SandboxMetrics
MessagingSessionMetrics
NetworkRegularMemberMetrics
DeflectionSignal
ProfileIpRestrictionMetrics
ExtIdentityLoginMetrics
NetworkPartnerLoginMetrics
NetworkCustomerLoginMetrics
NetworkPartnerMemberMetrics
NetworkCustomerMemberMetrics
TwoFactorMetrics
PlatformDailyUniqueLoginMetrics
NetworkPowerCustomerLoginMetrics
NetworkPowerCustomerMemberMetrics
NetworkPartnerDailyLoginMetrics
NetworkCustomerDailyLoginMetrics
NetworkLEAPlusDailyLoginMetrics
NetworkLEADailyLoginMetrics
NetworkPowerCustomerDailyLoginMetrics
ChatterMetrics
SharingMetrics		Object/TabTranslations fixed for consistency
FinnishData SourceTietolähde / DatalähdeDatalähdeInteractionDataSource
DataSource
DataSourceObject
ExternalDataSource
MktDataConnectionSrcParam
ExternalDataSrcDescriptor
RecAlrtDataSrcExpSetDef		Object/TabTranslations fixed for consistency
FrenchPromptRéplique/InviteInstruction générativeGlobal changeTranslation fixed for accuracy
JapaneseMilestone Typeマイルストーンタイプマイルストーン種別AssetMilestone_MilestoneTypeObject/TabTranslations fixed for consistency
Japanesevisualizationビジュアル化/視覚化ビジュアライゼーションOtherMajor style change
Koreanexperiment실험 / 시도 / 시험시험AbnExperiment
AbnExperimentCohort
AbnExperimentCohortAttrVal
InteractionExperiment
InteractionExperimentPath
AbnExperimentDef
AbnExperimentCohortDef
AbnExperimentParamValueDef
AbnExperimentScndMetricDef
AbnExperimentCohortAttrValDef		Object/TabTranslations fixed for consistency
Koreanvisualization시각화비주얼리제이션OtherMajor style change
NorwegianProducerProdusentForsikringsagentproducer
ProducerPolicyAssignment		Object/TabTranslation fixed for accuracy
PolishAssetzasób/środekzasóbOtherTranslation fixed for accuracy
PolishSecondary IndexesIndeksy dodatkoweIndeksy pomocniczeDataObjSecondaryIndexDef
DataObjSecondaryIndexDef_ID
DataObjSecondaryIndexDef_DeveloperName
DataObjSecondaryIndexDef_MasterLabel
DataObjSecondaryIndexDef_DataspaceScope
DataObjSecondaryIndexDef_SourceObject
DataObjSecondaryIndexDef_ShouldUseAllColumnsIncluded
DataObjSecondaryIndexDef_ScheduleExpression
DataObjSecondaryIndexDef_Status
DataObjSecondaryIndexDef_RuntimeStatus
DataObjSecondaryIndexDef_LastRefreshTime
DataObjSecondaryIndexDef_ComputeProcessReference
DataObjSecondaryIndexDef_SourceObjectType
DataObjSecondaryIndexDef_DataStorageObject
DataObjSecondaryIndexDef_Description
DataObjSecondaryIndexField
DataObjSecondaryIndexField_ID
DataObjSecondaryIndexField_FieldReference
DataObjSecondaryIndexField_SecondaryIndexType
DataObjSecondaryIndexField_FieldSequenceNumber
DataObjSecondaryIndex
DataObjSecondaryIndex_ID		Object/TabTranslations fixed for consistency
PolishShipping Carrier MethodSposób przewozu / Sposób dostawySposób dostawyShippingCarrierMethod
LocationShippingCarrierMethod		Object/TabTranslations fixed for consistency
SlovenianQuote Line ItemElement vrstice ponudbeVrstična postavka ponudbeBillinQuoteLineItemObject/TabTranslation fixed for accuracy
SlovenianBilling Milestone PlanNačrt mejnika izdajanja računovNačrt mejnikov izstavljanja računovBillingMilestonePlanObject/TabTranslation fixed for accuracy
SlovenianBilling ScheduleRazpored izdajanja računovRazpored izstavljanja računovBillingScheduleObject/TabTranslation fixed for accuracy
SlovenianBilling Milestone Plan ItemsElementi načrta mejnika izdajanja računovElementi načrta mejnikov izstavljanja računovBillingMilestonePlanItemObject/TabTranslation fixed for accuracy
SlovenianProduct Ramp SegmentSegment omejitve izdelkaNov segment skupine izdelkov z naraščajočo cenoProductRampSegmentObject/TabTranslation fixed for accuracy
Thaivisualizationการแสดงภาพ/การแสดงข้อมูลด้วยภาพ/การแสดงเป็นภาพการแสดงเป็นภาพOtherMajor style change
TurkishSecondary Indexesİkincil Dizinlerİkincil İndekslerDataObjSecondaryIndexDef
DataObjSecondaryIndexDef_ID
DataObjSecondaryIndexDef_DeveloperName
DataObjSecondaryIndexDef_MasterLabel
DataObjSecondaryIndexDef_DataspaceScope
DataObjSecondaryIndexDef_SourceObject
DataObjSecondaryIndexDef_ShouldUseAllColumnsIncluded
DataObjSecondaryIndexDef_ScheduleExpression
DataObjSecondaryIndexDef_Status
DataObjSecondaryIndexDef_RuntimeStatus
DataObjSecondaryIndexDef_LastRefreshTime
DataObjSecondaryIndexDef_ComputeProcessReference
DataObjSecondaryIndexDef_SourceObjectType
DataObjSecondaryIndexDef_DataStorageObject
DataObjSecondaryIndexDef_Description
DataObjSecondaryIndexField
DataObjSecondaryIndexField_ID
DataObjSecondaryIndexField_FieldReference
DataObjSecondaryIndexField_SecondaryIndexType
DataObjSecondaryIndexField_FieldSequenceNumber
DataObjSecondaryIndex
DataObjSecondaryIndex_ID		Object/TabTranslations fixed for consistency

To read more on the subject

WINTER’26 – User Field History – Find User History information

Publié le par
Répondre

As you have already learned from Salesforce Release Update documentation, and from my last article on this topic (« WINTER’26 – User Field History Tracking – new feature to track changes on Users »), Salesforce now allows to track changes on User records (beta feature coming with Salesforce Winter’26 release). We will see today where to find this information.

For the time being, you cannot add it on a User layout / lightning page, and you also need to wait for the different usual Salesforce extensions / tools need to be able to query on this new standard (v65.0) UserHistory object.

So, where can we visualize User History information in Salesforce new Winter’26 release ?

To access this information (as described in my previous article), you can indeed access this information from a custom report type !

Salesforce Winter’26 – And there are your latest tracked changes on user records

But, you can also access this information from the User page (click on the Avatar icon, and then on your name) :

Salesforce Winter’26 – User Field History Tracking – the avatar icon allows you to access your user page

From the Chatter part, you can visualize all recent updates with old and new values for fields tracked this way, or changes that happened for fields where only the change information is logged without values.

Salesforce Winter’26 – User Field History Tracking – Changes are followed in Chatter

Secondly, from the same user page, when you click on User Detail button, you access the traditional user record creation / update page.

Salesforce Winter’26 – User Field History Tracking – User Detail is available from the Avatar > User page
Salesforce Winter’26 – User Field History Tracking – View Summary is available in User detail page

On the top of the page, click on the View Summary button, and scroll down to the very bottom of the page in order to be able to visualize this user changes history, in a more compact and tabular way.

Salesforce Winter’26 – User Field History Tracking – Change summary is located at the bottom of the page

Even in beta, do not hesitate to quickly set up this feature to be more in control about what really happens when your user records are updated ! Have fun !

To read more on the subject

WINTER’26 – User Field History Tracking – new feature to track changes on Users

Publié le par
Répondre

With Salesforce Winter’26 new release, comes the beta User Field History Tracking feature. Follow the steps, described in this article, to easily enable this feature, configure it, and begin reporting on user records updates !

It was a pretty awaited feature (posted in IdeaExchange in 2008) that is now in beta !

Salesforce Winter’26 – The 17-year original post asking for this feature on IdeaExchange

To enable it, just navigate to Setup > User Management Settings.

Scroll down to the bottom of the page and toggle on the new « Enable User Field History Tracking (beta) » feature.

Salesforce Winter’26 – Enablement in Setup > User Management Settings

Once done, you would be able to define the User fields to track, as other objects, by navigating to Setup > Object Manager > User > Set History Tracking.

Salesforce Winter’26 – Same place to configure Field History Tracking in Object Manager

As fileds to track, you have there the option to choose

  • either users fields to follow with former and new values
Salesforce Winter’26 – Fields to track changes with old and new values
  • or other fiels whose changes are tracked but without values informations
Salesforce Winter’26 – Fields to track only the changes

For this test, I have updated a bunch of fields, with tracking on some of them :

As the extensions / tools are not yet compliant with v65.0 (Winter’26), lets see how you may circumvent it, and query / get these user records changes while waiting for our loved & usual extensions to be able to handle the new UserHistory object !

First create a new custom report type on UserHistory object.

  • Navigate to Setup > Report Types > Create Custom Report Type
  • Select UserHistory as primary object
  • Fill in a label, a name (automatically filled in based on label) and a description
  • Save it
Salesforce Winter’26 – Look for UserHistory object to track changes on User records
Salesforce Winter’26 – Custom Report Type creation on UserHistory

Keep the object alone, as it is the case when you normally query an History-typed object !

Remark : In an history-typed table, you get the information about which record it is related (Account Id for an AccountHistory object, for example), but you cannot navigate through the relation to this related record (e.g. you cannot access the Account’s DUNS number from it) to get information from the history object record. It is the same here for UserHistory table !

Salesforce Winter’26 – I am a poor lonesome cowboy

Then save the report !

Salesforce Winter’26 – Custom Report Type summary after creation

Finally, to test it, you will then go to your usual Salesforce application (or through the App Launcher > Reports), access the Reports tab, and create a new report from the custom report type, which you have just created.

Salesforce Winter’26 – New Custom Report Type, on UserHistory object, is available
Salesforce Winter’26 – Create new Report based on UserHistory-based Custom Report Type

Then, as you would do for any other reports, customize the fields to display, the ones to group by, and the filters to apply on your report ! Do not hesitate to adapt it a bit to match your requirements !

Salesforce Winter’26 – And there are your latest tracked changes on user records

It is now your turn to track changes on your org’s users ! Have fun !

To read more on the subject

SUMMER’25 – New User Interface for Agentforce Prompt Builder layout

Publié le par
Répondre

Have you recently witnessed some changes on Prompt Builder layout, since last Salesforce Summer’25 release upgrade ? Do you ask yourself how it will impact the way you write your prompts now with this new Agentforce Prompt Builder layout ?

If you had taken some modules on Agentforce, or if you are in your way throughout the « Agentblazer journey« , you have certainly already played / used former Prompt Builder.

Same thing if you have already taken / passed the Agentforce Specialist certification exam (previously known as AI Specialist) !

Agentblazer journey – Follow this journey to improve your skills on Agentforce

Before the latest changes, the screen was organized with :

  • the prompt, on the top part,
  • the preview part (resolution & response panes) on the bottom part,
  • and the template configuration pane, on the right side of the screen

Resources-related part was on top of the prompt section, and the input part (to test the prompt with record data) on top of the response section, in the middle of the page.

Summer’25 Salesforce – Prompt Builder UI changes – Former Prompt Builder UI
Screenshot from « Agentforce SDR Setup and Customization » Trailhead module
« https://trailhead.salesforce.com/it/content/learn/modules/agentforce-sdr-setup-and-customization/customize-agentforce-sdr »

Now, the view are side to side, with a dynamically collapsible / expandable approach, allowing to get a full page view of each of these parts.

Summer’25 Salesforce – Prompt Builder UI changes – New UI with all panes displayed

That is particularly useful when prompts – and answers (in this case, expand the « Generated Response pane » to get a whole page view on the response) – are long or text-formatted.

This way, you avoid scrolling down too much.

Summer’25 Salesforce – Prompt Builder UI changes – New UI with Prompt pane expanded

Each part could be collapsible with a click on the « – » button (in yellow in the screenshot), and could be also expandable with a click on the vertical ribbon or on the « + » button (in green, in the same screenshot).

Concerning the resources, they are still present on the page :

  • click on + Insert Resource, to display the possible resource types to add to your prompt
Summer’25 Salesforce – Prompt Builder UI changes – Insert Resources
Summer’25 Salesforce – Prompt Builder UI changes – Possible resources types to insert into your prompt

Same thing for the input parameters to test your prompt with. You need to click the Properties button to open the Template Settings pane, as shown below :

Summer’25 Salesforce – Prompt Builder UI changes – Open Template Settings button to open the pane

This pane allows you to visualize the required inputs to add to your prompt, to allow it to run, and then preview it, by entering any additional free text input resources.

Summer’25 Salesforce – Prompt Builder UI changes – Save and preview to test the prompt
Summer’25 Salesforce – Prompt Builder UI changes – Preview settings pane

To be honest, I was not a big fan of this new UI.. but I admit that I have played a bit with it, and became used to it. I still prefer the previous Input section, but I suppose I will get used to it too ! 😀

Have fun prompting !

To read more on the subject

SUMMER’25 – New login experience in Salesforce with email address

Publié le par
Répondre

If you have too many Salesforce usernames to remember, this new login experience will allow you to log in to your Salesforce instances by simply using your email address.

When using a domain (domainname.lightning.force.com), the email option is not proposed. You will see this option only when logging with generic login.salesforce.com.

Login experience with Email – Login page with new button to access this new login experience

The following article explains how you log in to Salesforce with your email address.

FIRST LOGIN WITH AN EMAIL ADDRESS

When it is the first time you try to log in with an email, the login page will ask you to enter an email address. Please fill in the Email address input field, with the email address mentioned on your Salesforce users.

Login experience with Email – First step is to select the email OR fill in the email to use (the first time)

Accordingly, on your first login with this email, you will be asked to verify it with a 6-digit code, which will naturally be sent to your email address, you are logging with !

Email with verification code
Page to enter 6-digit verification code

Please check your email spam folder if you do not receive this email.

LOGIN WITH AN EMAIL ADDRESS ALREADY USED ON THE LOGIN PAGE

If you have already used your email addresses to log in, this new Salesforce welcome login page will then propose you all the email addresses used so far.

You will be able to use other email addresses, and edit this list for better login management. In this case, note that you will be able to organize or remove recently used email addresses.

Login page with email address
Email addresses management in Salesforce Welcome login page

MANAGE YOUR ENVIRONMENT SWITCHER PAGE

If your email address is linked to multiple Salesforce accounts, you can see them all in the Environment Switcher. You will find there your Production usernames, and your Developer Editions usernames, which are linked to the specified email address.

Salesforce Environment Switcher – the list of production / dev edition linked to your email address

Now, from this page, you can change the name of your instance names, displayed in the instance tiles of your Environment Switcher, so that it will be more meaningful for you, and easier to keep your cool in this list.

To do so, click on the pencil icon of your instance tile, change its name and save.

Environment Switcher – click the pencil to rename the instance tile
Environment Switcher – rename and save the instance tile name

To log into your Salesforce instance, just click on the link in the header of the instance tile. The link is built this way : https://welcome.salesforce.com/environments#-51

Environment Switcher – click the tile name to log in to it

FINALIZE YOUR LOGIN

Then, once you have clicked on the link of the instance / username to log in with, Salesforce brings you on a welcome login page on which you would have to finalize your login process.

Login page – Once the instance has been chosen, you just need to type in your username password

Finally, you just have to fill in your password and click the Log In button, to access your selected instance. That is how you leverage new login experience with your email address !

To read more on the subject

Log In with Your Email Address : https://salesforce.vidyard.com/watch/nVj5vidvHYbwHHfMWPrEcU

Log In with Your Email Address Help Topic: https://help.salesforce.com/s/articleView?id=xcloud.log_in_with_email.htm&type=5

SALESFORCE #TIPS – Activate new SLDS 2 theme (Cosmos)

Publié le par
Répondre

You have probably seen that a new SLDS 2 theme was released a few months ago. Read the following article to know how to preview new SLDS 2 theme, and enable it, in your Salesforce instances !

BEFORE MIGRATING TO A NEW THEME

As you already know, this is the way a Salesforce record (a well-known account in this example) is displayed in Salesforce, with the current theme :

  • a Record detail page, with current theme
Current theme – Record detail page view
  • a Related lists page, with the same current theme
Current theme – Related list page view

PREVIEW THE NEW THEME FIRST

To preview or/and enable the new SLDS 2 theme, go to Setup > Themes and Branding. You will then ve able to see both :

  • The active theme in this instance is the classic (and efficient) Lightning Blue
  • The recent Salesforce Cosmos SLDS 2 theme, on the last line of the tab
Setup – Themes and Branding – Current configuration

It is always a best practice to preview a theme before activating it (as it is for all release update / new feature). It avoids bad surprises. To preview SLDS 2 new theme, select the Cosmos SLDS2 line, click on the down arrow button, at the end of the line, and click on Preview.

Setup – Themes and Branding – Preview new theme first, before activating it

You can now navigate throughout your Salesforce applications, to see how the components and pages render with the new theme. For information, you will get a banner, on the top of your page, to easily quit the theme preview mode (« End preview » link):

Top banner reminder, allowing you to quit the preview mode
New SLDS2 theme – Record detail page view with the new theme
New SLDS 2 theme – Related list page view with the new theme
New SLDS 2 theme – An example of a new record page layout, with the new theme

As always, the View option (from within the down arrow button, on the theme line) allows you to see the branding details / color palette of the theme

View Theme – Just for visualization (or modification for custom ones)

ENABLE A NEW THEME (SLDS 2 still in Beta, though)

If you want to customize a theme for your instance, please create a new one (« New Theme » for SLDS2 theme, « New SLDS 1 Theme » for a standard SLDS1 theme), and customize it. This way it will be easier to come back to the standard theme.

Setup – if you want to customize a theme, please create it first (SLDS 1 or SLDS 2)

A new theme will then be available in the Themes and Branding tab !

Then, once you have made up your mind about the theme to leverage (standard OOTB SLDS 2 Cosmos theme, or new customized one created as presented before), go back to previous screen, select the theme that you want to activate in the Themes and Branding tab, click on the down arrow button, and choose « Activate » to activate the chosen theme.

Setup – Themes and Branding – Activate a theme

Be aware that this theme feature is still in beta, and thus there coud be some side-effects, as reminded by Salesforce.

Information banner explaining the SLDS 2 is still in beta

If you activated the SLDS 2 theme and – due to some issues – you want to go back to former theme, go back to setting, select a standard SLDS 1 theme (like the famous « Lightning Blue » we have already mentioned) and activate this one. The theme will then get back to normal.

Have fun with this new theme !

To read more on the subject

TDX’25 – Free Salesforce Developer Edition with Agentforce

Publié le par
Répondre

One of big announcement of Salesforce TDX 2025 is the possibility to provision a developer edition with all Agentforce related features available in it. We will show how to provision it.

And great precision – compared to former Agentforce / Data Cloud playgrounds with which you may have played for your Trailhead modules so far – this Agentforce-fueled Dev Edition is available as long as your regularly use it (one login every 45 days !).

The QR Code to flash to get your own AI-fueled personal Dev Edition

Agentforce Dev Edition home page

For information, other news about Headless / Agentforce API have been shared during this session ; Agentforce is not only used by an human

New features related to Agentforce, centered on enhancing the interaction with the platform

This communication echoes some previous materials shared by Salesforce teams, like the two following ones, available in Youtube, on Salesforce Developers‘ account, published a couple of weeks, before TDX’25 event :

More to read in the coming weeks, for sure, to see all new use cases possibilities !

To read more on the subject

SUMMER’25 – Prepare your Salesforce Org for API v21-30 retirement

Publié le par
Répondre

You probably remember working on this Salesforce « API retirement » topic 2 years ago..! (see the post written for Summer’23 release update back then : https://forcewalk.com/salesforce-summer23-api-v21-30-retirement-summer25-integration-problem-with-microsoft-power-bi/)

Indeed, this topic was postponed, and is back again in your release update listing for upcoming Salesforce Winter’25 release. So how do we prepare for this API retirement ?

Accordingly, when this release update is live, external applications, which consumes these old Salesforce REST / SOAP / BULK API versions, will stop working, as these calls will fail (endpoint is not found).

Identify if your Salesforce instance is called through an old API version

Please navigate to Setup > Event Log File Browser to investigate. Then, once you have landed on the tool page, launch an analysis of your API Total Usage, on a daily basis, on a 1-month duration, here for example, from February 1st to February 28th.

This way, it provides a sufficiently broad window to ensure that all usages will be caught in this analysis, and that all calls to versions lower than v30.0 will be detected.

Event log file browser usage – Target API Total Usage on a daily basis

Once the time frame is selected, and you have chosen « API Total Usage » and a « Daily » interval, click Apply.

Event log file browser usage – Study every file on a day to day / file to file approach

For each day, download the file (click the arrow at the end of each line).

Event log file browser usage – download all files of the observed period & open them all in VS Code

Then, open each file, and look for API version below v30.0. In my case, I have handled this search with VS Code application. To find all the v21.0 to v30.0 usages occurrences, I have used the following regular expression : « (30|([012]?[0-9]))[.][0] »

Use VS Code’s Find feature with « Use Regular Expression » option (Ctrl+F then Alt+R) – Make sure to use proper double quotes in the regular expression !
Visualization of a file downloaded for all API Usages of a specific day (VS Code used for this part)

Make project teams adapt their calls to Salesforce

Besides, once you have found some occurrences using soon-to-be deprecated API versions, you have all that you need to identify where they come from :

  • « API_RESOURCE » : the URL resource that is involved in this API usage (« query », « update », « DescribeSObjects », « v29.0/query », « /v29.0/sobjects », « /v27.0/chatter/users/me »...)
  • « USER_ID » : the user who has called this resource

After you have grouped all these usages (by application type or by user), contact the different project teams to ask them to update their connector or code.

To read more on the subject

Salesforce Platform API Versions 21.0 through 30.0 Retirement : https://help.salesforce.com/s/articleView?id=000389618&type=1


See the post written for Summer’23 release update back then : https://forcewalk.com/salesforce-summer23-api-v21-30-retirement-summer25-integration-problem-with-microsoft-power-bi/

Salesforce Summer’23 – API v21-30 retirement (Summer’25!) – Integration problem with Microsoft Power BI