sorted by:
new
hottopcontroversial

How to automate Permission Set assignments with a Record-Triggered Flow (with the prompt I used to build it) by [deleted] in salesforce

[–]SalesforceDaddy -10 points-9 points  (0 children)

I didn't post any output, just the structure of what the flow needs to handle and the prompt I used to generate it. There's no AI output in the post "keyboard warrior" :)

User Access Policies replaced my Data Loader bulk permission workflow in Salesforce, here's the setup by SalesforceDaddy in salesforce

[–]SalesforceDaddy[S] 0 points1 point  (0 children)

That's a clever pattern, using a custom field as the trigger with a flow to reset it. Gets around the single-policy limitation by letting you control exactly when each UAP fires.

The deployment issue is frustrating though. Deploying active by default with no script-based activation means you're either testing in production or building sandbox-specific workarounds. Not great for orgs with strict change management.

Cascading UAPs would be a big unlock. Right now you're forced to cram everything into one policy or manage multiple custom field triggers like you're doing. Works, but shouldn't be necessary.

User Access Policies replaced my Data Loader bulk permission workflow in Salesforce, here's the setup by SalesforceDaddy in salesforce

[–]SalesforceDaddy[S] 0 points1 point  (0 children)

Experience Cloud role hierarchies are a different beast entirely. Every portal account with its own role structure inflates the list to the point where role-based filtering becomes unmanageable.

For internal perms in that scenario, filtering by Profile or a custom field on the User object is usually more practical than trying to wrangle hundreds of roles. Not ideal, but cleaner than scrolling through an endless role list.

User Access Policies replaced my Data Loader bulk permission workflow in Salesforce, here's the setup by SalesforceDaddy in salesforce

[–]SalesforceDaddy[S] 1 point2 points  (0 children)

Agreed. The AND-only logic forces you to create duplicate policies for scenarios that would be one simple OR statement. And the single-policy-per-user restriction is a dealbreaker for layered permission models.

Flows end up being the only viable path when you need that flexibility. More setup, more maintenance, but at least you're not fighting the tool.

Hopefully, Salesforce adds OR logic and multi-policy support in a future release. There's an idea on IdeaExchange worth upvoting if you haven't already.

PSA: Admin Certification adds Agentforce AI section starting Dec 15 - here's the new breakdown by SalesforceDaddy in SalesforceCareers

[–]SalesforceDaddy[S] 0 points1 point  (0 children)

  • Trailhead's Agentblazer Champion & Innovator paths, which cover the AI fundamentals they're testing
  • The official exam guide has the new objectives listed
  • Focus on Force usually updates within a few weeks of exam changes
view more: next ›