Rules and Guidelines for Using OData Consumer Connector
Rules and Guidelines for Using OData Consumer Connector
The following rules and guidelines apply when you use OData Consumer Connector:
The OData Consumer Connector supports the OData V4 protocol for simple entity types, but does not support complex types, open types, derivatives, relationship properties, navigation properties, singleton, and collections.
The OData Consumer connection supports only basic authorization.
When you configure a transformation in a task, you cannot use OData logical operators in transformations.
When you apply filters to read OData Consumer data that contains the DateTimeOffset field, you must use the following format:
For normal filters, specify the
DateTimeOffset equals 1970-01-01 08:12:27
format.
For advanced filters, specify the
DateTimeOffset eq 1970-01-01T08:12:27.000Z
format.
When you apply advanced filters to read OData Consumer data and specify a column name, the table name gets prepended to the column name and the filter does not get applied. Remove the table name and then specify the filter condition.
You can read, write, or preview OData Consumer data using the Timeofday field. If the OData server does not return the date, the date shows up as 1970-01-01.
You cannot use an OData Consumer connection to specify lookups in synchronization tasks, mappings, and mapping tasks.
If you want to specify only the truststore file name and password to connect to the OData Consumer application using SSL, do not keep the keystore file name and passwords fields blank. Specify the truststore file name and password in the keystore file name and password fields.