Read Connector
After you have an Ascend Read Connection set up, then you continue to set up the Read Connector in your dataflow.
Creating a New Salesforce Connector
The initial configuration of your Salesforce Connector can load all historical data or data dating back to a specified date. If you are uploading a large amount of data on the initial connection, there is an option to load the data by month to avoid timeouts in Salesforce. The Salesforce Connector will ingest every Salesforce record that has changed since the last refresh once the initial data is uploaded into Ascend.
Figure 1
- NAME: Read connector name to identify the specific data being collected.
- DESCRIPTION: Additional information about the connector.
Figure 2
- BROWSE CONNECTION: Click this button to explore Salesforce objects to ingest. Select the object you want to ingest and press CONFIRM.
Figure 3
- SALESFORCE OBJECT: The name of the object such as Account or Activity History.
- USE SALESFORCE BULK API (COMPOUND FIELD WILL BE EXCLUDED): Ascend supports both REST and Bulk API use. Check this box to utilize the Bulk API. Salesforce does not support the use of compound fields in the Bulk API. For additional information, see Salesforce's Bulk API.
- RECORDS AS JSON STRING: If selected, the data in the Generate Schema section will be returned as a JSON string of the full record.
Figure 4
If this box is not selected the data will be returned with multiple columns and rows.
Figure 5
- LOAD BY MONTH (FOR LARGE TABLE TO AVOID TIMEOUT): If selected, Ascend will ingest the data in month increments to avoid a timeout with the Salesforce API.
- LOAD START DATE: Specify the date you would like to start pulling from in the format
YYYY-MM-DD.
Generate Schema
Once you click on the GENERATE SCHEMA button, the parser will create a schema and a data preview will be populated.
- Add schema column: Add a custom column to the generated schema.
The schema will be generated according to if the RECORDS AS JSON STRING box is checked.
Refresh Schedule
The refresh schedule specifies how often Ascend checks the data location to see if there's new data. Ascend will automatically kick off the corresponding big data jobs once new or updated data is discovered.
Figure 6
Advanced Settings
Figure 7
- Assigned Priority: Is used to determine which components to schedule first. Higher priority numbers are scheduled before lower ones. Increasing the priority on a component also causes all its upstream components to be prioritized higher. Negative priorities can be used to postpone work until excess capacity becomes available.
Updated 10 months ago