Comparison of Developer Tools and Data Loader
Comparison of features and behaviors between Developer Tools and Data Loader.
Feature Comparison
| Feature / Use Case | Developer Tools | Data Loader |
|---|---|---|
| User Interface | Separate micro-applications (for example, Generic API Loader, Billing Preview) | Centralized, self-service UI within the Zuora platform |
| Core Functions | Import, Update, Delete, Export, Cancel with csv files | Import,Update, Delete, Export and Cancel with csv files |
| Data Migration | collection of micro-apps for data migration tasks | Unified tool for data load, review, correction, and submitting the job |
| Performance | Legacy experiences often rate-limited;performance dependent on manual configuration (batch size, threads) | Dynamically scales through native internal infrastructure for consistent high performance |
| Error Handling & Validation | Limited validation; errors often required manual review at the end of the job and required re-upload | Auto-maps fields, provides in-line validation, and allows for incremental job submission to resolve failed records |
| Templates | Provides templates for each object loader | Provides dynamic, reusable, object-specific templates for data ingestion |
| Object Coverage | Support Zuora Billing, Payments and Finance Objects | Supports Zuora Billing, Payments and Finance Objects inclusive of the newly-released objects in Zuora ecosystem (for example, Payment Schedules and Omni Subscriptions ) |
| API | NA | Provides a public API for performing programmatic jobs with csv and json. See, Bulk Data. |