Happy Business Starts Here

How do I know what records Zuora attempted to sync to Salesforce?

Highlighted
Community Manager

How do I know what records Zuora attempted to sync to Salesforce?

See Reply



Subscribe to Zuora System Updates at Zuora Trust
Follow Zuora Global Support on Twitter and LinkedIn

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Manager

Re: How do I know what records Zuora attempted to sync to Salesforce?

Problem Statement:
I find that a few records are not in Salesforce after a manual sync. How do I know if Zuora attempts to sync them to Salesforce?

Solution:
Checking Salesforce Bulk Data Load Jobs

Step 1: Under your login name, go to Setup > Administration Setup > Monitoring > Bulk Data Load Jobs
Step 2: Click on a Job ID > Batches
Step 3: View Request > Save as request.zip
Step 4: Unzip request.zip > open the file > search the record ID

 

Please note that Salesforce keeps the last 7-day log only.

 

Supporting References:
https://knowledgecenter.zuora.com/CA_Commerce/B_Zuora_360/F_Synchronize_Your_Data/O_Field_Reference



Subscribe to Zuora System Updates at Zuora Trust
Follow Zuora Global Support on Twitter and LinkedIn

View solution in original post

1 REPLY 1
Highlighted
Community Manager

Re: How do I know what records Zuora attempted to sync to Salesforce?

Problem Statement:
I find that a few records are not in Salesforce after a manual sync. How do I know if Zuora attempts to sync them to Salesforce?

Solution:
Checking Salesforce Bulk Data Load Jobs

Step 1: Under your login name, go to Setup > Administration Setup > Monitoring > Bulk Data Load Jobs
Step 2: Click on a Job ID > Batches
Step 3: View Request > Save as request.zip
Step 4: Unzip request.zip > open the file > search the record ID

 

Please note that Salesforce keeps the last 7-day log only.

 

Supporting References:
https://knowledgecenter.zuora.com/CA_Commerce/B_Zuora_360/F_Synchronize_Your_Data/O_Field_Reference



Subscribe to Zuora System Updates at Zuora Trust
Follow Zuora Global Support on Twitter and LinkedIn

View solution in original post