Revenue Cloud Developer Guide

Get Started with Revenue Cloud Developer Resources
Revenue Management Settings
Revenue Cloud Deployment
Deployment Workflows and Sequence
Deployment Considerations
Global Unique ID Setup
Managing Component States
Post-Deployment Steps
Deployment Scenarios
Object Deployment Reference
Metadata Deployment Reference
Additional Deployment Information
Product Catalog Management
Salesforce Pricing
Rate Management
Product Configurator
Transaction Management
Advanced Approvals
Dynamic Revenue Orchestrator
Usage Management
Billing
Revenue Cloud Associated Objects
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Deployment Considerations

In any deployment scenario, you must understand all dependencies and prerequisites related to your planned changes.

Here's a list of things to consider and plan for.

Key considerations include:

  • What’s the sequence followed for object deployment? What dependencies exist on related objects?
  • Do your objects have Draft, Active, or Inactive states?
  • Does activation occur through an API or by simply setting a boolean field (active flag)?
  • Are there special fields to consider, such as text fields with embedded IDs, JSON, or fields populated via triggers?
  • Are there fields or objects that represent unique or sequential data that must be preserved in the target org?
  • How would you handle system settings between the orgs? For example, making sure that a feature toggle is turned off in the target org so that automation doesn't start executing when you insert data from your source org.
  • What's the impact of versioning on your deployment? For example, schema, app, or API versions.

For detailed information about these deployment considerations, see Additional Deployment Information.

Note