OData Client Compatibility - Revision history

Nic at 06:38, 19 June 2025

2025-06-19T06:38:20Z

← Older revision		Revision as of 01:38, 19 June 2025
Line 2:		Line 2:

	By default, new models are set 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.		By default, new models are set 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.


			= How to configure the OData Client Compatibility option ==

			To configure the OData Client Compatibility option, follow these steps.

			# Go to '''app.odatalink.com'''.
			# Click on '''Models''' on the menu in the left-hand side.
			# Find the [[Models\|model]] you want to work on and click '''View'''.
			# Select the '''Settings''' tab.
			# Click on the '''Edit Model''' button.
			# Find the '''Miscellaneous Options''' section.
			# Choose the [[OData Client Compatibility\|OData Client Compatibility]] option required.
			# Click '''Save'''.

Nic at 06:35, 19 June 2025

2025-06-19T06:35:58Z

← Older revision		Revision as of 01:35, 19 June 2025
Line 2:		Line 2:

	By default, new models are set 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.		By default, new models are set 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.


			= OData Client Compatibility Options =

			The following options are available.

Nic at 06:18, 19 June 2025

2025-06-19T06:18:05Z

← Older revision		Revision as of 01:18, 19 June 2025
Line 21:		Line 21:
	'''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		* Does not support functions.
	: ''Functions will be accessible as as entity sets instead.''		: ''Functions will be accessible as as entity sets instead.''
	* Does not support complex types		* Does not support complex types.


Line 40:		Line 40:
	'''Fabric Data Factory''' has some limitations in how it supports the OData standard. The main two limitations are that it:		'''Fabric Data Factory''' has some limitations in how it supports the OData standard. The main two limitations are that it:

	* Does not support functions		* Does not support functions.
	: ''Functions will be accessible as as entity sets instead.''		: ''Functions will be accessible as as entity sets instead.''
	* Does not support complex types		* Does not support complex types.


Line 64:		Line 64:
	'''Solver''' has some limitations in how it supports the OData standard. The main limitations are that it:		'''Solver''' has some limitations in how it supports the OData standard. The main limitations are that it:

	* Does not support functions		* Does not support functions.
	: ''Functions will be accessible as as entity sets instead.''		: ''Functions will be accessible as as entity sets instead.''

Line 72:		Line 72:
	'''SQL Server Integration Services (SSIS)''' has some limitations in how it supports the OData standard. The main limitations are that it:		'''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		* Does not support functions.
	: ''Functions will be accessible as as entity sets instead.''		: ''Functions will be accessible as as entity sets instead.''
	* Does not the Date data type		* Does not the Date data type.
	: ''Instead, dates will be returned using the DateTimeZoneOffset data type.''		: ''Instead, dates will be returned using the DateTimeZoneOffset data type.''
	* Does not support complex types		* Does not support complex types.


Line 83:		Line 83:
	'''Tableau''' has some limitations in how it supports the OData standard. The main limitations are that it:		'''Tableau''' has some limitations in how it supports the OData standard. The main limitations are that it:

	* Does not support functions		* Does not support functions.
	: ''Functions will be accessible as as entity sets instead.''		: ''Functions will be accessible as as entity sets instead.''
	* Does not support time zones		* Does not support time zones.
	: ''The time zone component of the DateTimeZoneOffset data type will be omitted.''		: ''The time zone component of the DateTimeZoneOffset data type will be omitted.''
	* Does not support complex types		* Does not support complex types.

Nic at 04:35, 19 June 2025

2025-06-19T04:35:32Z

← Older revision		Revision as of 23:35, 18 June 2025
Line 6:		Line 6:
	== (Auto Detect) ==		== (Auto Detect) ==

	The '''(Auto Detect)''' option allows OdataLink to detect the type of OData Client that is requesting data. It then uses this to adapt the OData Feed dynamically and work around limitations of specific client. This is the ~~legacy~~ behaviour in ~~how~~ OdataLink ~~worked prior to adding~~ the ~~other options~~.		The '''(Auto Detect)''' option allows OdataLink to detect the type of OData Client that is requesting data. It then uses this to adapt the OData Feed dynamically and work around limitations of specific client. This is the default behaviour in OdataLink and has been in place since the original design.

	OdataLink uses the User-Agent header of the request to identify the client as follows.		OdataLink uses the User-Agent header of the request to identify the client as follows:

	User-Agent of ''Microsoft.Data.Mashup'' indicate the request came from ''[[#Excel\|Excel]]'', ''[[#Power BI\|Power BI]]'', ''Power Query'' and ''[[#Fabric\|Fabric]]'' (and related products).		* User-Agent of ''Microsoft.Data.Mashup'' indicate the request came from ''[[#Excel\|Excel]]'', ''[[#Power BI\|Power BI]]'', ''Power Query'' and ''[[#Fabric\|Fabric]]'' (and related products).
			* User-Agent of ''azure-data-factory'' indicate the request came from ''[[#Azure Data Factory (ADF)\|Azure Data Factory (ADF)]]''.
	User-Agent of ''azure-data-factory'' indicate the request came from ''[[#Azure Data Factory (ADF)\|Azure Data Factory (ADF)]]''.		* User-Agent of ''Microsoft.Data.DataFeedClient'' indicate the request came from ''[[#SQL Server Integration Services (SSIS)\|SQL Server Integration Services (SSIS)]]''.
			* User-Agent of ''Tableau''' or ''Apache-Olingo'' indicate the request came from ''[[#Tableau\|Tableau]]''.
	User-Agent of ''Microsoft.Data.DataFeedClient'' indicate the request came from ''[[#SQL Server Integration Services (SSIS)\|SQL Server Integration Services (SSIS)]]''.		* There is no mechanism yet to detect ''[[#Solver\|Solver]]'' or ''[[#Fabric Data Factory\|Fabric Data Factory]]''.

	User-Agent of ''Tableau''' or ''Apache-Olingo'' indicate the request came from ''[[#Tableau\|Tableau]]''.

	There is no mechanism yet to detect ''[[#Solver\|Solver]]'' or ''[[#Fabric Data Factory\|Fabric Data Factory]]''.

Nic at 03:58, 19 June 2025

2025-06-19T03:58:07Z

← Older revision		Revision as of 22:58, 18 June 2025
Line 10:		Line 10:
	OdataLink uses the User-Agent header of the request to identify the client as follows.		OdataLink uses the User-Agent header of the request to identify the client as follows.

	User-Agent of ''Microsoft.Data.Mashup'' indicate the request came from ''[[#Excel\|Excel]]'', ''Power BI'', ''Power Query'' and ''Fabric'' (and related products).		User-Agent of ''Microsoft.Data.Mashup'' indicate the request came from ''[[#Excel\|Excel]]'', ''[[#Power BI\|Power BI]]'', ''Power Query'' and ''[[#Fabric\|Fabric]]'' (and related products).

	User-Agent of ''azure-data-factory'' indicate the request came from ''Azure Data Factory (ADF)''.		User-Agent of ''azure-data-factory'' indicate the request came from ''[[#Azure Data Factory (ADF)\|Azure Data Factory (ADF)]]''.

	User-Agent of ''Microsoft.Data.DataFeedClient'' indicate the request came from ''SQL Server Integration Services (SSIS)''.		User-Agent of ''Microsoft.Data.DataFeedClient'' indicate the request came from ''[[#SQL Server Integration Services (SSIS)\|SQL Server Integration Services (SSIS)]]''.

	User-Agent of ''Tableau''' or ''Apache-Olingo'' indicate the request came from ''Tableau''.		User-Agent of ''Tableau''' or ''Apache-Olingo'' indicate the request came from ''[[#Tableau\|Tableau]]''.

	There is no mechanism yet to detect ''Solver'' or ''Fabric Data Factory''.		There is no mechanism yet to detect ''[[#Solver\|Solver]]'' or ''[[#Fabric Data Factory\|Fabric Data Factory]]''.

Nic at 03:57, 19 June 2025

2025-06-19T03:57:06Z

← Older revision		Revision as of 22:57, 18 June 2025
Line 10:		Line 10:
	OdataLink uses the User-Agent header of the request to identify the client as follows.		OdataLink uses the User-Agent header of the request to identify the client as follows.

	User-Agent of ''Microsoft.Data.Mashup'' indicate the request came from ''Excel'', ''Power BI'', ''Power Query'' and ''Fabric'' (and related products).		User-Agent of ''Microsoft.Data.Mashup'' indicate the request came from ''[[#Excel\|Excel]]'', ''Power BI'', ''Power Query'' and ''Fabric'' (and related products).

	User-Agent of ''azure-data-factory'' indicate the request came from ''Azure Data Factory (ADF)''.		User-Agent of ''azure-data-factory'' indicate the request came from ''Azure Data Factory (ADF)''.

Nic at 03:56, 19 June 2025

2025-06-19T03:56:29Z

@@ Line 1: / Line 1: @@
 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.
+By default, new models are set 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) ==

Nic at 03:26, 19 June 2025

2025-06-19T03:26:23Z

← Older revision		Revision as of 22:26, 18 June 2025
Line 10:		Line 10:

	* Does not support functions		* Does not support functions
	: ''Functions will ~~get returned~~ as entity sets.''		: ''Functions will be accessible as as entity sets instead.''
	* Does not support complex types		* Does not support complex types

Line 28:		Line 28:
	'''Fabric Data Factory''' has some limitations in how it supports the OData standard. The main two limitations are that it:		'''Fabric Data Factory''' has some limitations in how it supports the OData standard. The main two limitations are that it:

	* ~~'''~~Does not support functions'''		* Does not support functions
	:* Functions will ~~get returned~~ as entity sets.		: ''Functions will be accessible as as entity sets instead.''
	* Does not support complex types		* Does not support complex types

Line 52:		Line 52:
	'''Solver''' has some limitations in how it supports the OData standard. The main limitations are that it:		'''Solver''' has some limitations in how it supports the OData standard. The main limitations are that it:

	* ~~'''~~Does not support functions'''		* Does not support functions
	:* Functions will ~~get returned~~ as entity sets.		: ''Functions will be accessible as as entity sets instead.''


Line 60:		Line 60:
	'''SQL Server Integration Services (SSIS)''' has some limitations in how it supports the OData standard. The main limitations are that it:		'''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'''		* Does not support functions
	:* Functions will ~~get returned~~ as entity sets.		: ''Functions will be accessible as as entity sets instead.''
	* ~~'''~~Does not the Date data type'''		* Does not the Date data type
	:* Instead, dates will be returned using the DateTimeZoneOffset data type.		: ''Instead, dates will be returned using the DateTimeZoneOffset data type.''
	* Does not support complex types		* Does not support complex types

Line 71:		Line 71:
	'''Tableau''' has some limitations in how it supports the OData standard. The main limitations are that it:		'''Tableau''' has some limitations in how it supports the OData standard. The main limitations are that it:

	* ~~'''~~Does not support functions'''		* Does not support functions
	:* Functions will ~~get returned~~ as entity sets.		: ''Functions will be accessible as as entity sets instead.''
	* ~~'''~~Does not support time zones'''		* Does not support time zones
	:* The time zone component of the DateTimeZoneOffset data type will be omitted.		: ''The time zone component of the DateTimeZoneOffset data type will be omitted.''
	* Does not support complex types		* Does not support complex types

Nic at 03:25, 19 June 2025

2025-06-19T03:25:14Z

← Older revision		Revision as of 22:25, 18 June 2025
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'''		* Does not support functions
	:* Functions will get returned as entity sets.		: ''Functions will get returned as entity sets.''
	* Does not support complex types		* Does not support complex types

Nic: 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 ''..."

2025-06-19T03:24:35Z

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 ''..."

New page

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.