Add functions so that an admin can verify that an API user is not a UI user, and the password will never expire, and so that an admin can "reset" an API user who has accidentally become a UI user, so that the password will never expire. Alternately, prevent attempts to log in as a user who is an API user.
Callouts are frequently failing, and worse, detect that they have failed when in fact they succeeded.
A more intelligenty retry strategy may be helpful. A failed callout could be retried on a staggered schedule, for example 1 minute, 3 minutes, 6 minutes, 10 minutes, 15 minutes (1 + 2 + 3 + 4 + 5).
The ability to force a failed callout to retry again from the UI might be helpful.
The ability to stop a failed callout from retrying (without stopping all retries for all callouts) from the UI might be helpful.
I find the unusual layout of the Developer Center API Reference to be really unhelpful. Because the whole spec is on one page, it takes a really long time to load. And you can't use browser-search to navigate the specification for one API entry.
It would be most helpful to be able to export a tenant configuration to a file, like meta-data or similar, and have the ability to import it into a tenant. There are 2 use cases for this: first, to back up and archive configurations to satisfy auditor requests to validate no unapproved configurations have changed. Second, in ensuring environment integrity in API Sandboxes or Services tenants to your source/production tenant.
It should be possible to rearrange page layouts in Zuora for the different objects. Similar to the page layout functionality you find in Salesforce. This way you can create/add custom fields and show those fields where you would like on the Objects.
Since Zuora owns the integration from Zuora to Netsuite, it makes sense that the functionality should live on the Zuora side. In Zuora, the Netsuite Integration ID is just a text field. In Netsuite, that is a generated UNIQUE number. IF you happen to clone a charge and forget to delete the Netsuite Integration ID field, the cloned record in Netsuite gets updated with all of the details of the new charge and the old record basically disappears....and there is no error or other way of knowing that this happens.
If either Zuora OR the Zuora to Netsuite sync required that the Netsuite Integration ID field were required, then at the very least, a user would receive an error that this ID was already in use and we'd be able to avoid the errors altogether.
In the end, once we finally realize that there's an error, we have massive amounts of invoices and data in Netsuite that is actually being recognized under the wrong product because it is associated with an ID that was allowed to be duplicated. This would be a huge win for anyone that integrates Zuora with Netsuite. Thanks.
Customers have requested updated sample code be made available on https://github.com/zuora/ for PHP and Rudy.
We are currently working on this request. Subscribe to this article for updates.
The REST API field spelling should be consistent and not vary in terms of capitalized letters.
As an example the contacts CRUD actions:
Create, retrieve and update are using initial capital letters, for example the field success:
In contrary Delete is using small letters:
This problem is applicable to a lot of different objects. Another example:
"Accounts -> Get account" returns everything in small letters, while "Account -> Retrieve account" returns everything with an initial capital letter.
This makes it more difficult to work with case sensitive REST API framworks/libraries such as Java GSON. Instead of doing the serialization once, one has to do it twice, just because of the capital letters.
I frequently run into issues where my Aqua API request times out. When I look at the Aqua Job Finder, it indicates the job completed successfully. However, I cannot see how long the job took to run. All I see is 'As Of Time' which is the same as the 'Start Time'. It would be great if you could add the End Time / Completed Time. That would help me to determine how long to set the timeout on my request / job.
Please add the Completed Time for the Job as well as for each Query.
Feature Request: Extend the Manage Tenant Profile settings page with a list of tenant functions that have been enabled in a tenant
Status: under evaluation
Reference Number: DE10672
Business Need: When switching from sandbox to production, the options enabled on sandbox must also be enabled on production. Currently there is no quick way to see which option is enabled and whether sandbox and production are in sync.
Feature Request: Page View Options
Status: under evaluation
Reference Number: DE6843
Business Need: ‰Û¡ÌÝÌ Customer Accounts‰Û¡ÌÝå page system performance issue. Customer is requesting an additional setting to limit or increase the number of accounts displayed within the customer accounts page. Currently maximum of 25 accounts are displayed per page. He is asking for the ability to limit to 5 or less. In reverse the ability to display more then 25 per page.
We often get an UNKNOWN error when calling APIs. Recently we ran into a case where we were passing a custom field value that was too long for the value. It would be a simple thing to return that we exceeded the length. Instead the API returned UNKNOWN error. This is less than helpful. Improved error reporting would reduce customer development time. Also, since we ended up opening a support ticket it will reduce number of support issues raised.
Feature Request: Ability to delete old invalid values from pick list in custom field
Status: under evaluation
Reference Number: DE7566
Business Need: Currently in Zuora, the design of pick list in custom field is that once it is saved, one can only edit the values in pick list and cannot delete the values. However, some customers have old and invalid values that need to be cleaned out, therefore, they are asking for the ability to delete old invalid values from those pick list custom fields so that their end customers will not choose the wrong value.
Currently, there are c for many events on important objects (let's take, for this example, invoices) that allow timely callouts to external systems. Unfortunately, the current callouts are very limited and prevent a good implementation of an external service being synced in an efficient way to Zuora as they are lacking update and delete event notifications. For important objects, one should be able to set a callout on update or delete, not just insert. Having an insert-only callout doesn't enable efficient integration as it requires the receiving service to make many, many unnecessary queries to keep in sync with Zuora as it will never otherwise know if an object has been altered or deleted.
This would be more in line with standard web integration practices and would considerably simplify the application integration programming for our customers. This is under consideration by Product Management but not yet in our road map. Kindly reference to DE7193 for this enhancement request.
Feature Request: Longer character limit for account name (through API)
Status: Under evaluation
Reference Number: DE2732
Currently, our account name can be create with maximum of 50 characters, customer is requesting if we can make it longer. They have to build the account from scratch when any account name is over 50 characters.
Looks like currently Zuora does not allow to deactivate/ revoke a user if the status is pending activation. The work around suggested by support via ticket # 61582 is that we should update the email to our own or another email which we can access to first activate the account and then deactivate.
This seems coutner intuitive and a security risk. As a Zuora admin we should be able to deactivate/ revoke access at any given time.