OdataLink Servers: Difference between revisions

(3 intermediate revisions by the same user not shown)

Line 10:

* 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.

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]].

= Related Topic =

@@ Line 10: / Line 10: @@
 * 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.
+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]].
 = Related Topic =