flxbl docs
slackGitHub
  • flxbl
  • sfp
  • sfops
  • Introduction
  • Minimal Framework
  • Who uses flxbl?
  • Learnings from the flxbl community
  • OVERVIEW
    • Principles
    • Modular Development Renaissance for Salesforce
    • Toolbox
  • TECHNIQUES
    • Development Practices
      • Why modular development in Salesforce?
      • Organizing your code / config
      • Defining the boundaries of a package
    • Source Code Management
      • Project Structure
      • Branching Model
      • Branching Conventions
      • Feature Toggling
      • Dealing with Org Specific Metadata
      • Handling Profiles
      • Tracking Manual Steps
    • Environment Management
      • Guiding Principles
      • Pooling Scratch Orgs
  • BUILD AUTOMATION
    • sfp
  • CI/CD
    • sfops
  • Libraries
    • sfdc-feature-management
    • sfdc-trigger-framework
    • nebula logger
  • tools
    • sfdmu
    • browserforce
    • pmd
Powered by GitBook
On this page
  1. TECHNIQUES
  2. Source Code Management

Dealing with Org Specific Metadata

Last updated 2 months ago

The following metadata types usually contain Org specific information, which means it has to be customized for each org when it's getting deployed, or the configuration in your develop org would end up being deployed to production.

The type of org specific metadata include

  • (in most cases)

  • (that contains any sensitive information)

sfp provide a concept of an package, where a source package will have folders that match the alias of the target org where the metadata is getting deployed. The components have to be duplicated across each of the environments with settings

AuthProviders
AutoResponseRules
ConnectedApps
CSP Trusted Sites
CustomMetadata
DataSource
NamedCredential
RemoteSiteSetting
SamlSSOConfigs
Settings
WebLinks
aliasified