#SF Developer1 discussing

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.

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! 

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 -

). 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 (

).

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