Skip to main content A new Salesforce certification experience is coming July 21st. Discover how exams will be delivered in Pearson VUE, what it means for you, and ways to prepare. Learn more.

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.
When sending emails with attachments from with an account record, is it possilbe to have the attachment captured and stored in the  'Notes & Attachments' related box? 

 

Saving email attachments in the related 'Notes & Attachments' box.
3 answers
0/9000

Hey all! I’m a Salesforce Admin at a SaaS company, and we’re trying to make a decision on how to handle returning customers who were previously churned. It doesn’t happen super often, but we’ve had a few customers come back recently and it’s raising some questions. 

 

The main issue, is we integrate with other solutions (Intacct/Adaptive Planning) for financial and forecasting. A new Intacct ID is required when they return, which makes it cleaner

to create a brand new Account in Salesforce. On the other hand, I don’t love duplicating Accounts because we lose historical context in the CRM, and it can get messy for our Sales, CS, and Support teams. 

 

I’m wondering how others handle this — reopen or create new? 

 

Here’s the options we're considering:

Option 1: Reopen the old Account

  • Pros: Keeps CRM clean, retains full history, no confusion in reporting
  • Cons: Can cause confusion with financial/forecast planning integrations

Option 2: Create a new Account

  • Pros: Clean slate for integrations, financial and planning teams prefer this
  • Cons: Duplication in CRM, harder to trace lifecycle, need to relink Contacts/Cases/etc.

Possible Hybrid Approach:

  • New Account gets created
  • We link it back to the original via a custom lookup
  • Copy data onto the new account with apex/flows to ensure data cleanliness

Curious to hear how others handle this in integrated orgs. If you’ve dealt with this before, what worked for you? Any suggestions or best practices to share with this use case? Thanks in advance! #Salesforce Admin #Sales Cloud #Data Management

3 answers
  1. Today, 9:35 PM

    @Kaleigh Garcia From a data perspective, it's always best to avoid duplication — it rarely leads to anything beneficial. If I were in your position, I’d start by identifying the core business needs and requirements first, rather than jumping into the technical side. Next, I’d analyze the integration touchpoints to understand what’s triggering what. In many cases, existing accounts can be configured to meet the same objectives without creating duplicate records 

0/9000
3 answers
0/9000

Greetings Everyone, request to please assist as I am not able to create Agents on the Agentforce Developer Org, I am getting the following error, "Error creating agent : java.lang.IllegalArgumentException:User doesn't have access to use agent More Details: ERRORS : User doesn't have access to use agent , User doesn't have access to use agent WARNINGS" I am able to do so in Agentforce Playground, I have identified that the "Agentforce Service Agent User" and "Service Agent Permissions" permission sets are missing along with "Agentforce Service Agent User" Permission Set License Assignments for the user which I have created with "Einstein Agent User" profile in Agentforce Developer Org, please assist, on how we may fix it, thanks

1 answer
0/9000
1 answer
0/9000

Create a Partner Portal, Enable Partner Account and Users, and Add Members 

の以下ハンズオンを実施しています。 

この時「All Sites」のメニューが表示されないのですが、どうしたら良いでしょうか? 

Now that you’ve enabled digital experiences and increased the number of partner user roles, let’s set up a bare-bones partner portal. You should have been redirected to the All Sites page in Setup, but if not, enter Digital Experiences in Quick Find, and select

All Sites

 

#Trailhead Challenges

1 answer
0/9000
  •  

    Unified Link 1

    • The field "SourceRecordId__c" for the object "UnifiedssotIndividualCcid__dlm" doesn't exist.
    • The element has an invalid reference to "UnifiedssotIndividualCcid__dlm.SourceRecordId__c".
  •  

    Unified Link 2

    • The field "UnifiedRecordId__c" for the object "UnifiedssotIndividualCcid__dlm" doesn't exist.
    • The field "ssot__DataSourceObjectId__c" for the object "UnifiedssotIndividualCcid__dlm" doesn't exist.
    • The element has an invalid reference to "UnifiedssotIndividualCcid__dlm.UnifiedRecordId__c".
    • The element has an invalid reference to "Unified_Link_1.UnifiedRecordId__c".
    • The element has an invalid reference to "UnifiedssotIndividualCcid__dlm.ssot__DataSourceObjectId__c".
  •  

    Reservation 1

    • The element has an invalid reference to "Unified_Link_2.SourceRecordId__c".

 

 

#Trailhead Challenges

1 answer
0/9000
1 answer
0/9000
1 answer
0/9000