Skip to main content

Limitations of Zuora Connectors for Data Warehouses

Zuora

Limitations of Zuora Connectors for Data Warehouses

  1. Last updated
  2. Save as PDF
Describes the known limitations in the current version of the Zuora Connectors for Data Warehouses feature.

This article describes the known limitations in the current version of Zuora Connectors for Data Warehouses

  • Revenue Objects are not supported in Zuora Data Connectors for Data Warehouses.
  • Monetary values of Billing objects are in the transaction currency and conversion to “Home Currency” is not supported.
  • Multi-org functionality is not supported in Zuora Data Connectors for Data Warehouses i.e. Retrieved data may not be filtered based on user organization within a tenant.
  • The self-service connector configuration UI supports setup for only a single entity in multi-entity tenants. If multiple entities need to be connected, each entity must be configured manually.
  • Using OLTP destinations for large data volumes might result in slower performance, delays, or data processing issues. To address performance issues, consider optimizing database setup, adding more resources, or exploring specialized databases or data warehouses.
  • Schema evolution is limited to safe, non-destructive changes.
  • To prevent disruptions and conflicts in destination systems, avoid changing data types, reusing column names, or reusing table names; If performed, data type changes, column renames, and reused names require manual intervention.