OData Client Compatibility: Difference between revisions
Created page with "The OData Client Compatibility option fine tunes the Odata Feed as different client have different implementation of the OData standard. We recommend you use the option to ''..." |
No edit summary |
||
| Line 9: | Line 9: | ||
'''Azure Data Factory''' has some limitations in how it supports the OData standard. The main two limitations are that it: | '''Azure Data Factory''' has some limitations in how it supports the OData standard. The main two limitations are that it: | ||
* | * Does not support functions | ||
: ''Functions will get returned as entity sets.'' | |||
* Does not support complex types | * Does not support complex types | ||
Revision as of 22:25, 18 June 2025
The OData Client Compatibility option fine tunes the Odata Feed as different client have different implementation of the OData standard.
We recommend you use the option to (Auto Detect) as this ensures the OData Feed can be used with many different clients. There are situations where you may need to choose a specific client.
(Auto Detect)
Azure Data Factory (ADF)
Azure Data Factory has some limitations in how it supports the OData standard. The main two limitations are that it:
- Does not support functions
- Functions will get returned as entity sets.
- Does not support complex types
Excel
Excel uses Power Query under the hood to extract the data. It has the most complete implementation of the OData Standard.
Fabric
Fabric uses Power Query under the hood to extract the data. It has the most complete implementation of the OData Standard.
Fabric Data Factory
Fabric Data Factory has some limitations in how it supports the OData standard. The main two limitations are that it:
- Does not support functions
- Functions will get returned as entity sets.
- Does not support complex types
Power BI
Power BI uses Power Query under the hood to extract the data. It has the most complete implementation of the OData Standard.
Power BI Dataflows
Power BI Dataflows uses Power Query under the hood to extract the data. It has the most complete implementation of the OData Standard.
Power BI Datamarts
Power BI Datamarts uses Power Query under the hood to extract the data. It has the most complete implementation of the OData Standard.
Solver
Solver has some limitations in how it supports the OData standard. The main limitations are that it:
- Does not support functions
- Functions will get returned as entity sets.
SQL Server Integration Services (SSIS)
SQL Server Integration Services (SSIS) has some limitations in how it supports the OData standard. The main limitations are that it:
- Does not support functions
- Functions will get returned as entity sets.
- Does not the Date data type
- Instead, dates will be returned using the DateTimeZoneOffset data type.
- Does not support complex types
Tableau
Tableau has some limitations in how it supports the OData standard. The main limitations are that it:
- Does not support functions
- Functions will get returned as entity sets.
- Does not support time zones
- The time zone component of the DateTimeZoneOffset data type will be omitted.
- Does not support complex types
Other
When assigning the option of Other, OdataLink makes the assumption the client supports the complete standard and will work in the same way as Excel, Power BI and Fabric.