OData V2 Protocol Reader Connector > Mappings and mapping tasks with OData V2 Protocol Reader Connector > OData V2 Protocol Reader sources in mappings
  

OData V2 Protocol Reader sources in mappings

You can use an OData V2 Protocol Reader object as a source in mappings. When you create a mapping to read data from OData V2 applications, specify the OData V2 Protocol Reader source properties.
The following table describes the source properties that you can configure in a Source transformation:
Property
Description
Connection
Name of the source connection.
Source Type
Source type.
Select Single as the source type.
Object
Source object for the mapping.
The following table describes the advanced source properties that you can configure in a Source transformation:
Property
Description
Page Size
Determines the number of rows to read in each request.
Default is 1000 rows.
Number of Rows to Skip
Sets the number of rows you can skip.
For example, you can set this property to n to skip the first n rows in a source and read from the (n+1) row.
Default is 0.
Number of Rows to Fetch
Determines the number of rows you can read from the source.
For example, specify a value of 100 to read 100 records from the source.
Specify 0 to read all records from the source.
Default is 0.
Maximum Retry Attempts
The maximum number of retry attempts made to receive the response from the OData V2 endpoint.
Default is 1.
Retry Interval in seconds
The time in seconds to wait between each retry attempt.
Default is 5 seconds.
Cache Size for Web Service Response (KB)
Sets the memory available for the web service response.
If the web service response contains many rows or columns, you might want to increase the cache size.
Default is 1024 KB.
Applicable only for hierarchical entities.
The following table describes the query options that you can configure in a Source transformation:
Property
Description
Filter
Filters the source data based on the conditions you specify.
You can configure a simple filter or an advanced filter to filter rows from the source based on a filter condition. You can improve efficiency by filtering early in the data flow.
Click Configure to configure a filter option. You can specify the following filter conditions:
  • - Not parameterized. Uses a basic filter to specify the object, field, operator, and value to select specific records. Applies only to flat entities.
  • - Advanced. Uses an advanced filter to define a complex filter condition. Applies to flat and hierarchical entities.
For more information on filters and operators, follow the conventions specified in http://www.odata.org/documentation/odata-version-2-0/uri-conventions