About Goutham

Goutham

CRUD- Create and Delete operation: In this video we have provided simple example to create and Delete an account using CRUD operation, these operations can be used in more complex scenarios CRUD -Update CRUD update for account object is handled in this example, Mass update on objects can be done using this operation.

Goutham

Question: Workflow trigger through callout is performed by the API token and by Basic username and password as given in the following KC. https://knowledgecenter.zuora.com/CE_Workflow/Using_Workflow/Trigger_a_Workflow_via_Callouts User needs to trigger the callout using OAuth Bearer token Solution: The Workflow triggered through OAuth bearer token is performed through the regular Rest API URL followed by the workflow ID POST - https//rest.apisandbox.zuora.com/workflows/{{workflow_id}}/run US sandbox - https//rest.apisandbox.zuora.com/workflows/{{workflow_id}}/run Prod - https//rest.zuora.com/workflows/{{workflow_id}}/run EU Sandbox - https//rest.sandbox.eu.zuora.com/workflows/{{workflow_id}}/run EU Prod - https//rest.eu.zuora.com/workflows/{{workflow_id}}/run We can also get all the workflow details for the entity using the GET call Example - https//rest.apisandbox.zuora.com/workflows

Goutham

Question: User need need a REST API that does a preview of an existing subscription by only passing the Subscription number as available in the UI Solution We do not have the direct API call available to Preview subscription by only providing Subscription key (Subscription number/Subscription ID) option but please find the below example involving two API calls API 1: GET_SubscriptionsByKey Get the below information from the 1st API call by Providing only Subscription key (Subscription number/Subscription ID) contractEffectiveDate Accountkey productRatePlanChargeId productRatePlanId termType API 2: POST_PreviewSubscription The mandatory information received from the Get subscription by key API call should be used to POST the Preview subscription call Example Note: Multiple rate plan charge should be given inside the array

Goutham · ‎08-05-2019

Delay Task: This tutorial provide example to understand the Delay task in workflow. In this video we are using Delay task between two Bill runs and the same can be used between any task in different scenarios.

Goutham · ‎07-31-2019

Question Do we have documentation detailing an expected format for "4xx" and "5xx" status codes and we see difference in capitalization of response variables when calling a CRUD vs a newer REST APIs with response code 4xx. Is this response structure correct, and is this difference intentional Solution: For "4xx" and "5xx", they are standard HTTP status codes . The responses and errors for "200" status code is documented in Responses and Errors page because the response body contains Zuora-defined schemas. Response structure and capitalization difference: Basically the error response structure for a SOAP call contains an array of Error Object and a success field. The capitalization difference comes from the independent implementation of each product area. You have to query a specific engineering team to get the exact response schema.

Goutham · ‎07-31-2019

Problem: API general errors due to Zuora REST API version and Zuora WSDL version Scenario 1: User receives the error message even though they are using the New API call that supports the Invoice settlement https://www.zuora.com/developer/api-reference/#operation/POST_Subscription "message": "You have already enabled Invoice Settlement Permission, payment and refund in Zuora UI and SOAP API are still in process, please use the new REST API." Solution: The invoice settlement fields are in Zuora REST API version control. zuora-version should be set as 211.0 or later in the header. Scenario 2: User faces below error message when they are using CreateExport APi (/v1/object/export) Error Message : noSuchDataSource :[object] Solution: Zuora WSDL version plays key role in the Data source object error, Latest WSDL version should be updated to get the recently added objects X-Zuora-WSDL-Version: 88.0

Goutham · ‎06-30-2019

Answer: Get LatestPDFfile details for Debit/Credit memo from the respective API calls GET_CreditMemo and GET_DebitMemo Using Get-Files API call download the PDF file as shown in the below example In the response from Credit/Debit memo call the "latestPDFFileId" will be available and the id can be used to get the PDF file through the following call - (Example - https://rest.apisandbox.zuora.com/v1/files/2c92c08d699475ff0169993e379a5a9b )

Goutham · ‎06-30-2019

Question : Help us understand if we have any REST API call available to download the Credit Memo PDF/Doc.

Goutham · ‎04-03-2019

Solution As part of the Order Metrics migration, a new Amendment Type of "Composite" will appear in the Subscription to represent the Subscription creation. The below ZOQL query will fetch the Account and Amendment type detail "select SubscriptionVersionAmendment.type, SubscriptionVersionAmendment.ID, SubscriptionVersionAmendment.code, Account.AccountNumber from Subscription" Where the SubscriptionVersionAmendment.type provides the cancellation/composite type for an amendment.

Goutham · ‎04-03-2019

Problem Using the ZOQL Export API to get a list of recent amendments, and also the account they are associated with. However, for cancellation and composite amendments, I cannot get the account Id/name, or subscription id/name. Is there any way to get the account information from a cancellation/composite amendment, via ZOQL?

Goutham · ‎04-02-2019

Solution It is observed in this request that Tenant time zone is set as Pacific(PST) and the workflow is scheduled to execute daily at 11 PM EST. due to the time zone difference the effective date is set as previous date during the task execution User was suggested to use the below modified liquid code set for the effective date and it worked {{ "now" | date: "%Y-%m-%d %H:%M:%S %Z" | timezone: "%Y-%m-%d %H:%M:%S %Z", "%Y-%m-%d %H:%M:%S %Z", "Pacific Time (US & Canada)" | date: "%Y-%m-%d"}}

Goutham · ‎04-02-2019

Problem Customer built a workflow to add a credit card fee, as part of which a debit memo is created and an electronic payment is created. This workflow is scheduled to execute daily at 11 PM EST. We have observed an issue with setting effectiveDate in CreatePayment call to Data.Workflow.ExecutionDate. Hence it was updated to "2019-01-30 11:11 UTC". But, when the workflow execution gets delayed due to some issue the effective date remains same as previous day due to which the Create Payment API fails with error: "message" : "For electronic payment, effective date should be today's date or the payment should fail."

Goutham · ‎04-01-2019

We observe difference in custom field column name behaviour between AQUA and ZOQL as mentioned in the example below Example Describe call - /apps/api/describe/subscription <name>AutoRenew__c</name> <label>Auto Renew 1</label> please find the test results below Test Query - SELECT AutoRenew, AutoRenew__c, Account.Id, BillToContact.Id, DefaultPaymentMethod.Id, ParentAccount.Id, SoldToContact.Id, SubscriptionVersionAmendment.Id FROM Subscription ZOQL Response AQUA Response ZOQL export returns the column name directly from the describe call <name> Whereas both Stateful and Stateless AQUA mode returns the column name available in <label> Note: If the report is exported through Data source it will return the column name available in <label>

Goutham · ‎04-01-2019

User created custom field Auto Renew with API name AutoRenew__c, Since we already have a standard field Auto Renew in subscription AQUA results has Duplicate column names Question: Why the AQUA report is not displaying columns with API name while Zoql report does

Goutham · ‎02-09-2019

Solution What you have observed is by design, because there are two types of Profiles in Zuora, one is Default profile and the other is new communication profile which is especially for the end users. The Bill Run, Payment Run, Data Source Exports and Import notifications are present in default profile and once activated, it will send notifications to Zuora users within the organization. The new communication profile is customizable, they are designed for your end customers meaning it can be configured at Customer Account level and are intended to be sent to your end customers. This is the reason why new Communication Profile will not inherit all the notifications/emails available in the default profile. https://knowledgecenter.zuora.com/CF_Users_and_Administrators/Notifications/B_Viewing_Profiles

Goutham · ‎02-09-2019

Problem After creating new Communication Profiles, I noticed that some OOTB callouts/notifications are missing when editing the newly created Comm Profiles. The callout/notifications that I am specifically missing is "Payment Run Completion | Completed Status". This notification cannot be added through the UI since it is not in the Related Event list. Default Profile: New communication Profile:

Goutham · ‎02-09-2019

Solution: Currently Source and SourceID available via SOAP query, but not available under REST API call. Also, we can obtain the Source field through export, in the Knowledge center article fields mentioned as This field is in controlled release and they can be generated through Data source export. Reference (https://knowledgecenter.zuora.com/DC_Developers/G_SOAP_API/E1_SOAP_API_Object_Reference/Invoice)

Goutham · ‎02-09-2019

Issue: User not able to get the field 'Source' during a REST API call in Invoice, please find the query below, https://rest.zuora.com/v1/action/query { "queryString" : "SELECT ID,Source,Status FROM Invoice where ID = '2c92a0076390d4590163978cdc5a6d29'" } The response only shows ID and Status but not source { "records": [ { "Status": "Posted", "Id": "2c92a0076390d4590163978cdc5a6d29" } ], "size": 1, "done": true

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

CRUD operation in Workflow

Trigger Workflow through Callout using OAuth

Preview subscription API using Subscription number

Delay task in Workflow

API errors "4xx" and "5xx"

API general errors due to Zuora REST API version and Zuora WSDL version

Re: Download Credit/Debit memo PDF through REST API call

Download Credit/Debit memo PDF through REST API call

Re: Get the account information for composite amendment, via ZOQL

Get the account information for composite amendment, via ZOQL

Re: Workflow- For electronic payment, effective date should be today's date or the payment should fa

Workflow- For electronic payment, effective date should be today's date or the payment should fail

Re: AQUA and ZOQL returns different column names

AQUA and ZOQL returns different column names

Re: New Communication Profile Limitations

New Communication Profile Limitations

Re: Source field not available in the Invoice Record for REST API call

Source field not available in the Invoice Record for REST API call