This topic describes the scope and limitations of Revenue metadata deployment, including unsupported operations, environment constraints, and tenant relationship use cases.

Revenue metadata deployment has the following limitations:

• You cannot download compare results for Revenue metadata deployments.

• Delete operations are not supported. Only reverting a deployment is available. Existing configurations in the target tenant cannot be deleted.

• Usernames, passwords, and other authentication secrets are not migrated as metadata. Configure authentication and credentials separately in the target environment.

• Revenue-only source tenants require OneID-based authentication and the correct environment-specific OneID endpoint.

• You cannot use a source tenant created with a production OneID endpoint as a sandbox source tenant. Select the endpoint that corresponds to the environment of the source tenant.

• The Revenue deployment experience depends on the availability and behavior of the Revenue Settings Service and Revenue APIs. A Revenue component may be unavailable or fail validation if its API, data, or required dependency is not ready.

• Few Revenue components have nested or parent-child dependencies. A deployment may be incomplete if a required parent component is missing or if a dependent component is deployed before its prerequisite.

• Deployment Manager does not support the deployment of transactional data associated with any revenue metadata.