Toolbox Commands
The same metadata magic that powers OrgFlow's end-to-end DevOps functionality — also available for your own Salesforce scripting and automation ideas.
As comprehensive as OrgFlow's end-to-end DevOps functionality is, sometimes you need to automate or perform repetitive one-off tasks around Salesforce — perhaps unrelated to your normal Salesforce DevOps process. For those times, we provide a set of automation utility commands.
* Available in Pro and higher editions
Retrieve metadata
Way more powerful than the Salesforce CLI, the retrieve command is your general-purpose metadata retrieval tool. You specify one or more metadata filter rules and OrgFlow handles the rest — querying Salesforce for available components, generating the necessary retrieval manifests, and splitting the retrieval up in multiple concurrent batches for optimal performance.
Deploy metadata
The deploy command takes a metadata archive on disk and deploys it to a Salesforce org. Unlike the Salesforce CLI, OrgFlow takes care of all the heavy lifting — creating or updating the necessary package manifest files to match the archive content, creating the ZIP file for deployment, submitting it for deployment, and monitoring and reporting the deployment and test results.
Normalize and prune metadata archives
Sometimes metadata we get from Salesforce needs tidying up. The normalize command fixes any inconsistent indentation and formatting, as well as any non-deterministic element ordering, so that your metadata can be more reliably compared and versioned. The prune command removes any metadata components that don't match the set of metadata filter rules that you specify.
Compare and analyze metadata archives
Integrate our powerful metadata comparison engine in your own automation projects. The diff command compares two metadata archives on disk, prints a detailed diff report and writes the delta as a deployment archive. The stats command analyzes a metadata archive on disk and prints out key statistics, such as the number of components per metadata type.
Generate package manifests
Even though OrgFlow doesn't need them — even for deployments — package manifests are sometimes needed by other tools you may want to integrate or share your repository with. But crafting package.xml files by hand can be tedious and error-prone. The manifest command inspects a metadata archive on disk and creates or updates its package manifest files to match its content.
Apply and commit metadata
The apply command takes one metadata archive on disk and applies it on top of another one, while considering any metadata filters you specify. The commit command analyzes uncommitted changes in any local Git repository that contains a metadata archive, connects to Salesforce to find out which user last modified each of the changed metadata files, and then commits the changes grouped per Salesforce author.
Manage sandboxes
Managing sandboxes through the Salesforce UI cannot be automated, and doing it through the Salesforce CLI doesn't give you control over things like sandbox type and description. OrgFlow provides sandbox management commands better suited to org-based development, allowing you to create, delete and list sandboxes as part of your automation projects.
Ready to see what the fuss is all about?
Don't take our word for it — see for yourself! Try OrgFlow free for 2 months. No limits. No strings attached. No credit card or billing information required.
Try Now