MVP Office Hours (US)

I started seeing this error msg on a flow that updates Campaigns which has lookups to Agency (Accounts) & Agent (Contacts). It wasn't occurring previously and it seems odd bc it started around the time I updated the Process Automation Settings page to reference a general Sys Admin license instead of mine. The Agency & Agent fields has had blank values in the past & present but it seems as though now it's an issue. Here's the logic on the Agency field (Filter Criteria | Agency: Account Record Type equals Agency). What else could be causing this. (It still doesn't happen in prod where yes, Agency & Agent are sometimes blank.)

In a scheduled flow, I need to add the Record Type Name in the filter conditions but the only thing I see is Record Type ID. How do I get around not hard coding the value?

In celebration of US Independance Day, we are cancelling our next scheduled call (July 3rd) 

Please join us for the next MVP Office Hours call on:  

Register for the next MVP Office Hours

If you have questions or topics you would like to discuss in our next meeting, please post them in detail here on the MVPOH Trailblazer Community.  Our members may be able to help you right away, and we'll be sure to include your question on the upcoming agenda.  Or just bring your questions, answers, and enthusiasm to help to our next meeting!  We hope to see you then.     

#SolveProblemsTogether

@Joy Shutters-Helbing  @Squire Kershner

Please join us for the next MVP Office Hours call on  

Friday, June 19th 2:00 EST

Register for the next MVP Office Hours

If you have questions or topics you would like to discuss in our next meeting, please post them in detail here on the MVPOH Trailblazer Community.  Our members may be able to help you right away, and we'll be sure to include your question on the upcoming agenda.  Or just bring your questions, answers, and enthusiasm to help to our next meeting!  We hope to see you then.     

#SolveProblemsTogether

@Joy Shutters-Helbing  @Squire Kershner

I'm struggling with allowing a persona (profile & perm set) to see the "Add Account Team" & "Add Opportunity Team Members" buttons on the Opty layout. I understand there are a few reasons what may be preventing this and here's what I can rule out. 

- Role sits above & adjacent to owner almost like an uncle if you think of it in the terms of a family. 

- The buttons have been added to the layout. Other persona's can see the buttons. Yes team selling has been enabled. 

- A sharing rule has been created to provide the role with Read/Write access to Accounts & Optys to the applicable Record Types

First - great call today - even though I almost missed it :) 

Next - I have a problem (of course :)) which I have just hit the wall on (otherwise I would have posted it before the call). 

 I have a flow approval process. I want to update two emails - one that goes to the reviewer (I found that one in an approval process flow). I updated that one. Now I'm trying to find the email that goes to the submitter. I'm not finding it anywhere. I have checked email templates, flows and some other places in SF and still not coming up with anything. There is a help article which says that these emails can be configured - just can't find it - any suggestions or thoughts? Thanks!!! Have a great long weekend all!

I’m struggling to unlock the core differentiator of the "Headless 360" concept relative to Salesforce’s historical architecture. 

"Growing up Salesforce" (and having worked at the Motherforce once upon a time), it was always drummed into us that Salesforce is an API-first enterprise platform. Because of this Service Oriented Architecture (SOA), everything—metadata, multi-tenancy, and data models—has historically been accessible programmatically.

For example, when I was a Product Owner at Cisco, our engineer end-users bypassed our massive Service Cloud UI entirely. Using Salesforce APIs, they built their own citizen-developer tooling ("Quicker") to crawl logs, fetch data, and update configurations via the standard API layer.

So my question to the architects here:

Is this just a modern rebranding of the classic decoupled, API-first SOA we’ve been using for over a decade? Or is there a fundamental structural shift in how the core platform, Data Cloud, and Agentforce are exposed that changes how we must design enterprise integrations? 

Maybe I need to get some hands on to understand it more rather than just briefs here and there— would love yalls take!  Thank you!

Please join us for the next MVP Office Hours call on  

Friday, June 5th 2:00 EST

Register for the next MVP Office Hours

If you have questions or topics you would like to discuss in our next meeting, please post them in detail here on the MVPOH Trailblazer Community.  Our members may be able to help you right away, and we'll be sure to include your question on the upcoming agenda.  Or just bring your questions, answers, and enthusiasm to help to our next meeting!  We hope to see you then.     

#SolveProblemsTogether

@Joy Shutters-Helbing  @Squire Kershner