Skip to main content

#Salesforce CLI0 discussing

 Introducing MetaDelta

: A Salesforce CLI Plugin Built for DevOps Teams 

 

As Salesforce DevOps engineers, we've all faced the same challenges:

 ❌ "Who modified this metadata?" 

 ❌ "What exactly was deployed?" 

 ❌ "Can I generate a package.xml only for what changed?" 

 ❌ "How do I audit Salesforce Core and Vlocity/DataPacks together?" 

 ❌ "How can I automate manual Salesforce Setup tasks?"

That's why I built MetaDelta, an open-source Salesforce CLI plugin focused on metadata auditing, deployment analysis, manifest generation, and manual task automation. 

🔍 Current Features

📊 Metadata Auditing

Identify metadata modified by a specific user within a configurable time window.

  •  Salesforce Core support 
  •  Vlocity / Industries support 
  •  User-based filtering 
  •  Change tracking across environments 
  •  Deployment investigation 

Perfect for answering:

📦 Smart Manifest Generation

Automatically generate deployment manifests from detected changes.

Supports:

  •  package.xml 
  •  package.yaml 
  •  Salesforce Core Metadata 
  •  Vlocity DataPacks 

Useful for:

  •  Hotfix deployments 
  •  UAT packaging 
  •  Release preparation 
  •  Partial deployments 

🔎 Deployment & Change Analysis

Analyze deployment activity and understand:

  •  What was deployed 
  •  When it was deployed 
  •  Which components were affected 
  •  Who performed the deployment 

A feature designed to reduce investigation time during incidents and release validation.

🤖 Manual Salesforce Setup Automation

One of the newest capabilities in MetaDelta.

Record and replay manual Salesforce Setup activities using Playwright-based automation.

Examples:

✅ Enable Salesforce features 

 ✅ Configure Agentforce settings 

 ✅ Navigate complex Setup pages 

 ✅ Standardize manual deployment steps 

 ✅ Reproduce setup tasks across multiple orgs

This helps transform traditionally undocumented manual activities into repeatable automation.

🎥 Record Once, Replay Everywhere

MetaDelta can:

  1.  Record manual Salesforce actions 
  2.  Generate executable automation scripts 
  3.  Replay them later across environments 

Great for:

  •  Sandbox setup 
  •  Release preparation 
  •  Environment standardization 
  •  Compliance processes

🎯 Built For

  •  Salesforce DevOps Engineers 
  •  Release Managers 
  •  Salesforce Architects 
  •  Vlocity / Salesforce Industries Teams 
  •  CI/CD Engineers 
  •  Enterprise Salesforce Programs

⭐ Why MetaDelta?

Most Salesforce tools focus on deployment.

MetaDelta focuses on:

✅ Understanding change 

 ✅ Auditing metadata 

 ✅ Generating deployment artifacts 

 ✅ Automating manual setup activities 

 ✅ Supporting both Salesforce Core and Vlocity ecosystems 

 

🔗 GitHub Repository

If you're interested in Salesforce DevOps, metadata governance, release management, or Salesforce Industries automation, I'd love your feedback.

MetaDelta GitHub Repository

⭐ Star the project if you find it useful.

Contributions, ideas, feature requests, and feedback are always welcome. 

 

 

Introducing MetaDelta: A Salesforce CLI Plugin Built for DevOps Teams As Salesforce DevOps engineers, we've all faced the same challenges: ❌

 

 

 

#Salesforce CLI  #Sfdx Plugins  #Salesforce Admin  #Devops  #Open Source Tool  #Release Management  #CICD

0/9000

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. 

 

#Salesforce Developer  #Flow  #Automation  #Metadata  #Deployment  #Salesforce CLI

0/9000

In this article we will look into detailed steps to setup Visual Studio Code as IDE for Salesforce code development.

How to Setup Visual Studio Code for Salesforce Development

1 comment
  1. Aug 28, 2025, 9:46 AM

    Hi to Resoleve this issue just Unchek this in Vs Code Setting 

    Hi to Resoleve this issue just Unchek this in Vs Code Setting

     

     

0/9000

Salesforce Code Analyzer v5.0.0 is Now Generally Available (GA) 

 

Code Analyzer

 is completely free and helps developers scan and fix problematic code, acting as a unified layer on top of a range of open-source code scanning engines. It's now available across all key DX experiences: CLI, IDE, GitHub Actions and DevOps Testing!  

 

v5 now comes with:

  • 2 new engines: Flow Scanner and Regular Expressions
  • AI-powered quick fixes by Agentforce for Developers 
  • A single command to execute Code Analyzer
  • A brand new, highly polished HTML report
  • A completely new YAML configuration file
  • New integrations with DevOps Testing, GitHub Actions

Our VS Code extension v1.6.0 is also available with quick fix functionality that calls through to our Agenforce for Developers LLM.  

 

See our updated documentation here.

 

#Agentforce #Code Analyzer #Devops #Salesforce CLI #Github

0/9000

I've built a 2GP Package that I am trying to release as a Unlocked Package.

 

I've overcome various validation errors due to missing features or settings in my Scratch Org Definition file. 

 

However my package includes a Sharing Set which depends on the Contact being 'Private' and by default its 'Controlled by Parent', is there a way to define this feature/setting in my Scratch Org Definition File? 

 

@* Experience Cloud * @*Experience Cloud Developers* @Unlocked Packages  @Salesforce DX @* Salesforce Platform *

 

#Salesforce CLI #SFDX CLI #Salesforce Platform #Unlocked Packages #Unmanaged Package #Second Generation Packages #Scratch Org Definition #Experience Cloud #Experience Builder

2 answers
  1. Dec 4, 2024, 2:18 PM

    @Tom Bassett this might help you - https://salesforce.stackexchange.com/questions/218183/sfdx-sharing-settings-scratch-orgs

     

    Is your package ultimately intended for public consumption, or are you just using it internally with your own org(s)?  Deploying sharing-related settings on standard objects can be tricky because the destination org may have valid reasons for how sharing is configured on their standard objects and can't change to support your package.

0/9000

Resources from the Salesforce Developers Ask Me Anything on Summer ’24 Snapshots & Salesforce CLI

 

I hope you joined us for the fantastic SFDevsAMA on Wednesday 31 July 2024 hosted by @Charles Watkins and featuring product managers @Rohit Mehta and @Vivek Chawla. They loved answering your questions about the updated #Salesforce CLI and Scratch #Org Snapshot. If you missed it, don't worry - we recorded the series and our experts have provided some great resources that our experts for you to continue your learning! 

 

Still have questions? Post them in this thread for our experts!

 

#Ask An Expert #CommUpdates #CommUpdates#CommUpdates #SFDX CLI #DX Snapshots

1 comment
0/9000

Summer '24 Snapshots & Salesforce CLI: Salesforce Developers Ask Me Anything July 2024

 

It’s a double whammy for the July edition of Salesforce Developers Ask Me Anything. Tune into our live stream with Lead Developer Advocate @Charles Watkins (his first AMA!) as he hosts Director, Product Management @Vivek Chawla and Senior Director, Product Management @Rohit Mehta to answer all your questions about:

 

  • Scratch Org Snapshots: Now generally available (GA) in Summer '24, snapshots let you capture and replicate the state of your scratch org, speeding up development and CI tasks.
  • Salesforce CLI (v2): Celebrating its first anniversary, the updated CLI offers better performance and stability, new source decomposition options, and automatic source mobility in Summer ’24.

Date: Wednesday July 31, 2024

Time: 9am PT

Theme: Summer '24 Snapshots & Salesforce CLI

Click here to register!

 

*If you cannot attend the livestream, don't worry - all sessions are recorded and can be watched on our dedicated AMA playlist on the Salesforce Developers YouTube channel.

Summer '24 Snapshots & Salesforce CLI: Salesforce Developers Ask Me Anything July 2024 It’s a double whammy for the July edition of Salesforce Developers Ask Me Anything.

#Org Snapshot #Salesforce CLI #SFDX CLI #Salesforce Platform @* Salesforce Platform * #DX Snapshots #Org Snapshot

0/9000

Hi Everyone,

I created a lightning app in my dev org. Retrieved the metadata xml in vs code and then deployed it to the test org. Now, I see the metadata in the test org via vs code and I can retrieve and deploy it via the vs code. But strangely I cannot see the lightning app in App Manager list view. Has anyone faced this problem? Am I missing something? Any help would be appreciated.

Thanks

 

#Salesforce Developer #Lightning App Builder #Salesforce CLI

4 answers
  1. Jun 24, 2024, 8:41 AM

    Hi @Preeti Rathore,

     

    It seems like you successfully deployed your Lightning app's metadata to your test org via VS Code, but you're encountering an issue where the app isn't appearing in the App Manager list view. Here are some steps to troubleshoot: First, check the Deployment Status in Salesforce Setup to ensure there were no errors during deployment. Next, try refreshing the App Manager page in the test org or logging out and logging back in to see if the app appears. Double-check the <YourApp>.flexipage-meta.xml metadata file to ensure it's correctly configured with the <masterLabel> and <description> tags. Verify that profiles in your test org have appropriate permissions to access the Lightning app. If you're using namespaces, ensure they're correctly applied in your metadata files. Lastly, consider checking if your Salesforce edition supports custom Lightning app creation, as some editions have limitations. If the issue persists, reviewing deployment logs in VS Code or Salesforce Setup can provide more insights into any encountered errors or issues.

0/9000