About jbrown

jbrown · ‎11-28-2016

It would only work in those scenarios...but you can't set up scenarios in the product catalog..you can only choose one option for a charge. So we chose align to Term which works in most scenarios but then when we push sub changes from salesforce (for example), they will automatically use that setting and then we would have to amend each charge to another alignment in these scenarios.

jbrown · ‎11-28-2016

No, no answers. We're stuck with the current options, so we have to manually adjust all of the ones with that situation to a different alignment.

jbrown · ‎11-04-2016

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.

jbrown · ‎11-04-2016

We run into data issues in Salesforce because when we run the 360 sync, it syncs ALL products, rate plans, charges, ever...even if we have deleted them. It would be extremely helpful and make our Salesforce data much cleaner if there were either global settings in Zuora Commerce that would allow us to check "Don't sync deleted products" (and/or rate plans, charges, etc.) AND/OR be able to manage it on a record-by-record basis. The latter would also be helpful during the development of new products. We could mark them as "Do Not Sync" until it is complete. This caused us the biggest issue when we paid to have our API sandbox rebuilt. The products didn't get created correctly the first few times so the services team deleted them and recreated them. Since Zuora maintains deleted records in their DB, those too get synced. Although the deleted records get marked as such in Salesforce, it creates hundreds of records that we'll never use. Deleting them from Salesforce is futile because the next sync will re-add them.

jbrown · ‎09-27-2016

This is super important. When a billing address is updated in Zuora and then synced to Salesforce, a mismatch can (and does for us) lead to incorrect data. For example, if the initial billing contact is in New York, New York USA and then is changed to an address in another country, the billing team will remove the value from the State/Province field...but this won't update the State/Province field in Salesforce. So now, when we pull that address onto a contract, it has 123 Something Street, Other City, Other Country New York. Although the Salesforce API does not support updating values to NULL, it does support the passing of an empty string. Please consider this for one of the upcoming releases.

jbrown · ‎09-20-2016

When we sync products and charges to Netsuite, there is a field in Netsuite (Display Name) that does not exist in Zuora. If you change that product's name, it changes all of the related names in Netsuite EXCEPT for the Display Name. So all of the charge related fields show one name and the display name shows another. That field should be supported by the integration. There should be a "Netsuite Display Name" custom field that we can change when we change the charge names.

jbrown · ‎09-15-2016

Hi Lei, Yes. If you look at our recent ticket (https://support.zuora.com/hc/en-us/requests/99431), you'll see all of the details. Happy to fill in any blanks you might have. Let me know. Jenn

jbrown · ‎09-15-2016

The Billing Period Alignment options allow for "Align to Charge" and "Align to Term." However, if you want all of your recurring charges to invoice on the same schedule, no matter what the renewal term or billing term, there is no setting. We use "Align to Term" now and if customers have matching Billing Period and Renewal Term (Monthly billing and 1 month Renewal, for example), a mid-term change will generate a prorated invoice for the remainder of the month and then pick up all charges at the next billing period. This works great. But when we have a customer that has Quarterly billing period and monthly renewals for example, a mid-term change misaligns those same charges with the same settings. Since charges are configured by Billing Frequency, we only have the ability to configure our Quarterly charge with one option. So changes for this customer are manual every time.

jbrown · ‎06-24-2016

We would love to know when this is planned for, as well. This will be a great new feature!

jbrown · ‎05-11-2016

We can customize the name of a Batch, but not add a custom field. We have integrated software that updates information, based on Batches. Although it would be feasible to use a custom name and code the integration on that, it's not best practice to build code on names/text. If we had a custom field, we could use that in the integration logic.

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Re: Add Align to Billing Term Option

Re: Add Align to Billing Term Option

Make Netsuite Integration ID Unique

Add 360 Sync "Management" Settings

Re: Update custom fields to null in SFDC through Z...

"Netsuite Display Name" Custom field for integrati...

Re: Add Align to Billing Term Option

Add Align to Billing Term Option

Re: No invoices to be genrated for 0 qty usage

Custom Fields on Batch Object