Community - About Viktor

Viktor · ‎03-20-2021

This maintenance has completed as planned

Viktor · ‎03-10-2021

Hi @gayendra concurrency does not directly cause throttling in case of outbound notifications. If a very high number of notifications are being sent, they will simply enter a backend processing queue on our end and that's why timing and/or order might be affected. They would not be rejected like in the case of inbound requests.

Viktor · ‎09-07-2020

Our Services team provided the following process that can be used where the indexed property needs to be changed as fast as possible on a live Production tenant where traffic is ongoing. The suggested procedure for changing a field from non-indexed to indexed with virtually no disruption risk: 1. create a yourcustomfield_NEW__c (indexed) field 2. export the values from the current yourcustomfield__c (unindexed) field and populate the yourcustomfield_NEW__c (indexed) field with the same values, using Zuora Connect tools 3. rename the yourcustomfield__c (unindexed) field to yourcustomfield_OLD__c (between step 3 and 4 is where you have a couple seconds of possible disruption) 4. rename the yourcustomfield_NEW__c (indexed) field to yourcustomfield__c (optional) 5. compare yourcustomfield_OLD__c and yourcustomfield__c and fix manually any discrepancy that might have occurred during the loading process.

Viktor · ‎02-19-2019

Hi @kcavanaugh just to confirm, you can already create separate Bill Runs based on charge type, so limiting it to Usage. So it is indeed possible to create a BR that only picks up your usage-only Subscriptions, although not based on the Subscription but the charge type.

Viktor · ‎11-20-2018

Just confirming here as well: Symantec certificate-related issues should be resolved now!

Viktor · ‎11-19-2018

Hello @Nigel , Thanks for reporting this. Just like you've mentioned before, the suggested workaround is indeed to use Edge or Firefox if you're being affected by this. I've actually worked on this last week with our Ops as we've detected some impact before, and that time everyone who was affected confirmed this to be resolved across the EU environment. I am curious it returned now, so I'll check with Ops once again.

Viktor · ‎10-05-2018

Additional information: A properly configured server will provide all certificates necessary to verify it’s server certificate, minus the root, during the TLS handshake. You can verify that the server provides a proper chain using https://www.ssllabs.com/ssltest/?leadsource=3787244 For example, if you take a look at www.zuora.com through the Qualys SSL Server Test. You will see that the server provides all of it’s intermediate CA certificates. For reference: https://www.ssllabs.com/ssltest/analyze.html?d=www.zuora.com&latest

Viktor · ‎08-08-2018

Hi @peterscheen it's possible to define how long a discount should be applicable for by using the End Date charge-level setting, please see my screenshot below. More on this: https://knowledgecenter.zuora.com/CB_Billing/WA_Dates_in_Zuora/D_Product_Catalog_Dates%3A_Product_Rate_Plan_Charge_Date_Attributes

Viktor · ‎07-19-2018

Please see this: https://community.zuora.com/t5/Billing-Payments/Can-I-set-external-payment-method-in-a-subscribe-call/m-p/14909/highlight/true#M834

Viktor · ‎05-21-2018

Answer: You can use the following call to create a charge that's only effective for one month, and only for the charges specified. Please note it's required to include the X-Zuora-WSDL-Version header with the value 85.0 , otherwise the fields will be ignored. POST /v1/object/product-rate-plan-charge HTTP/1.1 Host: rest.apisandbox.zuora.com Content-Type: application/json X-Zuora-WSDL-Version: 85.0 Authorization: X Cache-Control: no-cache Postman-Token: X { "AccountingCode": "Deferred Revenue", "ApplyDiscountTo": "ONETIMERECURRINGUSAGE", "BillCycleDay": 1, "BillCycleType": "DefaultFromCustomer", "BillingPeriod": "Month", "BillingPeriodAlignment": "AlignToCharge", "ChargeModel": "Discount-Percentage", "ChargeType": "Recurring", "Description": "DISCOUNT PERCENTAGE", "DiscountLevel": "subscription", "EndDateCondition": "FixedPeriod", "DeferredRevenueAccount": "Deferred Revenue", "Name": "DiscountTest", "TriggerEvent": "ContractEffective", "UOM": "each", "UpToPeriods": "1", "UpToPeriodsType": "Months", "ProductRatePlanChargeTierData": { "ProductRatePlanChargeTier": [ { "DiscountPercentage": 10.0 } ] }, "ProductDiscountApplyDetailData": { "ProductDiscountApplyDetail": [ { "AppliedProductRatePlanId": "2c92c0f84ed8ca48014eef22c3fe0cb4", "AppliedProductRatePlanChargeId": "2c92c0f94ed8d0d7014eef23eab027b3" } ] }, "ProductRatePlanId": "2c92c0f94e9a725b014eb1023249223c" }

Viktor · ‎05-21-2018

Question: How can we create a discount charge via REST API that's only applicable to specific producs and/or a specific time period?

Viktor · ‎02-23-2018

Glad to hear @avi91 , happy to help!

Viktor · ‎02-23-2018

Hi @avi91 you've mentioned you're using POST, and 405 is a not supported (HTTP) message, so I assume you were using the default Content-Type header, and not text/xml. My login() call has the following RAW data: POST https://apisandbox.zuora.com/apps/services/a/85.0 HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: text/xml;charset=UTF-8 SOAPAction: "" Content-Length: 465 Host: apisandbox.zuora.com Connection: Keep-Alive User-Agent: Apache-HttpClient/4.1.1 (java 1.5) Response: HTTP/1.1 200 OK Content-Security-Policy-Report-Only: xxx Server: Zuora App Content-Type: text/xml;charset=UTF-8 Content-Length: 731 Expires: Fri, 23 Feb 2018 19:13:55 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Fri, 23 Feb 2018 19:13:55 GMT Connection: keep-alive Let me know if this helps!

Viktor · ‎12-06-2017

Hi @chandra if you review our /action/ calls, these should be in the very same format and covering the same functionalities as the SOAP calls: https://www.zuora.com/developer/api-reference/#tag/Actions So whatever you see in SOAP's "describe" should also be available via an /action/query or an /action/create call etc. Let me know if this helps!

Viktor · ‎11-01-2017

Hello @Zcadiz we're experiencing a delay with sending invoices - all your triggered emails will be sent out eventually! Please subscribe to our Trust page to follow this incident: https://trust.zuora.com/

Viktor · ‎10-13-2017

@jhprinz Basically the "missing" RatePlanIds in the exports are for charges that have been already removed. In the following example, I have removed C-00013401 from the 1st version of the subscription, but as you can see consecutive subscription versions still continue to have it: Since every charge needs a "parent" rateplanid, these ids will pop up in Exports - but are hidden from queries. I have discussed this with our internal teams and this is expected operation. If you'd like to have the same result set for your exports, you could exclude these rows by adding "and amendment.type != 'RemoveProduct'" to your export query. These should not relate to any segments in use, as explained by this article too: https://community.zuora.com/t5/Billing-Payments/How-to-find-all-latest-charges-of-active-subscriptions/m-p/14736/highlight/true#M818 Let me know if this helps finding what you're looking for.

Viktor · ‎10-13-2017

Thanks for the details @jhprinz I have replicated a similar scenario on my own environment and am investigating the details.

Viktor · ‎10-13-2017

Hi @jhprinz could you send me your tenant ID in a private message, along with a few example IDs that are missing from the query results? Thanks!

Viktor · ‎09-19-2017

Hi @_mikeSmith I have not seen a ticket from you (might have just avoided my attention), but I wanted to let you know this has been reported to our Developers already, as this seems to be affecting all Date-related functions like quarter() or month(). We expect this to be fixed shortly!

Viktor · ‎09-13-2017

@_mikeSmith you can register and log a case at support.zuora.com !

Viktor · ‎09-12-2017

Hi @_mikeSmith I've done some testing around this, and it seems to me this is actually a bug as I've managed to capture some errors in our internal logs. Could you open a Support Ticket regarding this please, as this will need more in-depth investigation? You can address the ticket to me and I can continue working on this.

Viktor · ‎09-12-2017

I'll take a look at this @_mikeSmith - ping me again if you would not hear from me tomorrow!

Viktor · ‎09-07-2017

Please also note that some REST solutions tend to append "Params" after the endpoint defined in the POST, e.g. POST https://apisandbox-api.zuora.com/rest/v1/accounts?%24format=json Since the "Signature" generated by the HMAC call is specific to the uri defined in that call, and the appended "param" makes this a completely different URL, the generated Signature won't work for your 2nd call in this scenario. You need to make sure the uri defined in the HMAC call's body is exactly the same as the POST endpoint of the followup call. If you need to, it IS possible to work with the appended "Params", you just need to generate the HMAC token/signature pair for the uri that includes the full URL including the Param.

Viktor · ‎09-04-2017

Hello @Sgaestel , I have good news for you! There is a REST equivalent of the Subscribe call, the /action/subscribe call! It's basically the same Subscribe feature, but using the JSON format. You can find more information on: https://www.zuora.com/developer/api-reference/#operation/Action_POSTsubscribe Hope this helps!

Viktor · ‎08-31-2017

Please note the above example usually requires the Origin header as well. The Origin header needs to be present and set to the same URL in both the HMAC and the succeeding POST call, e.g: POST /rest/v1/hmac-signatures HTTP/1.1 Host: apisandbox-api.zuora.com Content-Type: application/json Authorization: Basic xxxxxx== Origin: www.test.gov.uk Cache-Control: no-cache Postman-Token: xxx-e424-8a27-c289-xxx { "uri": "https://apisandbox-api.zuora.com/rest/v1/payment-methods/credit-cards", "method": "POST", "accountKey": "2c92c0f85e1d50df015e338f66746b01" } { "signature" : "xxx==", "token" : "xxx", "success" : true } -------------------------- POST /rest/v1/payment-methods/credit-cards HTTP/1.1 Host: apisandbox-api.zuora.com Signature: xxx== Token: xxx Content-Type: application/json Origin: www.test.gov.uk Cache-Control: no-cache Postman-Token: xxx-b669-9415-bba4-xxx {"defaultPaymentMethod": true, "cardHolderInfo": {"addressLine1": "77 Fallon Glen", "addressLine2": "", "zipCode": "94020", "state": "California", "phone": "4155551234", "country": "USA", "cardHolderName": "Bill Thiebault", "city": "Fremont", "email": "bill@testaddress.com"}, "expirationMonth": "10", "accountKey": "2c92c0f85e1d50df015e338f66746b01", "creditCardType": "Visa", "expirationYear": "2019", "creditCardNumber": "4111111111111111", "securityCode": "123" } { "success": true, "paymentMethodId": "2c92c0fa5e1d50a5015e383343db745a" }

Viktor · ‎08-02-2017

Yes! Go to https://www.zuora.com/apps/PaymentLog.do?method=batchHandleProcessingPayment Create a Windows CSV file with the following columns; PaymentId TransactionId GatewayType GatewayState GatewayResponseCode GatewayResponseMSG TransactionResultCode You can leave the TransactionId,GatewayResponseCode,GatewayResponseMSG blank. IMPORTANT: you still need to check every transaction if they exist in the gateway to see if the ultimate Status needs to be updated to Error or Processed.

Viktor · ‎07-12-2017

Hi @hdeschamps , my first suggestion would be a one month long percentage discount, could you elaborate what's not feasible with this approach? My configuration for your described scenario would be something like this: Subscription's initial term = 13 months, renewal term = 12 months The Rate Plan added has 2 charges: a monthly charge and a 100% discount that is ending after the first month:

Viktor · ‎06-26-2017

Hello @kconnor can you also confirm if your account that you're trying to charge has a default electronic payment method set up? Thanks!

Viktor · ‎06-26-2017

Hi @taikhuu I have moved your topic, please make sure you upvote it to grant it further visibility and help our Product team to prioritize.

Viktor · ‎06-26-2017

Hi @taikhuu I have taken a closer look at this and it seems to me this newly added field is indeed not available via Data Source Exports, currently it's only an API object. I'll move this topic to the Ideas boards as those are monitored directly by our Product Team who are responsible for enhancing these features.

Happy Business Starts Here