Most ODATA metadata feeds include standardize column data type definitions for the endpoints. Currently, TimeXtender ignores this and interprets datatypes itself based on the first page of actual data, or the entire set of data when exhaustive metadata scan is enabled.
This is unnecessary and leads to datatype errors and/or extremely long import-metadata times. TimeXtender should just interpret the metadata from the ODATA feed, or at the least, allow us to define datatypes for ingestion ourselves in ODATA/REST.
Example metadata ODATA feed:
Example TDI interpretation:
