sf-metadata

You can automate Salesforce metadata validation by using pre-deploy checks that enforce naming conventions, structural integrity, and security scoring across multiple metadata types. This eliminates manual errors in object and field definitions before org deployment.

The best way to generate Salesforce metadata templates is through automated generation of standard definitions for objects, fields, validation rules, and permission sets. This includes templated guidance for fields and relationships based on local definitions.

Yes, you can query Salesforce org metadata structures using sf CLI v2. The automation applies across end-to-end workflows from local templates to org deployment, coordinating definitions with subsequent data operations.

Yes, this metadata automation supports permission sets and validation rules. It automates generation and validation of Salesforce metadata definitions for custom objects, fields, profiles, permission sets, and validation rules across the full lifecycle.

The orchestration order for Salesforce metadata deployment workflows follows a strict sequence: sf-metadata, then sf-flow, followed by sf-deploy, and finally sf-data. This maintains dependency tracking across all stages.

Yes, you need to run validate_metadata as a dependency before generating Salesforce metadata definitions. This ensures that frontmatter-based discovery and pre-deploy validation checks are properly enforced during the automation process.