#Automation47 discutindo

Potential Fix for Flow Deployment Error with emailSimple / Send Email Core Action

I ran into an issue when deploying a Flow that uses the Salesforce Flow core action Send Email.

The deployment failed with this error:

Send_Email_to_Users (Action) - We can't find an action with the name and action type that you specified.

The action metadata looked valid:

<actionName>emailSimple</actionName>
<actionType>emailSimple</actionType>

However, the issue ended up being the versionString inside the actionCalls node.

In my sandbox, Salesforce generated the emailSimple action metadata with:

<versionString>3.0.1</versionString>

But in production, the same Send Email action was being generated with:

<versionString>2.0.1</versionString>

After changing the Flow metadata from 3.0.1 to 2.0.1, the deployment completed successfully.

Example:

<actionCalls>
    <name>Send_Email_to_Users</name>
    <label>Send Email to Users</label>
    <actionName>emailSimple</actionName>
    <actionType>emailSimple</actionType>
    ...
    <nameSegment>emailSimple</nameSegment>
    <offset>0</offset>
    <versionString>2.0.1</versionString>
</actionCalls>

So, if you are seeing this deployment error with Flow Send Email / emailSimple, check whether the versionString value differs between sandbox and production.

This looks like an internal version mismatch for Salesforce’s emailSimple core action. The deployment error message does not directly identify versionString as the problem, so it can be easy to miss. 

Sharing a new update to the Salesforce Metadata Navigator plugin. 

The plugin now supports:

• comparing Profiles and Permission Sets together
• reviewing differences side by side
• updating both Profiles and Permission Sets directly from the plugin

This helps reduce the time spent navigating across different setup pages when reviewing or adjusting access. It is especially useful when validating security differences, troubleshooting user access, or cleaning up permission models. 

A few key improvements:

• compare Profiles vs Permission Sets in one place
• review changes before saving
• update access directly through the plugin
• streamline admin and architect workflows

Built this to make permission analysis and maintenance much more practical inside day-to-day Salesforce work. Would love feedback from the community. 

Built a new Object Explorer experience into Salesforce Metadata Navigator

 to cut down the clicks it takes to inspect object setup. 

You can jump into a specific object’s configuration from anywhere and browse it in a mini Salesforce-style Object Manager layout right inside the extension. Instead of bouncing through multiple Setup pages, you can quickly access: 

• Details
• Fields & Relationships
• Page Layouts
• Lightning Record Pages
• Buttons, Links, and Actions
• Compact Layouts
• Field Sets
• Record Types
• Search Layouts
• Object and Field Access
• Triggers
• Validation Rules
• and more

The goal was simple: reduce navigation time for admins and architects who spend too much time drilling through Setup just to find one object setting. 

It gives you a faster way to inspect metadata, open the exact setup page you need, and move between object-level configurations without losing context. 

If you work across multiple objects every day, this makes admin work feel much more direct and a lot less click-heavy. 

#Salesforce Admin #Trailblazer  #Salesforcearchitects  #Metadata  #Salesforce @* Release Readiness Trailblazers *@* Salesforce Administrators *@Admin Tricks #RRTreasureHunts #New Releases #Automation

One small Salesforce debugging pain point I wanted to solve: 

You see a validation rule error in the debug logs, but you have no idea where it’s coming from.

In large orgs, manually checking objects and validation rules can take forever. 

So I added a feature in my Salesforce Metadata Navigator

plugin that lets you search validation rules using: 

🔍 Error message 

🔍 Validation rule name 

🔍 Object name 

The plugin searches across your metadata and helps you instantly find the exact validation rule causing the issue. 

This has already been a big time saver during debugging and support work.

Sharing a quick demo GIF below. 

Would love any feedback, suggestions, or ideas for improvement from the Salesforce community! 

#Salesforce @* Release Readiness Trailblazers *@* Salesforce Administrators *@Admin Tricks #RRTreasureHunts #New Releases #Automation

 Hey Trailblazers! Quick Permission Set Magic is now available in  Salesforce Metadata Navigator

I built a Salesforce metadata plugin that helps with things like: 

•  Comparing and editing permission sets
•  Navigating to objects, fields, flows, and validation rules faster

Permission set manager features: 

•  Pick 1 or 2+ permission sets to compare/EDIT side-by-side.
•  See exactly where they differ (object, field, system, Apex classes, VF).
•  Edit permissions directly and save changes back to Salesforce.
•  Export csv with the permissions.

I’d love to get your thoughts or any feedback on it.  

#Salesforce @* Release Readiness Trailblazers *@* Salesforce Administrators *@Admin Tricks #RRTreasureHunts #New Releases #Automation