OdataLink Servers - Revision history

Nic at 23:24, 2 August 2026

2026-08-02T23:24:20Z

← Older revision		Revision as of 18:24, 2 August 2026
Line 16:		Line 16:
	If however, you want to ensure only the server selected is used, that is where the '''Strict''' option comes in. Ticking the '''Strict''' option will instruct all other servers to reject processing your data. This option is especially important for data residency and GDPR enforcement and is strongly recommended to be enforced for those in the UK or in Europe.		If however, you want to ensure only the server selected is used, that is where the '''Strict''' option comes in. Ticking the '''Strict''' option will instruct all other servers to reject processing your data. This option is especially important for data residency and GDPR enforcement and is strongly recommended to be enforced for those in the UK or in Europe.

	In this case, in addition to the notification email, OdataLink will also log [[~~https~~:~~//help.odatalink.com/index.php?title=OdataLink_Error_Code_3007:_Model_called_using_different_server_than_configured~~\|Error 3007]].		In this case, in addition to the notification email, OdataLink will also log [[OdataLink Error Code 3007: Model called using different server than configured\|Error 3007]].

Nic at 23:24, 2 August 2026

2026-08-02T23:24:06Z

← Older revision		Revision as of 18:24, 2 August 2026
Line 15:		Line 15:

	If however, you want to ensure only the server selected is used, that is where the '''Strict''' option comes in. Ticking the '''Strict''' option will instruct all other servers to reject processing your data. This option is especially important for data residency and GDPR enforcement and is strongly recommended to be enforced for those in the UK or in Europe.		If however, you want to ensure only the server selected is used, that is where the '''Strict''' option comes in. Ticking the '''Strict''' option will instruct all other servers to reject processing your data. This option is especially important for data residency and GDPR enforcement and is strongly recommended to be enforced for those in the UK or in Europe.

			In this case, in addition to the notification email, OdataLink will also log [[https://help.odatalink.com/index.php?title=OdataLink_Error_Code_3007:_Model_called_using_different_server_than_configured\|Error 3007]].


	= Related Topic =		= Related Topic =

Nic at 23:22, 2 August 2026

2026-08-02T23:22:10Z

← Older revision		Revision as of 18:22, 2 August 2026
Line 10:		Line 10:
	* where the data will be archived.		* where the data will be archived.

	While you can choose which server to use, OdataLink does not enforce this choice unless you ~~tick the '''Strict''' option~~. So while you can choose the UK server, you could still technically use an Australian Odata Feed and everything will still work. ~~However~~, ~~ticking~~ the '''Strict''' option will instruct all other servers to reject processing your data. This option is especially important for data residency and GDPR enforcement.		While you can choose which server to use, OdataLink does not enforce this choice unless you configure it to be strict (more on this later). In other words, all servers are always available for all models at all times. This is to make it easy to transition from one server to another. So while you can choose the UK server, you could still technically use an Australian Odata Feed and everything will still work.

			If you do end up using a different server than the one configured, OdataLink will generate an email notification to inform you.

			If however, you want to ensure only the server selected is used, that is where the '''Strict''' option comes in. Ticking the '''Strict''' option will instruct all other servers to reject processing your data. This option is especially important for data residency and GDPR enforcement and is strongly recommended to be enforced for those in the UK or in Europe.

	= Related Topic =		= Related Topic =

Nic: Nic moved page OdataLink Server to OdataLink Servers without leaving a redirect

2026-08-02T23:08:17Z

Nic moved page OdataLink Server to OdataLink Servers without leaving a redirect

← Older revision	Revision as of 18:08, 2 August 2026
(No difference)

Nic: Created page with "OdataLink provides you the ability to select which server will serve your data for each model. We recommend choosing a server closer to your lo..."

2026-08-02T23:07:39Z

Created page with "OdataLink provides you the ability to select which server will serve your data for each model. We recommend choosing a server closer to your lo..."

New page

OdataLink provides you the ability to select which [[OdataLink Server|server]] will serve your data for each [[Models|model]]. We recommend choosing a server closer to your location. The Default server is currently located in Australia.

You can choose from 3 different options:
* Default
* Australia
* UK

The server you choose controls:
* where the server that processes your data is located.
* where the data will be archived.

While you can choose which server to use, OdataLink does not enforce this choice unless you tick the '''Strict''' option. So while you can choose the UK server, you could still technically use an Australian Odata Feed and everything will still work. However, ticking the '''Strict''' option will instruct all other servers to reject processing your data. This option is especially important for data residency and GDPR enforcement.

= Related Topic =

:[[Configuring models]]
:[[Select which OdataLink server to use for your model]]