Feed

 If a single Flow contains multiple Update

elements that each modify the same object (e.g., Contact), will each of these DML operations trigger the associated Apex trigger separately?  

Thanks in advance for your help!  

#Trailhead Challenges

Hello,

I’ve been facing a strange issue on Salesforce. Whenever I post comments, they appear perfectly fine on my side — I can see them clearly when I’m logged in. However, when I open Salesforce in incognito mode or ask a friend to check from their account, my comments are not visible to them.

I’m not sure if it’s a permission issue, a visibility setting, or something else going wrong. Has anyone else experienced this? Any help or insight would be greatly appreciated!

Thanks. 

When we work with unstructured Data in Data Cloud. We use to create retriever and break the Data into chunks. Can we Customized that Chunking Process? What happens internally, when we use the retriever to break the data??  

Hi all, I have a flow routing the incoming messaging requests to a queue for messaging for web implementation. But I see the routing is failing for some messaging requests and flow is failing at Route Work action with this error 'The queue must be an Omni-Channel queue This Route Work invocable action did not create a valid Pending Service Routing.' Now my question is that since it works just fine for most of the messaging requests then how can there be an issue with the queue. I am not able to figure out the issue here. I have also checked the data of incoming messaging requests for both failing and passing cases and I can't see any relevant issue in the data as well. 

Has anyone faced this before? Is there something I should look at which I may be missing here? 

Let me know please, thanks!! 

Hi folks, 

I've finally decided it’s time to move our tiny-but-growing org to package-based development. It’s 2025 already and although I know plenty of orgs still living in the Happy Soup, I still feel late to the party.

The plan is not a big-bang refactor. I’ve been warned off that enough times that it's burned into my brain. I want to start small, but I feel like starting small still needs a clear map, otherwise I'll end up shuffling fields and classes between packages every other week. 

After disappearing for a couple of days, I grouped every piece of metadata I could find, and sketched the diagram that's attached. It's very first-draft, sketched only by me without anyone to provide their thoughts yet, so poke as many holes in it as you like. 

What you'll see in the picture

• Unpackaged layer: stuff that really depends on everything that can't/shouldn't be packaged (layouts, permission sets + groups, lightning record pages, etc.)
• Business layer: four core packages (Sales, Service, Finance, Marketing) plus where a new package, such as a billing-system integration (not created yet), would go.
• Extension layer: add-ons like sbqq-ext, blng-ext, millio-ext, and a sf-test-data-generation package that spits out test/demo data. For instance, sbqq-ext would hold SBQQ.QuoteModel, QuoteCalculatorQueueable, etc. Also, some custom fields...?
• Structural layer: one big common package. It holds the generic SObjectBuilder, base triggers, and anything that should be usable only knowing our objects, not their fields.
• Managed layer: the third-party managed packages we depend on (sbqq, sbaa, blng, millio, pi, cldseq.)
• Utilities layer: FFLib, Trigger Actions, force-di, Nebula Logger, Apex Libra, etc.

A few things I’m wrestling with

1. Does it even make any sense? Is it on the right path, over engineering, both?  
   I'm coming up with these layers and packages with no real prior experience. Do they make sense? What metadata components would you say go or don't go into them? 
    

2. Fields and Trigger Handlers:  
   I envision that we would put fields like SBQQ__Quote__c.TextField__c in sbqq-ext. But it's never so clear cut like that. What if we wanted a field on quote (just an example) looking up to blng__LegalEntity__c? I guess, since that might relate to a requirement for finance dept., that we'd put that in the Finance Core. Is that the correct thinking? Also, sf-test-data-generation is a pretty standalone package, and introduces custom objects and triggers for it. While all our triggers are in Common, does it make sense to have a custom object definition, triggers, etc. (specific to sf-test-data-generation) in that package? 
    

3. Also, where should the sf-test-data-generation package live?  
   It isn't really "business logic", but it also isn't as low-level as
   utilities. I dropped it in the extension layer for now. Does that placement make sense? 
    

4. Business vs. Extension: are these really two separate layers?  
   Should there even be something like an "extension layer"? The names were, again, just invented on the spot. In practice they both hold code that depend on managed packages. I know that for sbqq-ext, we would have CPQ API classes in there, and maybe some other relevant queueables. But would we also store some custom fields there? Similar question to #2.

I've nearly a decade of building on Salesforce on my belt, but this experience has made me realize that although I can ship features fast, I don't really know how to design an application, one that can grow without turning to spaghetti. This packaging exercise is forcing me to think quite a bit deeper, and so I could really use a few extra heads. So if you've walked this road, even part of it, I'd love any feedback, nit-picks, or "you're totally off here" comments. 

Thanks a ton in advance! 

Hi, 

       Non-admin users receive insufficient privileges Error for the Org Check app, even after assigning the "Org Check User" permission set. Please let me know if I am missing anything. 

Thank you

Every now and then, we have users who create more than one account in a Custom Community Portal under a different user name.  While we can deactivate one of their accounts as a user, we cannot delete the account/contact because the "account is associated with a portal user." Is there any way around this?

Hi All, 

I’m new to the Marketing Cloud Meta WhatsApp feature, so I’m exploring what could be the best approach to achieve this. 

I’m creating a WhatsApp template where the CTA action will include a fully dynamic URL. From what I see, the dynamic option supports parameters, but the base URL needs to remain the same. In my case, there are around 10–15 different base URLs. 

If I need to create separate WhatsApp templates for each base URL, or is there any way to handle this through mapping in a Data Extension or using a CloudPage to manage it with a single template?

Thanks