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.
1 answer
0/9000
1 answer
  1. Today, 11:38 AM

    If your default home page is a dashboard and you're unable to add components, check the dashboard settings or permissions. Some platforms may restrict adding components based on user roles. If you still can't find the option, consider consulting the help documentation or reaching out to support for assistance.

0/9000
0/9000

Hello everyone,     I have added on lwc component on partner site and in which I have displayed the account records with hyperlink, upon clicking on it will open that record on separate tab.  It is working fine on Dev and UAT org but it is giving me the csp src font error . Anyone knows regarding this. I have added screenshot below. Please refer that one.  

3 answers
  1. Today, 11:32 AM

    Hi @Tushar Patil

    1.  Go to CSP Trusted Sites in Setup
    2.  Add the font/CDN domain causing the error
    3.  Set CSP Context to “Lightning Components”
    4.  Clear cache and re-publish community
0/9000
3 answers
0/9000

Hi!  I'm trying to merge Person Accounts, but the error message appears "We couldn't merge these accounts. We couldn't merge the Contact Profiles. Ask your Salesforce admin for help.

 You can't undo a merge." As in the attached print I can't perform the process. Can you help me?  I'm a system administrator, so my profile has general access; Person Accounts have the same RecordType and Owner. 

 

 

#Person Accounts  #Salesforce Developer

3 answers
  1. Today, 10:57 AM

    Hi @Aparna Lanjekar

      

    Possible Causes for Person Account Merge Error:

    1.  Contact is linked to a User / Customer Portal / Community User
    2.  Validation Rule or Duplicate Rule is blocking the merge
    3.  Apex Trigger or Required Field is causing failure
    4.  Person Account is part of an active Duplicate Matching job
    5.  Sharing settings or manual sharing preventing access
    6.  Record is being edited or locked by another process
0/9000

Hi Guys,  I have a Query, can you tell me how many times the trigger will execute an Upsert Event?

 

Actually, in triggers, we have insert, update, delete, and undelete events are there however,  there is no upsert event in triggers. How can I understand the above question?    Can you please explain me clearly?

5 answers
  1. Today, 10:02 AM

    Hi @Vadde Amaresh

     

     

    In Salesforce, an upsert executes the trigger

    only once per record, either as an insert or updatenot both. The trigger runs in the context that applies to the record.

0/9000

I have the new Quickchoice component, version 2.34, installed and I need to set the existing value for a picklist field called Member Status, however, for the life of me, I can't figure out how to set it.  In the "Value" input, I have tried "Existing" and I have tried to pull the value form the single record collection I have, but the Member Status Picklist field is not showing up.  So I am super confused. 

 

#Unofficial SF #Flow

 

 

 

Can't set existing picklist value in Quickchoice?

 

 

1 answer
  1. Today, 10:50 AM

    Hi @Heath Parks this is tricky, unfortunately QuickChoice does not automatically set a picklist value from record field, solution I found is to create a text variable in a Flow and assign it to the picklist value you need (in your case Member_Status__c) then set varpdefaultpicklist as Default value in the QuickChoice

0/9000

Hi everyone,

I'm facing a DUPLICATE_VALUE

error when inserting a new Opportunity in my test class. 

After investigation, I discovered that the issue comes from my @TestSetup method. However, there are

no unique fields defined on the Opportunity object, and even if there were, the inserted data isn’t identical.

To reproduce the issue, I wrote the following test class, and I still get the error. However, if I comment out the insert statement in @TestSetup, everything works fine.

Has anyone encountered this behavior before? Why would Salesforce consider the record a duplicate, even when the data is different?

My only workaround was to delete all Opportunity records in my test method before recreating them, but I’d love to understand the root cause of this issue.

public class TestSetupInsert {

public static Opportunity createHypothequeOpportunity(Id accountId){

Opportunity opp = new Opportunity(

StageName='En attente',

CloseDate=Date.newInstance(2024, 12, 31),

RecordTypeId='0127Q0000005LXLQA2',

OwnerId='005TG000000Zlk2YAC',

AccountId=accountId,

Name='Test'

);

insert opp;

return opp;

}

}

 

@IsTest

public class TestSetupInsertTest {

@TestSetup

public static void setup(){

Account acc = AccountFactory.createPersonAccount();

// Hypothèque

Opportunity oppHypotheque = OpportunityFactory.createHypothequeOpportunity(acc.Id);

OpportunityLineItem oppProdHypotheque = OpportunityFactory.createOpportunityProductHypotheque(oppHypotheque.Id);

}

@IsTest

public static void createHypothequeOpportunityTest() {

Account acc = [SELECT Id FROM Account LIMIT 1];

Test.startTest();

Opportunity opp = TestSetupInsert.createHypothequeOpportunity(acc.Id);

Test.stopTest();

Opportunity newOpp = [SELECT Id, Name, RecordTypeId FROM Opportunity LIMIT 1];

System.assertEquals('Test', newOpp.Name);

}

}

Thanks in advance for any insights! 🚀 

 

#Salesforce Developer

4 answers
  1. Today, 10:39 AM

    @Issam Tebbikh

     

    Hi,  

    Try changing the

    Name field in your createHypothequeOpportunity

    method to 

    Name = 'Test - ' + System.currentTimeMillis() 

    and run the test once again.

    Reason:

     

    Salesforce sometimes treats records with exactly the same unique combination of fields as duplicates, even if there are no explicit unique fields defined. By appending System.currentTimeMillis(), you make the Name unique every time the method runs, avoiding duplicate value errors during insert. This helps ensure each test record is distinct and prevents Salesforce from blocking the insert due to perceived duplication."

0/9000