About Jamie

Jamie · ‎02-07-2019

Related to this community message here https://community.zuora.com/t5/Zuora-CPQ/Why-System-NullPointerException-Argument-cannot-be-null-while/m-p/23591/highlight/false#M1774 I've experienced similiar error messages from within Zuora's package while trying to programmatically build quotes. In the example above, Zuora's code did not properly handle a scenario when the Address1 field was missing from a Contact so it threw a NullPointerException. I've received this same error message when the Initial Term wasn't populated on a Quote. Zuora's code should never throw NullPointerExceptions. Instead it should throw meaningful exceptions such as throw new ZuoraRequiredFieldException("Address1 on BillToContact is null"); Don't leave us guessing as to which field on potentially several different objects hasn't met some criteria required by Zuora.

Jamie · ‎02-07-2019

@GregT what's the latest status of Data Connect and how soon until it fully replaces the current 360 sync functionality?

Jamie · ‎02-07-2019

@nathanc any update here?

Jamie · ‎02-07-2019

Zuora's package should never be throwing a NullPointerException (that's sloppy coding). In this scenario above it should have thrown a meaningful error message such as throw new ZuoraRequiredFieldException("Address1 on BillToContact is null"); Don't leave us guessing as to what field on potentially several different objects hasn't met some criteria required by Zuora.

Jamie · ‎03-16-2018

@Liangqi what's the update on this? 7 months ago was your last comment when you said you would get back to us soon on the progress?

Jamie · ‎08-11-2017

Having it configurable would be fine with us. Thanks.

Jamie · ‎08-11-2017

@Liangqi This is clearly a defect that needs to be resolved so that Zuora data in Salesforce accurately matches what is in Zuora.

Jamie · ‎05-03-2017

Is that a realistic date this time? You originally stated it would be LA last fall.

Jamie · ‎04-03-2017

Hi @lukasz we're now in Q2 and I thought this was going to be ready in early Q1. Is this feature still not ready?

Jamie · ‎03-01-2017

Hi @lukasz I'll echo @feisley's comments. Depending on the type of feature we likely wouldn't want to risk breaking our production environment but one of our sandbox environments possibly could be used for this as long as we have the ability to opt-in to the new features. Follow up with me via email if you'd like to discuss more. Thanks.

Jamie · ‎02-27-2017

Hi @lukasz, you're probably tired of hearing from me about this ;) It's Feb 27th, has this feature be rolled out into Production?

Jamie · ‎02-02-2017

Hi @lukasz can you provide another update on this? Thanks.

Jamie · ‎01-13-2017

Note that this is not limited to custom fields. This behavior also affects standard fields on Zuora records. In addition, Salesforce API's do allow for setting values to null making use of "fieldsToNull" https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_concepts_core_data_objects.htm

Jamie · ‎12-21-2016

@lukasz We currently make use of Zuora's standard callout notifications for different events (new subscriptions, etc) to notify a custom web service we have about the change. In addition to that we have an integration that runs in Salesforce but updates custom fields in Zuora on Account records related to past due payments. When we update those custom fields, we need that same webservice callout to occur. We have been making that webservice callout from our Salesforce integration but its a more logical flow to have Zuora make that callout. Unfortunately it has never been possibly to trigger the standard Zuora callouts for custom field changes.

Jamie · ‎12-20-2016

Thanks @lukasz will we be able to participate in the LA release?

Jamie · ‎11-30-2016

Hi @lukasz. It's been a few months since the last update. What's the latest?

Jamie · ‎08-24-2016

Hi @lukasz Just checking in again now that it's late August. Any updates?

Jamie · ‎07-21-2016

Hi @lukasz. Any update on this will be rolling out in LA?

Jamie · ‎06-17-2016

@lukasz +1 for the being part of the limited release.

Jamie · ‎05-11-2016

Hi @feisley I appreciate your detailed response. In regards to your comment regarding "the use of "SeeAllData=true" is only bad if your test actually depends on org level data" I would present this scenario. In a fullcopy sandbox a unit test may need to create a Zuora.zObject('Account') object as well as create some custom Salesforce objects that have unique identifiers enforceable at the object level. Now in order to create these records my test custom objects can't be created with the same unique values as records that may already exist (since it's a fullcopy sandbox) so my test has to now look at existing data to make sure it's not creating test records with overlapping unique fields. My test shouldn't have to be concerned with records that already exist but is now forced to because SeeAllData needed to be set to true. If this data is currently stored in managed Custom Settings a solution could be to migrate it to Custom Metadata types which are already visible in test methods. This would eliminate the need to use SeeAllData=true to provide Zuora access to custom settings.

Jamie · ‎05-10-2016

Nice to see they posted my question as an idea. Yes.. this needs to be fixed!

Jamie · ‎05-10-2016

Agreed. Perhaps it should be a configurable option in the Zuora Product catalog sync. It can certainly add a lot of bloat to the sync.

Jamie · ‎05-10-2016

Zuora already has a "360" connection to Salesforce. It could certainly be possible for Zuora to build a customization that fetches the name of Account Owner from Salesforce based on the CrmID. This may not work for eveyone though as the Account.Owner may not be the same as the Sales Rep. I've built a custom integration using an iPaaS system that runs once a day to keep these values (SFDC.Account.Owner and Zuora.Acount.SalesRep in sync.

Jamie · ‎03-28-2016

This would be very helpful for us as well. I'd like to be able to configure a callout any time a change to an Account in Zuora occurs (including on custom fields).

Jamie · ‎03-16-2016

I've been asking for this from Zuora for years to no avail.

Jamie · ‎03-16-2016

Can someone at Zuora provide a reason behind that status classification of "unlikely"?

Happy Business Starts Here