Community - About Saryu

Saryu · ‎06-21-2018

Solution : Our product catalog sync is a FULL sync if it is initiated from Zuora to SFDC and hence there is not way to do a selective sync at the moment. Although. If you have Bundling enabled, your Product sync is from SFDC to Zuora and the you can sync the product one product at a time from Salesforce to Zuora instead of ALL the products. You can use Order builder to sync one product at a time from Zuora to SFDC as well, Please review the article below : https://knowledgecenter.zuora.com/CA_Commerce/I_Development_Resources/C_Component_Library/G_Component_Library_Sample_Code/G_Product_Catalog_On-Demand_Sync

Saryu · ‎06-21-2018

Problem : The customer wants to implement "selective sync" of product catalog and product rate plans.

Saryu · ‎06-21-2018

Solution : As per the Product Design, The error is thrown because , zqu.zQuoteUtil.previewQuotes() method do not support to preview the Quote Metric value for Child Quote or Parent Quote or Readonly quote. Please confirm if you have the following setting enabled in your configuration which makes the Quote read only after it has been sent and hence you are unable to preview the metrics! Additionally, to keep this setting set to true, and not receive the error, Please set the field "zqu__IsChargeExpired__c" to False for Quotes with status "Sent to Z-Billing

Saryu · ‎06-21-2018

Problem When the the quote is sent to zbilling, we are seeing error message "Child Quote or Parent Quote or Readonly quote cannot be previewed."

Saryu · ‎06-20-2018

Solution : Tax is calculated on a Zuora Quote when making a preview call to core Zuora and the metrics are returned as per the calculation. For this use-case Initial term=12month Contract Effective date = 10/01/2018 Tax is calculated by 10%, Although the expectation is to apply 8%. We can see the Service Period = 10/01/2018-09/30/2019, so the Invoice Target Date = 10/01/2019, 10/01/2019 is within tax rate 10% period, so 10% was applied. In the Zuora Billing Engine, the determination date that decides using which effective period of tax rates of Zuora Tax is the target date. In other words, the target date decides the effective period of tax rates. When we preview a subscription, It has a preview period which contains a start date and end date, such as [startDate, endDate]. So the Invoice Target Date is the next date of the preview period's end date. Hence, the tax is calculated based on the Invoice Target date of the subscription.

Saryu · ‎06-20-2018

Problem : We have tax code A with ZTax engine. There are 2 periods with 2 tax rate. 04-01-2014 to 09-30-2019, the tax rate is 8%. 10-01-2019 to the future, the tax rate is 10%. So the customer expectation was: If charge trigger date within 04-01-2014 to 09-30-2019, the tax rate applied is supposed to be 8%. If charge trigger date within 10-01-2019 to the future, the tax rate applied is supposed to be 10%.

Saryu · ‎06-20-2018

The drop down is under the Quote Wizard Step Object Go to Setup > Create > Objects > Quote Wizard Step Go to the Field > Subscription Type Activate the picklist value "Cancel Subscription" This adds the values under the quote type!

Saryu · ‎06-20-2018

Problem : How can I enable the "cancel existing subscription for this billing account" option under the "Choose Quote Type" section of the New Quote flow ?

Saryu · ‎06-18-2018

Solution : We are aware of the request and working on the package to handle the same in the future, although at the moment the ways to resolve could be the below : 1. Reduce the number of fields in the Display Charge fieldset on the quote rate plan charge object. ( We have observed the issue with 19 fields in the field-set or more ) 2. When using the CpqSelectProduct Component, you can add your own JS and Css. You can add a min-width CSS rule to the page to expand the product name column.

Saryu · ‎06-18-2018

Problem : Product Selector drop down overlaps the first field one the Edit Quotes page when the product name is very large and a large number of custom fields added to the Display charge field set.

Saryu · ‎06-07-2018

Solution : After reviewing this issue, this error was caused due to the triggers necessary on Zuora and with the orders API, These fields were required, In Quotes 9.5 we introduced "Default Trigger Dates" in Quote settings which is necessary to be checked if you have orders, as this rolls down the value from Contract Effective date to Customer Acceptance date and service activation date. Go to Zuora config > Quote Configuration Settings > Enable Default Trigger Dates

Saryu · ‎06-07-2018

Problem : With Customer Org's with Orders enabled , we were seeing an error during the Quote Preview : ` Code: 58730000, Message: Effective date is not provided.; `

Saryu · ‎06-04-2018

Solution : After reviewing further, Here was the error stack from the Debug log 13:03:22.57 (1601272792)|EXCEPTION_THROWN|[234]|System.SObjectException: SObject row was retrieved via SOQL without querying the requested field: zqu__Quote__c.zqu__Status__c 13:03:22.57 (1601366197)|METHOD_EXIT|[219]|01p29000000JdCk|zqu.ZuoraQuoteSubmitController.checkOKForSend() 13:03:22.57 (1601983305)|VF_PAGE_MESSAGE|Exception in interacting with Zuora for information. Details:SObject row was retrieved via SOQL without querying the requested field: zqu__Quote__c.zqu__Status__c 13:03:22.57 (1602794974)|SYSTEM_MODE_EXIT|false 13:03:22.57 (1603441403)|SYSTEM_MODE_ENTER|true 13:03:22.57 (1603592217)|SYSTEM_MODE_ENTER|true 13:03:22.57 (1603688421)|SYSTEM_MODE_ENTER|false Looking at the code, it seemed to be referencing the quote.status field where as looking at the Quote Object on the customers org, I could see another field with the same field name. We advise against using the same names as the OOTB fields as that interferes in the process certain times. This has also been mentioned in the article : https://community.zuora.com/t5/Zuora-CPQ/Add-a-custom-field-in-Zuora-object-which-has-a-same-name-with-a/td-p/2310 After changing the API name of the field , the issue was resolved.

Saryu · ‎06-04-2018

Problem The customer received the following error when clicking on the "Send to Zuora" button. Exception in interacting with Zuora for information. Details:SObject row was retrieved via SOQL without querying the requested field: zqu__Quote__c.zqu__Status__c

Saryu · ‎06-01-2018

You did not see the Bill to / sold To contacts populating when creating a new quote from an existing account. After checking the bill to/ Sold to contact, I saw there was a discrepancy on the contact information with the contact in SFDC consisting of a "Phone" field value where as Zuora did not. After correcting the contacts to match the fields, I was able to successfully create the quote with the values populated : The reason is, Bill To/Sold To fields value are from SFDC Contact object. If SFDC Contact information does not match Zuora tenant Billing account Contact Information, then in the quote, Bill To/Sold To fields would not populate. Before we auto populate contact in Quote, we compare the contact information in the salesforce account and the one linked to billing account in Zuora side. The problem that we found out was that the phone in SFDC's contact side had a value where as Zuora did not. Basically before auto-population, we compare "First Name", "Last Name", "Email", "Phone", "MaillingStreet", "City" and "MailingPostalCode". If any of them are different, we don't do auto-population. For similar issues, Could you please compare the SFDC standard Account contact information and the corresponding Zuora tenant Customer Account Contacts information? We need to ensure they are the same, the validation needs to be successful for the value to be populated.

Saryu · ‎06-01-2018

Problem: During Quote creation The Bill to / Sold to contact are not getting populated.

Saryu · ‎05-30-2018

Solution : After reviewing this further, we found out that customer had translated the ‘Default’ record type of Quote object, but in quote creation page Zuora Quotes use the ‘Default’ to get the record type, that’s why the error happens. If removing the translation, we were able to get this to work 🙂

Saryu · ‎05-30-2018

Problem : Customers having errors when pressing the "New Quote" Button when the language is in french. They changed/updated it to "Principal" as per : https://knowledgecenter.zuora.com/CA_Commerce/A_Zuora_CPQ/C_More_About_Zuora_for_Salesforce/Localize_and_Customize_Labels_and_Messages However they were still get an error "Attempt to de-reference a null object Erreur dans l'expression '{!theOptions}' du composant <zqu:propertycomponent> dans component zqu:propertycomponent"

Saryu · ‎04-17-2018

The original subscription was: quantity: 10, list price: 4, discount: 25%, effective price: 3, total price: 30 The new subscription was: quantity: 20, list price: 4, discount: 40%, effective price: 2.4, total price 48 Hence, in order to get from 30 => 48, our amendment was quantity: 10, list price: 4, discount: x, effective price: y, total price 18 Here is the calculation : y = 18/10 x = y/list price * 100% y = 1.8 x = 1.8/4 * 100% = 0.55 * 100% = 55% There exists a special situation where the quantity stays the same but the discount is altered Example, the amendment will display a discount difference but showing quantity of 0 eg: quantity: 10, discount: 25%, total: 30 to quantity: 10, discount: 40%, total: 24 The amendment is: quantity: 0, discount: +15%, total: -6

Saryu · ‎04-17-2018

Problem : My QCS record for the update record on an amendment quote displays a different value on the Discount field. QCS Record : Here is the Initial Quote : Here is my Amendment Quote :

Saryu · ‎04-13-2018

Solution : The issue is occurring because of the ProductRatePlanCharge.zqu__Type__c value on some of the ProductRatePlanCharges. As of Quotes 9.3, we no longer support the 'OneTime' value on ProductRatePlanCharge object. Only the values, 'One-Time', 'Recurring', and 'Usage' are supported (note that One-Time is supported while OneTime is not). Please run the below query to find the value of this field on the Product rate plan charge object : select id,name,zqu__Type__c, zqu__EndDateCondition__c,zqu__ZuoraId__c,zqu__productRatePlan__r.zqu__product__c, zqu__Model__c,createdDate,lastmodifiedDate, zqu__SyncStatus__c from zqu__productRatePlanCharge__c where zqu__productRatePlan__r.zqu__product__c = 'Product SFDC ID' You will see that some of the Charges have the value, 'OneTime' on the zqu__Type__c field. As a workaround, please update the zqu__Type__c value on these charges from 'OneTime' to 'One-Time'.

Saryu · ‎04-13-2018

Problem : Product Catalog sync failing with the null reference error : ERROR: >>> zsync exception occurred: Attempt to de-reference a null object ERROR: >>> zsync exception occurred: Attempt to de-reference a null object

Saryu · ‎04-09-2018

In this short video, I’ll be going over two very familiar Sync errors on Zuora and how to resolve them: INVALID_FIELD:Foreign key external ID: XXXX not found for field Zuora__External_Id__c in entity YYYY DUPLICATE_VALUE:duplicate value found: Zuora__SubscriptionNumber__c duplicates value on record error with id: XXXX Here is a related Community articles that might also help: How do I resolve "INVALID_FIELD:Foreign key external ID" error with Zuora 360 Sync? As the Zuora for Salesforce SME for Salesforce Application, I look forward to your comments and questions!

Saryu · ‎04-08-2018

Solution : Rule 1 is associated with Filter 1 and Calculated Value 1. All the records are uploaded into Salesforce without any error and does show under individual objects, The association between the Rule and Filters/Calculated Values is not made. Rule ( In the Original ORG) Rule in Destination Org Rule object has a field "zqu_Json_c" which consists of the Id's of the Related objects i.e Filters and Calculated Values. The issue is related to handling 15 digit id and 18 digit ids of Calculated Values and Filter Conditions when used in rules. During the import process all the dependent record ids are replaced correctly, but are being converted to 18 digit instead of 15 digit. At the moment the application not able to link correct dependent Calculated Values for these cases. We are working towards enhancing the application to handle this issue in the future. Workaround : As a a work around,if you see the calculated value would be mapped correctly in the rule json eg. "calculatedValueId":"a0146000002xm6gAAA", but it has those extra last 3 chars ( this example is from my ORG ). That might be the cause of the issue. If we remove those last 3 chars the calculated values shows up. So for the time being you can use it as a workaround. Import the rules and calculated values / filters . Go to the rules which has the calculated values/ filters. Update the JSON to remove the last 3 chars. Example Change "calculatedValueId":"a0146000002xm6gAAA" to "calculatedValueId":"a0146000002xm6g"

Saryu · ‎04-08-2018

Problem : While performing an import from another SFDC Org, The Filters and calculated values do not seem to get associated.

Saryu · ‎04-06-2018

Solution : At the moment, IsEditable fields are derived only by Charge values, not by Charge Group values. Further validation is done in the UI. As a workaround, please consider the Charge Group type in your custom logic. Period is editable for group types, TYPE_PRODUCT_NEW, TYPE_AMENDMENT_NEWPRODUCT, TYPE_RENEWAL_NEWPRODUCT, TYPE_SUBSCRIPTION_ADDED.

Saryu · ‎04-06-2018

Problem If we call the isPeriodEditable field using the chargeGroups it does not mimic the UI functionality. For amendment quote with original charges, the field is un-editable in the UI although zqu.zCharge.isPeriodEditable returns a 'true' value. You can embedd the below code in you Quote Rules engine plugin to retrieve the value : for(zqu.zChargeGroup chargeGroup: zcgs){ //System.debug('original group id '+ chargeGroup.originalChargeGroup.groupID); //System.debug('current group id '+ chargeGroup.groupID); //for(zqu.zCharge originalCharge: chargeGroup.originalChargeGroup.zCharges){ //// originalChargePeriodMap.put(charge.ID, charge.PERIOD); // System.debug('original charge period '+originalCharge.Id + originalCharge.PERIOD+' '+originalCharge.chargeObject.get('isUpdated__c')); // System.debug('original PRPC '+originalCharge.PRODUCT_RATE_PLAN_CHARGE_ZUORA_ID); //} for(zqu.zCharge currentCharge: chargeGroup.zCharges){ //String originalPeriod = originalChargePeriodMap.get(charge.ID); //System.debug('retrieved original charge period '+originalPeriod); //System.debug('current charge period '+currentCharge.Id + currentCharge.PERIOD+' '+currentCharge.chargeObject.get('isUpdated__c')); System.debug('current charge PRPC '+ currentCharge.PRODUCT_RATE_PLAN_CHARGE_ZUORA_ID); System.debug('current charge isPeriodEditable '+ currentCharge.isPeriodEditable); } } Or you can call the class directly from the Dev Console using the below code : String quoteId = 'PUT QUOTE ID HERE'; List<zqu.zChargeGroup> chargeGroups = zqu.zQuoteUtil.getChargeGroups(quoteId); for(zqu.zChargeGroup chargeGroup: chargeGroups){ for(zqu.zCharge charge: chargeGroup.zCharges){ System.debug('name'+charge.NAME+' '+charge.isPeriodEditable); } }

Saryu · ‎04-06-2018

Since our ZQuote 7.40 release , the Billing Account Selector has been made configurable with a new plugin on the SelectBillingAccount component. This can be used to filter out certain accounts from showing up or pre-selecting a specific one for the user) Please review the 7.40 Release Notes : https://knowledgecenter.zuora.com/AA_Whats_New/S_Previous_Z-Force_Releases/V_2016_Zuora_for_Salesforce_Release_Notes/B_Zuora_Quotes_Q3_2016_Release_Notes#Maintenance_Release_7.40) The new ICustomizeBillingAccountPlugin plugin supports the following customization: For billing account selection Set the default billing account type to New or Existing Filter billing accounts This is what you would be looking for, Set the default billing account Control whether users can change the default billing account Please See SelectBillingAccount Component for the information about the Customize Billing Account Plugin and sample codes.

Saryu · ‎04-06-2018

Problem : How can I customize my Billing Accounts section and choose to display only the selected accounts v/s ALL the billing accounts in the create quote page?

Saryu · ‎03-19-2018

Solution : Starting from the release 2.9 of Zuora Connector for Salesforce CPQ, when sending quotes into Zuora, the price sent will be based on the Customer Price instead of the Renewal Price for Flat Fee and Per Unit charges. This change comes into place to support the proper behavior of the Salesforce CPQ Renewal Price field, which enables a user to configure the pricing that will carry forward when the Salesforce CPQ Contract is renewed, without affecting the current term's price. Although, we are working on enhancing this behavior to also factor in the Proration Multiplier which will be fixed in our version 2.10.1 This enables the connector to prorate products whose billing period is different than the Contract period. Please let us know if you have any questions and our product team will be engaged in any queries our customers may have! Zuora's strives to make the product ideal and better with each release that is implemented and we continue to do so.

Happy Business Starts Here