Skip to main content The last day to register for a Salesforce or Tableau exam is June 30th. Learn more about the new Salesforce certification experience coming July 21st.

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.

Hello! My company is changing names (so new URL, logo, brand, etc.). Does anyone have experience with something similar with their Pardot/Account Engagement instance? We know we will need to add a new domain tracker (and thus change our landing page URLs), create new templates, etc. But we would love to hear about gotchas and successes from someone who has gone through something similar. 

1 answer
  1. Today, 4:16 PM

    Hi, 

     

    I went through this exact process a couple of years ago when my company rebranded. It’s a big project, but totally manageable if you map it out carefully. Here are a few lessons we learned (and some surprises we ran into): 

     

    First, yes, setting up the new tracker domain is step one. We had to work closely with IT and DNS to get the CNAME set up properly before switching it in Pardot (now Account Engagement). 

     

    What surprised us:

    • Old URLs were everywhere, landing pages, email templates, forms, and images all needed manual updates. We actually missed a few nurture emails and had to fix them fast after people clicked broken links.
    • We forgot about SSL for the new tracker domain at first, which delayed us. Make sure you set that up early.
    • Any custom redirects in Pardot need to be recreated for the new domain, or you’ll get 404 errors.
    • Engagement Studio programs often have links or assets tied to the old domain, easy to overlook.

     

    What helped us

    • We ran the old and new domains side by side for a bit. This gave us time to update things gradually without breaking live links.
    • Doing a full content audit before starting saved us a lot of headaches.
    • We kept the sales team in the loop early since they often share marketing links.

     

    Last thing: if you use dynamic content or personalization, double-check for old logos or brand references. 

0/9000

How do I fix this error in the Agentforce champion playground. I've double checked the steps and I haven't missed any steps or inputted anything incorrectly. The error says:  

"Step not yet complete in Data Cloud and Einstein AI It looks like the Reservation 1 Flow element does not have the correct setting for the one filter."  

 

#Trailhead  #Trailhead Challenges  #Salesforce Developer

0/9000

Hi there, 

 

We’ve suddenly run into an issue with formal and informal greetings in Salesforce NPSP. 

 

Previously, the greetings were behaving correctly. For example, if a contact was marked as deceased (e.g. John [Deceased] and Margaret Smith), the formal greeting would correctly show Margaret Smith, and the informal greeting would show Margaret

only. 

 

However, last Friday we noticed that deceased contacts were being included again in both the formal and informal greetings. We initially assumed it might have been changed accidentally by a team member, so we corrected it manually. 

 

But this morning, we found the same record had reverted — the deceased spouse was included again in the greetings! 

 

Has anyone else experienced this issue recently? Any advice or suggestions would be appreciated. 

 

Thank you!

4 answers
  1. Today, 4:10 PM

    What @Dodi Friedenberg

    said. While this description is not a match for the exact criteria in that Known Issue, it seems clear that there was an issue introduced in Summer '25 related to Naming.  

     

    The good news (hopefully) is that there is a fix in process, and it appears they are targeting it for a patch release, so folks won't have to wait until Winter '26 (next release).  

     

    But I'm not entirely convinced this issue will be resolved in the code they're working on.

    @Noriko Murakami Are you updating the "Exclude from..." checkbox fields on Contact to make sure the Contact is excluded? Is that the value that is being unchecked? Or are you only toggling the Deceased checkbox? What values are you seeing in "Naming Exclusion" field on Contact, and is that field changing?

0/9000
1 answer
0/9000

 Hi, is it possible to assign a different profile to a user after they’ve been created in the system, based on certain conditions in their related Contact record?  

 

#Salesforce Developer  #Flow

2 answers
  1. Today, 4:03 PM

    Hi @Nuriye Kahraman

     

     

    You cannot change profile of a user directly from flow. 

    but you can change profile of a user from Apex. you can add your custom logic in apex file for assigning profile to a user. 

     

    few things to consider: user must be active and not an admin user

0/9000
1 answer
  1. Today, 3:54 PM

    Hi @Genna Wilson

     

    o resolve the issue with the missing ‘Technical Skills’ field section on the Technical Position

    page in the Trailhead playground, please follow these steps:  

     

    1. Go to the Technical Position record page (open any existing record).
    2. Click the gear icon at the top right and choose "Edit Page" to open the Lightning App Builder.
    3. In the Lightning App Builder, look for the ‘Technical Skills’ section in the components or fields pane.
    4. If it's not already added, drag and drop the section onto the page layout where appropriate.
    5. Click "Save" and then "Activate" the page if prompted.
    6. Go back to the record page and refresh the page. The ‘Technical Skills’ field section should now be visible.

     Thanks

0/9000

I had no option but changing my email address,  as my company prefers I study with my private google account. I merged both accounts but since then, I cannot open my developer account. And I do not received the emails to reset my password anymore, so I am stuck and cannot progress with my Coursera Course. 

 

#Trailhead Challenges

1 answer
0/9000

my log4j2.xml 

 Mule application is deployed successfully, and API is responding in Postman. but no logs in Postgres. 

Errors in the console:

  • ERROR Error processing element ConnectionSource ([JDBC: null]): CLASS_NOT_FOUND
  •  ERROR Null object returned for JDBC in Appenders.
  • ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.db.jdbc.JdbcAppender for element JDBC org.apache.logging.log4j.core.config.ConfigurationException: Arguments given for element JDBC are invalid: field 'connectionSource' has invalid value 'null'
  • ERROR Unable to locate appender "DatabaseAppender" for logger config "root"

<Appenders> 

    <JDBC name="DatabaseAppender" tableName="api_logs"> 

      <ConnectionSource class="org.apache.logging.log4j.core.appender.db.jdbc.DriverManagerConnectionSource"> 

        <Property name="driverClassName">org.postgresql.Driver</Property> 

        <Property name="connectionString">jdbc:postgresql://localhost:5432/postgres</Property> 

        <Property name="userName">postgres</Property> 

        <Property name="password">pass</Property> 

      </ConnectionSource> 

 

      <Column name="log_timestamp" isEventTimestamp="true"/> 

      <Column name="log_level" pattern="%level"/> 

      <Column name="logger" pattern="%logger"/> 

      <Column name="message" pattern="%message"/> 

    </JDBC> 

 

    <Console name="Console" target="SYSTEM_OUT"> 

      <PatternLayout pattern="%d [%t] %-5level %logger{36} - %msg%n"/> 

    </Console> 

  </Appenders> 

 

  <Loggers> 

    <Root level="info">

      <AppenderRef ref="Console"/>

      <AppenderRef ref="DatabaseAppender"/> 

    </Root> 

 

@* Salesforce Developers *

 

 

 

#Salesforce Developer

2 answers
  1. Today, 3:50 PM

     Hi Praveen, beside the JDBC error, keep in mind the well known performance degradation caused by high volume of logging in Mule 4.  

    Performance degradation caused by high volume of logging in Mule 4

      

     

    For high performance application is better to use a different pattern, such as 

    - in the application flow, send log to a Messaging system (Kafka, AMQ, JMS, ...) 

    - then read from the queues and forward logs to the DB, or external log collector, as you like 

     

     

0/9000
10 answers
0/9000

Just a quick question for the "Save and Debug" section of the "Build Record-Triggered Flows Guide." 

 

The debug did work just fine for me, in that it shows the dark blue line. But as a for future reference, I was wondering if I was supposed to delete all the information in all the other fields other than "Closed Won" and "250000" before debugging? The instructions weren't 100% clear on that, and I wasnt able to find this specific question that may have been answered elsewhere.  

 

So in the future, when I run the Debug, do I clear out all the other fields that aren't part of the criteria for creating a new record? Or is all that other information also necessary?  

 

#Trailhead Challenges  #Trailhead

0/9000