Fine-Tuning Data Access
Set the following properties to control how the adapter models OData APIs as a database:
• NavigationPropertiesAsViews: By default, the adapter models navigation properties as views. This enables access to related entities, even though these entities may not be linked by a foreign key in your OData service.
• SupportsExpand: If your API does not support the $expand parameter, set this property to avoid an error when NavigationPropertiesAsViews is set. If this is the case for your API, specify the base entity's primary key in the WHERE clause to access navigation properties.
• DataFormat: Set this property to JSON or XML. Otherwise, the adapter uses the default format defined by the service.
• ODataVersion: Use this to override the version detected by the adapter. This is useful if your application supports an older OData version.
• UseIdUrl: By default the adapter returns the direct URL to an entity as the primary key. By setting this to false, the entity key is returned.
• UseSimpleNames: Set this to true to return only alphanumeric characters in column names. This can help you to avoid SQL escapes and errors in SQL-based tools.
• ServerTimeZone: By default, the adapter assumes the server's Edm.DateTime values are GMT and converts them to and from the installed machine's local timezone accordingly. If the server's Edm.DateTime values are known to apply to a different timezone, then set this property to that timezone (i.e. EST).