#Trailblazer Community Questions3.334 discutindo

Ran into packaging gotcha worth flagging to this group: if Permission Set includes standard object permissions or user permissions, 2nd-generation package builds clean — no error, no warning at build time, none at install time either. But those permission entries get silently stripped during install. Permission set deploys "successfully" and ends up empty of the very perms you configured.

No compile error. No validation warning. Just quiet divergence between metadata you packaged and metadata that lands in subscriber org — typically surfaces only when integration user hits FLS/object-access failure in production, and someone burns hours tracing it back to packaging, not code.

For anyone architecting managed/2GP packages with permission sets: worth auditing what's actually landing post-install, not just trusting deploy success.

Idea open on Salesforce Ideas asking for standard object perms + user perms to be packageable. Even short of full support, ask includes smaller ask that'd solve most of the pain: raise build-time error when permission set contains unsupported permission types, instead of silent drop.

Upvotes appreciated if you've hit this too: 

Curious if others in this group have workarounds beyond post-install Apex/Flow to re-grant these perms.

Hello everyone, 

we have a lot of invalid accounts in our system. 

Naturally, our sales team isn't exactly thrilled that when they use the global search to look for a customer, they also get all the invalid accounts suggested to them. 

Nevertheless, these accounts should still be visible in the global search for system administrators and internal staff responsible for data maintenance and history. Is there a (simple) way to do this? Deleting them is not an option. Thank you in advance. 

Badge: dataloader+data wizard  

module: Use

to Export Data  

I got 715 successes instead of 11. 

Did anyone come across same problem? 

Hello. We have Cases created from emails, and when we export a Case report, the Description field only contains the body of the first email that created the Case. Later customer replies are not included, even though they can be viewed as related email records within the Case.

Is there a standard way to include the latest email body or all EmailMessage records related to each Case Number in a report? We need the updated conversation because delivery date changes, rescheduling requests, and urgency information may appear after the initial email. The user can manually view these email records but does not have administrator permissions.

I'm a Salesforce consultant. Every project I've worked on started the same way: a Figma or grey-box wireframe that the client signs off, then a build that surprises them, because a picture of a Lightning page is not a Lightning page. Hover cards, path chevrons, related lists, the way a quick action opens: none of it is in the mock-up, and the review meeting turns into "is this what Salesforce looks like?" instead of "is this the requirement?". 

What I've been doing instead is building the page itself in the real Lightning Design System from the user story, in both the SLDS 1 and SLDS 2 looks, then clicking through it with the client and reading the acceptance criteria back off the page. It has changed our review meetings, but I'd like to know what others in this group use: 

Do you prototype in the SLDS Figma kit, or straight in App Builder in a sandbox? 

How do you show interaction (quick actions, screen flows, popups) without building it for real? 

How do you handle the SLDS 2 transition when the client's org still shows the classic look? 

Full disclosure: I built the tool I use for this (