Skip to main content

Hi all! I think I can't get around this but I'm wondering if anyone has any ideas. I have two lines of business (line a and line b) and line b wants to see some information from line a. Previously this has not been needed or possible. 

 

I have managed (using a looking field on the opportunity and a sharing rule) to make that happen. The problem is that if line b runs an account report (for example) they get line a info and we don't want that to happen. If I remove the sharing rule that makes this whole thing work - what I created falls apart. 

 

I'm thinking the only way is do something thing that would require a LOT of work and probably involve bringing in a developer - one or more of the following 

- custom dl account reference object 

- screen flow search 

- custom LWC 

anyone have any other thoughts/ideas? 

Thank you in advance as always for any help!  :) 

 

#Salesforce Admin  #Salesforce  #Sales Cloud  #Automation

3 réponses
  1. 23 oct., 11:20

    Your instinct about the screen flow is right, and it doesn't have to need a developer. 

     

    The core issue is that sharing is all-or-nothing at the record level. Once line B can see a line A Account, it shows up in every report, list view and search. You can't share a record for one screen but hide it in reports. 

     

    So flip the approach: 

     

    1. Remove the sharing rule, so line A Accounts stay private to line A. 

    2. Build the screen flow you mentioned, launched from a button on the Opportunity, and set it to run in "System Context Without Sharing". The flow can read the line A record through your lookup and display only the specific fields line B needs. 

     

    3. Show it on the Opportunity page as a screen flow component or quick action, so there are no reports and no broad visibility. 

     

    Watch out: system context also bypasses field-level security. Be deliberate about which fields the flow displays, and document it for your security or audit team (relevant at a firm like yours). 

     

    If line B also needs to report on that information, add a small custom object or a few fields on the Opportunity, filled by a record-triggered flow with a copy of just the fields they need. That gives line B something reportable without opening up the Account.

0/9000