Skip to main content

#SF Developer3 debatiendo

Agents have FLS for most fields on opportunity and we have something called SA1 records. Those are the records owned by 'System Admin 1' user. Agents can access those records from a related list. But we wanna restrict them to search for Opportunities with just email or phone. They should not be able to find say opportunities in a particular state or address from global search.

#Salesforce Developer #Salesforce Admin #Systems Administrator #Administrator #Advanced-Administrator #SF Developer #Platform Developer #SF Developers #Application Architecture #Ladies Be Architect
2 respuestas
  1. Hoy, 1:38

    Hi @ATU PANDU Salesforce Global Search doesn't support restricting searches to only Email and Phone fields for specific users.

    A few options to consider:

    1. FLS: Remove access to State and Address fields if agents don't need them.
    2. Search Manager: Check whether unwanted fields can be excluded from search indexing.
    3. Search Layouts: These control which fields appear in results, not which fields can be searched.
    4. Custom LWC with Apex: Build a search component that allows agents to search Opportunities using only Email or Phone.

    Since agents still need access to SA1 records, a custom LWC would be a good option.

    Important: Custom search alone won't restrict standard Global Search. You'll also need to review field permissions and other available search paths.

    Hope this helps!

0/9000

Hi Everyone! I am taking my career to the next level by learning how to be a SF Administrator and on to a SF Developer after I was let go from my client success role at a Saas company back in April and have been unable to find a new role since then. I loved working on the SF platform at my previous role so it seemed like a great next step for me! I am very excited to learn from all you in the coming years! 

4 comentarios
  1. 7 dic 2020, 14:49
    Good luck, @Ashley Owens! The ADM 201 certification is a great way to demonstrate your knowledge of Salesforce. It will certainly boost your credibility and open doors in the Salesforce ecosystem!
0/9000

Hi All,

For Community 'Ideas' validation (of offensive language) - how do we avoid the Scunthorpe problem?

Not sure if there is already material on this; I've made a Github page with validation pages for both Ideas creation and also when commenting on Ideas (as detailed in the Ideas Implementation Guide -

https://eu3.salesforce.com/help/pdfs/en/salesforce_ideas_implementation_guide.pdf

). I'm hoping this helps make adding words to validation pages efficient for everyone (obviously feel free to commit to this list!).

However, I'm hoping an experienced SF developer knows how to avoid the Scunthorpe problem (

http://en.wikipedia.org/wiki/Scunthorpe_problem

).

Currently I have excluded words to compensate based on my company's user base and the words they tend to use, but it would be great to add some code so that we can have a universal validation list for everyone to use no matter what sector we work in.

Any thoughts/experiences with this?

Kind regards,

Mark Rossiter

Ideas Validation on Github

6 comentarios
0/9000
My company - NAVEX Global (HQ in Lake Oswego, OR outside of Portland) is looking for a talented SF Developer. Anyone know someone or perhaps you may be interested in finding out more about what we've got going on. We have a lean team and are working on some exciting projects with opportunities to use everything SF has to offer. Here is the job post: http://www.navexglobal.com/career/SFDCDeveloper. Thank you.
0/9000