Skip to main content

Known behavior


Known behavior

  1. Data Loader currently has support for CSV files encoded in UTF-8 format. This means that when using Data Loader, you can confidently work with CSV files that are encoded in UTF-8, ensuring compatibility and seamless data loading. UTF-8 encoding is widely recognized and provides robust support for a wide range of characters and languages, enabling smooth data integration and manipulation within the Data Loader.

  2. The file size limit for submission is set to a maximum 1GB. This means that any files that the user submits should not exceed this size threshold. We have implemented this limit to ensure optimal performance and efficient handling of the data submission process. Please make sure that files comply with this size restriction when submitting them,as it will help facilitate smooth and timely processing data. 

  3. Data Loader currently allows users to submit a maximum of 5 jobs. This means that you can initiate up to 5 separate job submissions within the given timeframe. We have implemented this limit to manage resource allocation in the backend effectively and maintain a balanced workload. By adhering to this maximum job submission limit, the users can ensure optimal performance. Please keep this limit in mind as the data migrations jobs are planned and scheduled.

  4. The first row of the CSV file must contain column headers.

  5. The import process is easier when the file structure resembles the object structure in Zuora. Product level recommendation would be to import data from the in-built templates. Data Loader will do the auto-mapping. You can later modify this mapping to your requirement.

  6. Data Loader supports One-to-One field mapping. With this mapping, each field from the CSV File can be mapped to the exact corresponding field in the target to create a similar environment from the previous system. This means that for every field in the source CSV, there is a single, specific field in the target where the data should be copied or loaded. 

  7. Data Loader’s current functionality includes support for acceptable data format at the API level, ensuring smooth and accurate data migration. However, to enhance this capability further, we will be working on expanded date format support for accommodating user-specific preferences.

  8. Data Loader retains the ‘Uploaded’, ‘Records successful’ and ‘Records failed’ files for 30 days. By the end of 30 days, these files will be deleted and no longer be available for download from the user interface.

  9. Data Loader supports Billing and Payments objects for Z Billing. It does not support Zephr, Payment Methods, and Z-Revenue objects.

  10. Data Loader supports Dynamic Templates. Dynamic templates allow users to customize data import formats based on the tenant level permissions enabled. It includes:

  • Multiple Organizations Label Fields on Account
  • Custom Fields 
  • Netsuite Integration fields (for Z Billing only)
  • Other tenant level permissions such as Multi-Currency, Invoice Settlement etc.
  • The objects supported for dynamic templates are as follows:
    • Credit-memo-from-charge
    • Credit-memo-from-invoice
    • Debit-memo-from-charge
    • Debit-memo-from-invoice
    • Product
    • Product-rate-plan
    • Subscription
    • Payment-schedule
    • Accounts-and-contacts
    • Accounting-code
    • Accounting-period
    • Payments
    • UOM
    • Usage