ADP
Building the JDBC URL
After installing the license, access the connection management page by executing the command java -jar kingswaysoft.jdbc.jar. Enter the necessary details, and the program will automatically generate the JDBC connection URL. Users can click Test Connection to test the generated URL, and Copy to Clipboard to copy the connection string for use within the application where the JDBC driver is being used.
Note: If the license is not installed, you can still use the connection manager to generate a JDBC URL; however, the 'Test Connection' feature will be disabled.
General Page
The General page of the ADP Connection Manager allows you to specify the general settings of the connection:

General Settings
- Instance Type
-
The Instance Type identifies the ADP environment you're connecting to. It determines which ADP systems and data your integration will interact with.
- Token Server URL
-
The Token Server URL is the endpoint used to request OAuth access tokens from ADP. Your application authenticates here to obtain a token for secure API access.
- Use Authorization Header
-
The Use Authorization Header indicates whether the access token request credentials should be sent in the HTTP Authorization header.
- API Base URL
-
The API Base URL is the root URL for all ADP API endpoints in a given environment. All API paths are appended to this base URL when making requests.
- API Throttling Rate
-
The API Throttling Rate will limit the number of requests that can be sent per second. Set this value to 0 to disable API throttling.
Request Settings
- Role Code
-
The Role Code identifies the ADP security role assigned to the application or user. It determines which APIs, data domains, and actions are permitted.
- Mask Data
-
The Mask Data indicates whether sensitive data returned by ADP should be partially hidden or obfuscated.
Authentication Methods for ADP
Authentication
- Client ID
-
A public identifier issued by ADP that represents your application. Indicates which client is making the authentication request.
- Client Secret
-
A private key associated with the Client ID. It is used to prove your application's identity when requesting access tokens.
- Path To Certificate
-
The file system location of the client certificate used for certificate-based authentication with ADP.
- Certificate Password
-
The password used to protect and unlock the certificate file. It allows the application to access the private key during authentication.
Advanced Settings Page
The Advanced Settings page allows you to specify advanced settings for the connection.

Proxy Server Settings
- Proxy Mode
-
The Proxy Mode option allows you to specify how you want to configure the proxy server setting. There are three options available.
- No Proxy
- Auto-detect (Use system configured proxy)
- Manual
- Proxy Server
-
Using the Proxy Server option allows you to specify the name of the proxy server for the connection.
- Port
-
The Port option allows you to specify the port number of the proxy server for the connection.
- Username (Proxy Server Authentication)
-
The Username option (under Proxy Server Authentication) allows you to specify the proxy user account.
- Password (Proxy Server Authentication)
-
The Password option (under Proxy Server Authentication) allows you to specify the proxy user's password.
Miscellaneous Settings
- Timeout (secs)
-
The Timeout (secs) option allows you to specify a timeout value in seconds for the connection. The default value is 120 seconds. Specify 0 for infinite timeout.
- Retry on Intermittent Errors
-
The retry on intermittent errors determines if requests will be retried when there is an error. If this option is checked, requests will be retried up to 3 times.
- Ignore Certificate Errors
-
This option can be used to ignore those SSL certificate errors when connecting to the target server.
Warning: Enabling the "Ignore Certificate Errors" option is generally NOT recommended, particularly for production instances. Unless there is a strong reason to believe the connection is secure - such as the network communication is only happening in an internal infrastructure, this option should be unchecked for the best security.
Note: When this option is enabled, it applies to all HTTP-based SSL connections in the same job process.
- Concurrent Writing Threads
-
This option can be used to set the number of threads to be used during write operations. This can improve performance during large-volume write operations.
Using the JDBC Driver
Explore detailed examples in this section that demonstrate the application of JDBC classes such as Connection, Statement, and ResultSet to effectively manage interactions with ADP data. This section covers the use of regular statements and prepared statements for executing complex or frequently executed queries.
Executing Statements
Once you've connected from your code (see Connecting with DriverManager and Connecting with DataSource), you can execute SQL statements using the Statement class. Refer to the Executing Prepared Statements section for information on how to execute parameterized statements.
SELECT
Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data. To retrieve the results of a query, you would then call the getResultSet method of the Statement.
String sql = "SELECT * FROM hr/v2/workers/leaves WHERE aoid = 123"; try { ResultSet resultSet = statement.executeQuery(sql); LOGGER.info(resultSet.toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
INSERT
Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "INSERT INTO events/hr/v1/worker.leave.cancel (eventContext.associateOID, eventContext.workAssignmentID, " + "eventContext.leaveStartDate) VALUES ('G3EVERZ42YSP4E8T', '85826601N', '2020-07-15')"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors
null,null,null,{"events":[{"data":{"eventContext":{"associateOID":"G3EVERZ42YSP4E8T","workAssignmentID":"85826601N","leaveStartDate":"2020-07-15T00:00:00+00:00"}}}]},false
UPDATE
Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.
String sql = "UPDATE account-linking/federated-users/actions SET organizationKey = '7Oma78KO0d414s6rGxtXQ6nA8Pw6lIJX2SRGPaw/qhU=', " + "targetUserKey = 'c5ddc5b32e7d06e0cfb7952668551c3099', actor.userKey = 'c5ddc5b32e7d06e0cfb7952668551c30', " + "actor.federationID = 'd9ade5d5e25041158769987ecd5ac7e2', user.name.givenName = 'Alex', user.name.familyName='Smith', " + "user.emailAddress = '[email protected]', user.phoneNumber.formattedNumber = '+91 9876543210', user.assignedRoleCode = 'ADP12345'"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors
null,null,null,{"organizationKey":"7Oma78KO0d414s6rGxtXQ6nA8Pw6lIJX2SRGPaw/qhU=","targetUserKey":"c5ddc5b32e7d06e0cfb7952668551c3099","actor":{"userKey":"c5ddc5b32e7d06e0cfb7952668551c30","federationID":"d9ade5d5e25041158769987ecd5ac7e2"},"user":{"name":{"givenName":"Alex","familyName":"Smith"},"emailAddress":"[email protected]","phoneNumber":{"formattedNumber":"+91 9876543210"},"assignedRoleCode":"ADP12345"}},false
DELETE
Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "DELETE FROM payroll/v3/deduction-configurations WHERE deduction-configurations-id = '1'"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors null,null,null,null,false
Executing Prepared Statements
Using a PreparedStatement can improve performance when you need to execute a SQL statement multiple times with different parameters. Unlike a Statement object, a PreparedStatement object is provided with a SQL statement when it is created, which can then be executed with different values each time. This special type of statement is derived from the more general class, Statement.
Below are the steps outlining how to execute a prepared statement:
Creating and Executing a Prepared Statement
- Create a PreparedStatement
-
Use the
prepareStatementmethod of theConnectionclass to instantiate aPreparedStatement.Refer to Connecting with DriverManager or Connecting with DataSource for information related to establishing connections.
- Set Parameters
- Declare parameters by calling the corresponding setter method of the
PreparedStatement. - NOTE: The parameter indices start at 1.
- Execute the PreparedStatement
- Use the generic
executeorexecuteUpdatemethod of thePreparedStatement. - Retrieve Results
- Call the
getResultSetmethod of thePreparedStatementto obtain the query results, which will be returned as a ResultSet. - Iterate Over the Result Set
- Use the
nextmethod of the ResultSet to iterate through the results. To obtain column information, utilize theResultSetMetaDataclass. Instantiate aResultSetMetaDataobject by calling thegetMetaDatamethod of the ResultSet.
SELECT
Use the PreparedStatement class's generic execute method or the executeQuery method to execute SQL statements that return data.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the retrieved data.
String sql = "SELECT * FROM hr/v2/workers/leaves WHERE aoid = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setInt(1, 1); ps.execute(query); while (ps.getResultSet().next()) { for (int i = 1; i <= ps.getResultSet().getMetaData().getColumnCount(); i++) { LOGGER.info(ps.getResultSet().getMetaData().getColumnLabel(i) + "=" + ps.getResultSet().getString(i)); } } } catch (SQLException e) { LOGGER.error(e); }
INSERT
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an INSERT operation.
The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of inserted data, exceptions raised during execution, and the data affected by the insertion.
String sql = "INSERT INTO events/hr/v1/worker.leave.cancel (eventContext.associateOID, eventContext.workAssignmentID, " + "eventContext.leaveStartDate) VALUES (?, ?, ?)"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "G3EVERZ42YSP4E8T"); ps.setString(2, "85826601N"); ps.setString(3, "2020-07-15"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.error(e); }
id,errorcode,errormessage,processdata,haserrors
null,null,null,{"events":[{"data":{"eventContext":{"associateOID":"G3EVERZ42YSP4E8T","workAssignmentID":"85826601N","leaveStartDate":"2020-07-15T00:00:00+00:00"}}}]},false
UPDATE
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an UPDATE operation.
The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of updated data, exceptions raised during execution, and the data affected by the update.
String sql = "UPDATE account-linking/federated-users/actions SET organizationKey = ?, " + "targetUserKey = ?, actor.userKey = ?, actor.federationID = ?, user.name.givenName = ?, " + "user.name.familyName = ?, user.emailAddress = ?, user.phoneNumber.formattedNumber = ?, " + "user.assignedRoleCode = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "7Oma78KO0d414s6rGxtXQ6nA8Pw6lIJX2SRGPaw/qhU="); ps.setString(2, "c5ddc5b32e7d06e0cfb7952668551c3099"); ps.setString(3, "c5ddc5b32e7d06e0cfb7952668551c30"); ps.setString(4, "d9ade5d5e25041158769987ecd5ac7e2"); ps.setString(5, "Alex"); ps.setString(6, "Smith"); ps.setString(7, "[email protected]"); ps.setString(8, "+91 9876543210"); ps.setString(9, "ADP12345"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.error(e); }
id,errorcode,errormessage,processdata,haserrors
null,null,null,{"organizationKey":"7Oma78KO0d414s6rGxtXQ6nA8Pw6lIJX2SRGPaw/qhU=","targetUserKey":"c5ddc5b32e7d06e0cfb7952668551c3099","actor":{"userKey":"c5ddc5b32e7d06e0cfb7952668551c30","federationID":"d9ade5d5e25041158769987ecd5ac7e2"},"user":{"name":{"givenName":"Alex","familyName":"Smith"},"emailAddress":"[email protected]","phoneNumber":{"formattedNumber":"+91 9876543210"},"assignedRoleCode":"ADP12345"}},false
DELETE
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute a DELETE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "DELETE FROM payroll/v3/deduction-configurations WHERE deduction-configurations-id = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setInt(1, 1); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.error(e); }
id,errorcode,errormessage,processdata,haserrors null,null,null,null,false
Metadata Discovery
This section provides examples on how to retrieve table and column metadata using the getTables, getColumns, and getPrimaryKeys methods from the DatabaseMetaData interface. These are essential for discovering database structures.
Tables
The getTables method from the DatabaseMetaData interface can be used to retrieve a list of tables.
This method only retrieves tables that are not write-only.
To get a list of tables which include write-only tables, query the table system.tables.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet rs = connection.getMetaData().getTables(null, null, null, null); LOGGER.info("\r\n" + rs.toString()); } catch (SQLException e) { LOGGER.severe(e.getMessage()); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,TABLE_TYPE,REMARKS null,null,account-linking/federated-users/actions,Table,null null,null,associate-document-management/associates/documents/content,Table,null null,null,benefits/v1/associates/beneficiaries,Table,null null,null,benefits/v1/associates/benefit-coverages,Table,null null,null,benefits/v1/associates/dependents,Table,null null,null,benefits/v1/payroll-schedule-uploads,Table,null null,null,commerce/v1/health-insurance-management/prospect-interaction,Table,null null,null,commerce/v1/insurance-management/prospect-interactions,Table,null null,null,core/v1/associateAuthorization,Table,null null,null,core/v1/associates/associate-authorization,Table,null ......
The getTables method returns the following metadata columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The catalog that contains the table. |
| TABLE_SCHEM | String | The schema of the table. |
| TABLE_NAME | String | The name of the table. |
| TABLE_TYPE | String | The type of the table (e.g., TABLE or VIEW). |
| REMARKS | String | An optional description of the table. |
Columns
Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns. To narrow the results to a specific table, specify the table name using the parameter table_name.
This method returns columns only for tables that are not write-only.
To get columns for tables which are write-only, query the table system.columns.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet rs = connection.getMetaData().getColumns(null, null, "hr/v2/workers", null); LOGGER.info(rs.toString()); } catch (SQLException e) { e.printStackTrace(); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,DATA_TYPE,TYPE_NAME,COLUMN_SIZE,BUFFER_LENGTH,DECIMAL_DIGITS,NUM_PREC_RADIX,NULLABLE,REMARKS,COLUMN_DEF,SQL_DATA_TYPE,SQL_DATETIME_SUB,CHAR_OCTET_LENGTH,ORDINAL_POSITION,IS_NULLABLE,SCOPE_CATALOG,SCOPE_SCHEMA,SCOPE_TABLE,SOURCE_DATA_TYPE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE null,null,hr/v2/workers,_languageCode.codeValue,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,_languageCode.longName,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,_languageCode.shortName,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,alternateIDs,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,associateOID,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,associateProfile.associateBio,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,associateProfile.associateInterests,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,associateProfile.associateStandoutRoles,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,associateProfile.contactMeForTopics,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,hr/v2/workers,businessCommunication.emails,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR ......
The getColumns method returns the following columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The database name. |
| TABLE_SCHEM | String | The table schema. |
| TABLE_NAME | String | The table name. |
| COLUMN_NAME | String | The column name. |
| DATA_TYPE | Integer | The data type represented by a constant value from java.sql.Types. |
| TYPE_NAME | String | The data type name used by the driver. |
| COLUMN_SIZE | Integer | The length in characters of the column or the numeric precision. |
| BUFFER_LENGTH | Integer | The buffer length. |
| DECIMAL_DIGITS | Integer | The column scale or number of digits to the right of the decimal point. |
| NUM_PREC_RADIX | Integer | The radix, or base. |
| NULLABLE | Integer | Whether the column can contain null as defined by the following JDBC DatabaseMetaData constants: columnNoNulls (0) or columnNullable (1). |
| REMARKS | String | The comment or note associated with the object. |
| COLUMN_DEF | String | The default value for the column. |
| SQL_DATA_TYPE | Integer | Reserved by the specification. |
| SQL_DATETIME_SUB | Integer | Reserved by the specification. |
| CHAR_OCTET_LENGTH | Integer | The maximum length of binary and character-based columns. |
| ORDINAL_POSITION | Integer | The position of the column in the table, starting at 1. |
| IS_NULLABLE | String | Whether a null value is allowed: YES or NO. |
| SCOPE_CATALOG | String | The catalog of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SCOPE_SCHEMA | String | The schema of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SCOPE_TABLE | String | The name of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SOURCE_DATA_TYPE | Short | The source type of a distinct type or user-defined REF type (null if DATA_TYPE is neither DISTINCT nor a user-defined REF). |
| IS_AUTOINCREMENT | String | Whether the column value is assigned by ADP in fixed increments. |
| IS_GENERATEDCOLUMN | String | Whether the column is generated: YES or NO. |
| DTS_TYPE | String | Object DTS attribute type. |
Primary Keys
The getPrimaryKeys method in the DatabaseMetaData interface is used to retrieve metadata about primary keys for a given table in ADP.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet resultSet = connection.getMetaData().getPrimaryKeys(null, null, "hr/v2/workers"); LOGGER.info("\r\n" + resultSet.toString()); Assertions.assertNotNull(resultSet); } catch (SQLException e) { LOGGER.severe(e.getMessage()); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,KEY_SEQ,PK_NAME null,null,hr/v2/workers,associateOID,1,null
The getPrimaryKeys method returns the following columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The catalog name. |
| TABLE_SCHEM | String | The schema name. |
| TABLE_NAME | String | The name of the table that contains the primary key. |
| COLUMN_NAME | String | The name of the column that serves as the primary key for the table. |
| KEY_SEQ | Short | The sequence number within the primary key. |
| PK_NAME | String | The primary key name. |
Connection Settings
| Connection Setting | Type | Default Value | Description |
|---|---|---|---|
| ApiThrottleRate | Integer | 5 | The maximum number of API requests a client can make to the server within a specific time period, defined in requests per second. |
| BaseUrl | String | "" | The URL of the API endpoint for your ADP instance. |
| CacheExpirationTime | Integer | 30 | Defines the expiration time for cache. A value of 0 disables caching. |
| CertificatePassword | String | "" | The password used to access the keystore file. |
| ClientId | String | "" | The ClientId used to access ADP. |
| ClientSecret | String | "" | The ClientSecret used to access ADP. |
| ConcurrentWritingThreads | Integer | 1 | The number of threads for executing operations in parallel. A value of 0 will disable multi threading. |
| ConnectionTimeout | Integer | 30 | ConnectionTimeout is the maximum amount of time the program will wait to set up a connection to the ADP API. |
| IgnoreCertificateErrors | Boolean | false | Specifies whether to verify the certificate when connecting to ADP. If no certificate verification is required, you can set this value to 'true'. |
| IgnoreError | Boolean | false | Determines if the program continues executing SQL statements after encountering an error. |
| InstanceType | String | "Production" | ADP identity server that an authentication token is retrieved from. |
| LogFileSize | String | "10485760" | A string specifying the maximum size in bytes for a log file. |
| LogLevel | String | "INFO" | The logging level for the JDBC driver. |
| LogPath | String | "./jdbcLogs" | The directory where log files are stored. |
| MaskData | Boolean | true | Indicates whether sensitive data returned by ADP should be partially hidden or obfuscated. |
| OemKey | String | "" | The OEM license key. |
| PathToCertificate | String | "" | PathToCertificate specifies the file path where the keystore file for connecting to ADP is located. |
| ProxyMode | String | "NoProxy" | This setting configures the proxy. Allowed values are "NoProxy", "AutoDetect" and "Manual". |
| ProxyPassword | String | "" | The password to be used to authenticate to the proxy. |
| ProxyServer | String | "" | The host of the proxy server. |
| ProxyServerPort | Integer | 0 | The port of the proxy server. |
| ProxyUsername | String | "" | The username to be used to authenticate to the proxy. |
| ReadBatchSize | Integer | 100 | ReadBatchSize is used to set how many records can be read from ADP in a single call. ADP has a maximum ReadBatchSize of 100. |
| ResultPath | String | "" | The path where the execution result files are saved. |
| RetryOnIntermittentErrors | Boolean | true | The RetryOnIntermittentErrors parameter indicates whether to retry the connection when it might occasionally fail due to temporary issues. |
| RoleCode | String | "" | Identifies the ADP security role assigned to the application or user. It determines which APIs, data domains, and actions are permitted. |
| ThrottleRateUnit | String | "PerMinute" | The unit of time for limiting API requests to avoid being throttled. Valid values include, "PerSecond", "PerMinute" and "PerHour". |
| TokenUrl | String | "" | The endpoint used to request OAuth access tokens from ADP. |
| SaveResult | Boolean | false | The SaveResult parameter indicates whether to save the execution results to a file. |
| ServiceName | String | "ADP" | The ServiceName refers to the name of the service API selected by the user. |
| ServiceTimeout | Integer | 120 | The ServiceTimeout is the timeout to receive the full response from ADP API. |
| Suppress404NotFoundError | Boolean | true | When set to true, if a query results in an HTTP 404 error, a result set will still be created. When set to false, an error is logged instead and no result set is created. |
| UseAuthHeader | Boolean | false | Indicates whether the credentials to acquire access token should be sent in the Authorization header. |
| WriteBatchSize | Integer | 1 | WriteBatchSize is used to set how many records can be written to ADP in a single call. At this time, ADP does not support batch writing. As such, the value of this property should be kept at 1. |