#Lightning Web Components6 discutindo

☁️ Salesforce Developers — Ready for Your Next Adventure? 🚀 

Innovate! Inc. is looking for a Mid-Level Salesforce Developer to join our team and help build scalable, user-focused Salesforce solutions. 

If you enjoy turning business requirements into great Salesforce experiences and have hands-on experience with Experience Cloud, Apex, LWC, Flow, and integrations, this could be a great next step! 💻✨ 

🔹 What we’re looking for:

☁️ 3+ years of hands-on Salesforce development experience 

🌐 Hands-on Experience Cloud development, including authenticated external-user experiences 

💻 Experience with Apex, Lightning Web Components, Flow & SOQL

🔗 Experience developing or supporting REST/SOAP integrations

🛡️ Understanding of Salesforce security, sharing, profiles, permission sets & external-user access 

🧪 Experience with code reviews, testing, troubleshooting & production support 

🚀 Familiarity with Git, Salesforce CLI/SFDX, deployments & CI/CD processes 

🤝 Ability to collaborate with business analysts and technical teams to build scalable solutions

➕ Experience with Service Cloud and MuleSoft is a plus!

🏅 Preferred certifications include Experience Cloud Consultant, Platform App Builder, Platform Developer I, and JavaScript Developer I. 

🏠 Remote within the U.S. 

💰 Salary Range: $100,000–$120,000 

🇺🇸 U.S. Citizenship required

 🔐 Must be able to obtain a Public Trust clearance

📋 Position is contingent upon contract award. 

Interested? Take a look! 👇 

👉 Learn more and apply:

https://innovateteam.my.salesforce-sites.com/InnovatePublicJobBoard/PublicJobPosting?id=a1KVJ00001nrZKf2AM

And if someone in your Trailblazer network comes to mind, please tag or share! 🙌☁️ 

#Jobs #Salesforce Developer #Experience Cloud #MuleSoft #Lightning Web Components #Remote Opportunities

We use the activities timeline on both Financial account pages and Account pages (Person, Household, Institution). On the financial account page, our activity timeline has one of our custom Task record types "Compliance Task" as an option to submit directly there. We do not have it on any other activity page on any other lightning page. I am trying to figure out why it is only showing there? I would like to have it be available option on all pages.  

#Financial Services Cloud  #Tasks  #Lightning Web Components

Do you use managed packages built with Lightning Web Components? Your Salesforce users might be losing 30+ seconds every day on their initial record load due to a Salesforce known issue that needs to be better prioritized. 

Have you noticed how on some Lightning record pages, the initial load takes 30+ seconds and seems totally unexplainable? Then after that first load, it's fine for the rest of the day. 

Here's what makes this worse than it looks: it's not a one-time delay. Every individual user hits their own cold start, so if you have 50 users opening an affected record type each morning, that's 50 separate 30-60 second delays, every single day. The productivity cost scales directly with your user count. 

We spent weeks investigating this on our managed package pages with the managed package vendor before Salesforce support confirmed it's a platform-level known issue affecting Lightning pages with shared component subtrees, not something specific to any one vendor's code: 

Known Issue: Flexipage performance degradation on DynamicComponent

 (Reference ID: W-23284931) 

This known issue feels significantly underreported for how big the impact is. If you've written it off as your imagination, blamed it on a slow server day, assumed it'll just go away, or your users have just been complaining without ever filing a ticket, this is likely why. 

If you manage Lightning pages with complex or shared component structures and have noticed this pattern, please report the known issue above against your own org and ask your AM for a timeline of when the issue will be fixed. At a minimum, it just takes clicking a checkbox on the known issue. I am hoping more visibility on the known issue means more pressure on Salesforce to prioritize a fix. 

#Lightning Performance  #Lightning Web Components  #Installed Packages  #Salesforce Admin  #Salesforce

I use the Lightning Component "Tab" on a lightning page. Is there a way to get the URL to one of the component's tabs? Hovering over a tab just shows "javascript:void(0)".

For example, I want to give a user a direct link to the "Decisions" tab. But I can't because I don't know the URL to that tab.

Thanks,

Marc

#Lightning Component  #Lightning Web Components

Preventing Recursive Lightning Message Service Calls in Screen Flow LWCs Using a Source Flag 

When working with Lightning Message Service (LMS) inside Screen Flow embedded LWCs, communication between components becomes extremely powerful — but it can also introduce unexpected recursive behaviour.

Recently, I encountered an interesting real-world scenario where two LWCs on a Screen Flow were unintentionally triggering each other repeatedly, causing incorrect value population even though the logic looked perfectly fine.

This blog walks through:

•  The Scenario 
•  The Problem 
•  Debugging Process 
•  Root Cause 
•  The Solution (Using Source Flag) 
•  Best Practices 
•  Final Takeaways 

Scenario

I had a Screen Flow containing two Lightning Web Components:

• LWC A — Publishes some values 
• LWC B — Publishes some values 
•  Both components subscribe to the same Lightning Message Channel

So essentially:

•  LWC A publishes → LWC B receives 
•  LWC B publishes → LWC A receives 

This setup is valid and expected — and initially, everything worked correctly.

However, as the use case evolved, values started getting populated incorrectly

. 

Even though:

•  Logic was correct 
•  Variables were correct 
•  Message structure was correct 

The values were getting overwritten incorrectly.

Example Behavior:

1.  LWC A publishes value 
2.  LWC B receives and updates 
3.  LWC B publishes updated value 
4.  LWC A receives again 
5.  LWC A publishes again 
6.  Loop continues... 

This created a recursive publish-subscribe loop

. 

To identify the issue:

•  Added console logs 
•  Checked publish events 
•  Checked subscription callbacks 

While debugging, I noticed:

• Publish method firing multiple times
• Subscription handler triggering repeatedly
• Unexpected value overwrites

This clearly indicated recursive message passing

. 

The root cause was:

Since both components:

•  Subscribe 
•  Update values 
•  Publish again 

It resulted in infinite cross-communication.

This is a common pitfall when using Lightning Message Service with multiple publishers

. 

The Solution — Using a Source Flag

To stop recursion, I introduced a Source Flag inside the message payload.

The idea:

•  Each LWC sends its name as source
•  When receiving a message: 
  •  If message source == current LWC 
  •  Ignore the message 

This prevents recursive triggering.

Example Message Payload

{
    value: selectedValue,
    source: 'LWC_A'
}

Implementation Example

Publisher

publishMessage() {
    const message = {
        value: this.selectedValue,
        source: 'LWC_A'
    };
    publish(this.messageContext, SAMPLEMC, message);
}

Subscriber

subscribeMessage() {
    this.subscription = subscribe(
        this.messageContext,
        SAMPLEMC,
        (message) => {
            if(message.source === 'LWC_A') {
                return;
            }
            this.selectedValue = message.value;
        }
    );
}

1.  LWC A publishes (source = LWC A) 
2.  LWC B receives 
3.  LWC B updates UI 
4.  LWC B publishes (source = LWC B) 
5.  LWC A receives 
6.  LWC A updates UI 
7.  No recursion 

#Lightning Web Components  #Lightning Message Channel  #Salesforce Developer  #Issues