OdataLink - User contributions [en]

Getting Started Guide

2026-05-05T03:08:29Z

Jeff:

OdataLink is a cloud-based solution developed by [https://accountingaddons.com.au Accounting Addons] to allow [[OData]] consumers such as [[Microsoft Excel]] and [[Microsoft Power BI]] to download data from [[MYOB]] and [[Xero]].

To get started with OdataLink, you will need to perform the following tasks.

# [[Registering for OdataLink|Register your user]]
#: You will need to register your email with OdataLink to get started. Registering is simple and easy.
# [[Creating an account|Create an account]] 
#: Once you have registered, you will need to create an [[Account|account]].
# [[Configuring models|Configure one or more models]] 
#: After creating your [[Account]], you will need to create a [[Models|model]] to control the security around your data.
# [[Adding data files|Add one or more data files]] 
#: The second last step will require you to add the [[Data Files|data files]] to which you want to connect.
# [[Testing OData feed URLs|Test one or more OData feed ULRs]] 
#: Lastly, you will need to test the [[OData Feeds|OData feeds]] created.

Updating my credit card details

2026-01-14T05:00:29Z

Jeff:

Credit card details can be updated from within the OdataLink app by [[Users|administrators]].

= Steps =

To update your credit card details, follow these steps.

# From the left menu, Select '''Account / Subscription'''.
# Click on the '''Update Credit Card''' button.
# Enter the new credit card details.
# Click on the '''Update''' button.

= Related Topic =

[[Managing my account]]

Changing a model's Archive Type from Developer to Live

2025-11-21T02:13:30Z

Jeff:

== Overview ==

If you find that your refresh are successful but are not picking up the latest data, it's most likely because your [[Models|Model's]] [[Archive Types|Archive Type]] is still set to '''Developer'''.

By default a [[Models|Model's]] archive type is set to '''Developer'''. This is to ensure refreshes are as quick as possible during development. When set to Developer, a refresh is only LIVE once every 8 hours.

To see the latest data, you can change the Archive Type to '''Live''' or '''Live (no archive)'''. This is recommend when you finish building your reports.

== Steps ==

The change the [[Archive Types|Archive Type]] of your model, follow these steps.

# 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 and click on the '''Edit Model''' button.
# Locate the [[Archive Types|Archive Type]] option and change it to '''Live''' or '''Live (no archive)'''.
# Click '''Save'''.

== Related ==

:[[Archive Types]]
:[[Editing a model's details]]

Archive Types

2025-03-25T12:31:56Z

Jeff:

== Overview ==

While a super strenght of OdataLink is the ability to pull live data, it can come with a performance cost. To mitigate that, Odatalink can archive data in our servers which returns data faster than from the live source. OdataLink has different options for caching depending on your situation. You can control how the archive works by changing the '''Archive Type''' option.

The possible values are:
* Live (with Archive)
* Live (no archive)
* Developer
* Static

=== Live (with Archive) ===

When the '''Archive Type''' is set to '''Live (with Archive)''', OdataLink will serve data directly from your [[Data Files|data file]].

This is the preferred option once you have finished building your reports and development is complete.

Some endpoints which cannot be edited, such as [[Xero Accounting Endpoint: JournalsAccrual|JournalsAccrual]] and [[Xero Accounting Endpoint: JournalsCash|JournalsCash]] will get cached in an encrypted archive to speed up refreshes. This only applies to endpoints whose data never changes.

It is also possible to configure a cut off data which will instruct OdataLink to archive all data prior to this date. This increases the performance when pulling large amounts of historical data. The cut off date can either be entered directly, or calculated from a number of months or days. It may also be important to configure the [[Archive Paging]] option can force paging by month or year.

=== Live (no archive) ===

When the '''Archive Type''' is set to '''Live (no archive)''', OdataLink will serve data directly from your [[Data Files|data file]].

This is option is only recommend for those that need maximum security. It does come at the cost that some endpoints will be particularly slow.

=== Developer ===

When the '''Archive Type''' is set to '''Developer''', OdataLink will be optimised for developing reports. In this mode, Live data will only be served once every 8 hours. If a refresh takes place within 8 hours of the last refresh, it will instead served cached data stored in an encrypted archive.

The benefit is that it makes refreshes faster but at the cost of not always retrieving the latest data.

This is the default when creating a model.

This is the preferred option when building reports. It should be changed to '''Live''' or '''Live (no archive)''' once development is complete.

=== Static ===

When the '''Archive Type''' is set to '''Static''', OdataLink will only query data from your [[Data Files|data file]] once.

This option is mostly used for data that never changes such as historical data.

== Related ==

[[Changing a model's Archive Type from Developer to Live]]

[[Editing a model's details]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-17T03:13:31Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected for 24 hours

While we can't force Xero to start returning calls again we can configure OdataLink to lesson its impact.

A call is as a page of data. Typically the default page size is 100 records. OdataLink has a Default Page Size field. If you increase its value from 100 to the maximum then more records will be downloaded with each call thus reducing the number of calls.

OdataLink has a caching mechanism. If you set a cut off date, future calls made to historical periods will return the cached data rather than live calls to Xero.

For instructions on how to apply these settings see [[Editing a model's details]]

= Reference =

[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-17T03:13:08Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected for 24 hours

While we can't force Xero to start returning calls again we can configure OdataLink to lesson its impact.

A call is as a page of data. Typically the default page size is 100 records. OdataLink has a Default Page Size field. If you increase its value from 100 to the maximum then more records will be downloaded with each call thus reducing the number of calls.

OdataLink has a caching mechanism. If you set a cut off date, future calls made to historical periods will return the cached data and not require live calls to Xero.

For instructions on how to apply these settings see [[Editing a model's details]]

= Reference =

[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T23:05:31Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected for 24 hours

While we can't force Xero to start returning calls again we can configure OdataLink to lesson its impact.

A call is as a page of data. Typically the default page size is 100 records. OdataLink has a Default Page Size field. If you increase its value from 100 to the maximum then more records will be downloaded with each call thus reducing the number of calls.

OdataLink has a caching mechanism. If you set a cut off date, future calls made to histical periods will return the cached data and not require live calls to Xero.

For instructions on how to apply these settings see [[Editing a model's details]]

= Reference =

[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T23:00:08Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected for 24 hours

While we can't force Xero to start returning calls again we can configure OdataLink to lesson its impact.

A call is as a page of data. Typically the default page size is 100 records. OdataLink has a Default Page Size field. If you increase its value from 100 to the maximum then more records will be downloaded with each call thus reducing the number of calls.

OdataLink has a caching mechanism. If you set a cut off date, future calls made to histical periods will return the cached data and not require live calls to Xero.

= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T23:00:00Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected for 24 hours

While we can't force Xero to start returning calls again we can configure OdataLink to lesson its impact.

A call is as a page of data. Typically the default page size is 100 records. OdataLink has a Default Page Size field. If you increase its value from 100 to the maximum then more records will be downloaded with each call thus reducing the number of calls.

OdataLink has a caching mechanism. If you set a cut off date, future calls made to histical periods will return the cached data and not require live calls to Xero

= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T22:59:02Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected for 24 hours

While we can't force Xero to start returning calls again we can configure OdataLink to lesson its impact

A call is as a page of data. Typically the default page size is 100 records. OdataLink has a Default Page Size field. If you increase its value from 100 to the maximum then more records will be downloaded with each call thus reducing the number of calls.

OdataLink has a caching mechanism. If you set a cut off date, future calls made to histical periods will return the cached data and not require live calls to Xero

= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T22:57:57Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected for 24 hours

While we can't force Xero to start returning calls again we can configure OdataLink to lesson its impact

A call is as a page of data. Typically the default page size is 100 records.

OdataLink has a Default Page Size field. If you increase its value from 100 to the maximum then more records will be downloaded with each cal

OdataLink has a caching mechanism. If you set a cut off date, future calls made to histical periods will return the cached data and not require live calls to Xero

= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T22:57:29Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected by Xero for 24 hours

While we can't force Xero to start returning calls again we can configure OdataLink to lesson its impact

A call is as a page of data. Typically the default page size is 100 records.

OdataLink has a Default Page Size field. If you increase its value from 100 to the maximum then more records will be downloaded with each cal

OdataLink has a caching mechanism. If you set a cut off date, future calls made to histical periods will return the cached data and not require live calls to Xero

= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T22:52:32Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file. This 5000 call limit is imposed by [https://developer.xero.com/documentation/api/accounting/overview Xero]. Once reached calls will be rejected by Xero for 24 hours

A call is returned as a page of data which typically defaults to 100 records per page.

One solution to reduce the number of calls is to increase the models Default Page Size to the maximum

Another solution is to cache historical data by setting a cut off date in in the Live (with Archive) archive method. When historical data is cached OdataLink can pull historical records from there rather than making live calls

= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T22:51:58Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file. This 5000 call limit is imposed by Xero [https://developer.xero.com/documentation/api/accounting/overview Xero API]. Once reached calls will be rejected by Xero for 24 hours

A call is returned as a page of data which typically defaults to 100 records per page.

One solution to reduce the number of calls is to increase the models Default Page Size to the maximum

Another solution is to cache historical data by setting a cut off date in in the Live (with Archive) archive method. When historical data is cached OdataLink can pull historical records from there rather than making live calls

= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T22:50:59Z

Jeff:

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T22:48:14Z

Jeff:

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T00:59:54Z

Jeff:

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-16T00:59:08Z

Jeff:

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T06:15:01Z

Jeff:

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T06:14:27Z

Jeff:

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T06:12:45Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file. This 5000 call limit is set by the [https://developer.xero.com/documentation/api/accounting/overview Xero API]. Once reached calls will be rejected by Xero for a 24 hours

A call is returned as a page of data which defaults to 100 records per page. One solution to reduce the number of calls is to increase the Default Page Size

Another solution is to cache historical data and only pull live data for recent periods. This can be setup in a Model by setting the Archive Type to Live (with archive) and then setting a Cut Off Date

One page of '''Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals''' contains line-item details for '''100 Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals respectively'''.

Xero allows users to retrieve Journals in batches of 100. If the journal lines exceed 5 million (100 lines x 5000 calls).

Xero has stated that it is not suitable for those businesses which have very high transaction volumes. In those cases, alternative solutions architecture involving '''Static Archived Models''' can be used to store historical data. This mechanism ensures only the latest, small volume of data, is queried from Xero.

OdataLink is also developing a '''Hybrid Archive mechanism''', which will archive data up to a particular date, or keep rolling data later than the specified period into the archive, making the queries even smaller.



= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T06:10:19Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file. This 5000 call limit is set by the [https://developer.xero.com/documentation/api/accounting/overview Xero API]. Once reached calls will be rejected by Xero for a 24 hours

A call is returned as a page of data which defaults to 100 records per page. One solution to reduce the number of calls is to increase the Default Page Size

Another solution is to cache historical data and return that rather for historical periods and only pulling live data for recent periods. This can be setup in a Model by setting the Archive Type to by using the Live (with archive) and then setting a Cut Off Date

OdataLink has implemented code-level optimizations as per the recommendations from Xero.

For each query, Xero returns line-item details for 100 endpoint items which support pagination.

A '''Query''' constitutes an '''API call sent to Xero'''. Each page sends a new API call.

One page of '''Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals''' contains line-item details for '''100 Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals respectively'''.

Xero allows users to retrieve Journals in batches of 100. If the journal lines exceed 5 million (100 lines x 5000 calls).

Xero has stated that it is not suitable for those businesses which have very high transaction volumes. In those cases, alternative solutions architecture involving '''Static Archived Models''' can be used to store historical data. This mechanism ensures only the latest, small volume of data, is queried from Xero.

OdataLink is also developing a '''Hybrid Archive mechanism''', which will archive data up to a particular date, or keep rolling data later than the specified period into the archive, making the queries even smaller.



= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T06:08:27Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file. This 5000 call limit is set by the [https://developer.xero.com/documentation/api/accounting/overview Xero API]. Once reached calls will be rejected by Xero for a 24 hours

A call is returned as a page of data which defaults to 100 records per page. One solution to reduce the number of calls is to increase the Default Page Size

Another solution is to cache historical data so that it pulls a saved copy rather than pulling live from Xero. This can be setup by using the Live (with archive)

OdataLink has implemented code-level optimizations as per the recommendations from Xero.

For each query, Xero returns line-item details for 100 endpoint items which support pagination.

A '''Query''' constitutes an '''API call sent to Xero'''. Each page sends a new API call.

One page of '''Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals''' contains line-item details for '''100 Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals respectively'''.

Xero allows users to retrieve Journals in batches of 100. If the journal lines exceed 5 million (100 lines x 5000 calls).

Xero has stated that it is not suitable for those businesses which have very high transaction volumes. In those cases, alternative solutions architecture involving '''Static Archived Models''' can be used to store historical data. This mechanism ensures only the latest, small volume of data, is queried from Xero.

OdataLink is also developing a '''Hybrid Archive mechanism''', which will archive data up to a particular date, or keep rolling data later than the specified period into the archive, making the queries even smaller.



= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T06:00:31Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

The 5000 call limit is set by the [https://developer.xero.com/documentation/api/accounting/overview Xero API].

Once the limit is reached calls will be rejected by Xero for a 24 hours

OdataLink has implemented code-level optimizations as per the recommendations from Xero.

For each query, Xero returns line-item details for 100 endpoint items which support pagination.

A '''Query''' constitutes an '''API call sent to Xero'''. Each page sends a new API call.

One page of '''Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals''' contains line-item details for '''100 Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals respectively'''.

Xero allows users to retrieve Journals in batches of 100. If the journal lines exceed 5 million (100 lines x 5000 calls).

Xero has stated that it is not suitable for those businesses which have very high transaction volumes. In those cases, alternative solutions architecture involving '''Static Archived Models''' can be used to store historical data. This mechanism ensures only the latest, small volume of data, is queried from Xero.

OdataLink is also developing a '''Hybrid Archive mechanism''', which will archive data up to a particular date, or keep rolling data later than the specified period into the archive, making the queries even smaller.



= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T05:57:50Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

The 5000 call limit is set by the [https://developer.xero.com/documentation/api/accounting/overview Xero API].

Past this point, Xero will reject  any queries sent to the affected datafile(s).

OdataLink has implemented code-level optimizations as per the recommendations from Xero.

For each query, Xero returns line-item details for 100 endpoint items which support pagination.

A '''Query''' constitutes an '''API call sent to Xero'''. Each page sends a new API call.

One page of '''Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals''' contains line-item details for '''100 Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals respectively'''.

Xero allows users to retrieve Journals in batches of 100. If the journal lines exceed 5 million (100 lines x 5000 calls), Xero will block the datafile for 24 hours.

Xero has stated that it is not suitable for those businesses which have very high transaction volumes. In those cases, alternative solutions architecture involving '''Static Archived Models''' can be used to store historical data. This mechanism ensures only the latest, small volume of data, is queried from Xero.

OdataLink is also developing a '''Hybrid Archive mechanism''', which will archive data up to a particular date, or keep rolling data later than the specified period into the archive, making the queries even smaller.



= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T05:57:23Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

The 5000 call limit is set by the Xero API [https://developer.xero.com/documentation/api/accounting/overview Xero API].

Past this point, Xero will reject  any queries sent to the affected datafile(s).

OdataLink has implemented code-level optimizations as per the recommendations from Xero.

For each query, Xero returns line-item details for 100 endpoint items which support pagination.

A '''Query''' constitutes an '''API call sent to Xero'''. Each page sends a new API call.

One page of '''Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals''' contains line-item details for '''100 Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals respectively'''.

Xero allows users to retrieve Journals in batches of 100. If the journal lines exceed 5 million (100 lines x 5000 calls), Xero will block the datafile for 24 hours.

Xero has stated that it is not suitable for those businesses which have very high transaction volumes. In those cases, alternative solutions architecture involving '''Static Archived Models''' can be used to store historical data. This mechanism ensures only the latest, small volume of data, is queried from Xero.

OdataLink is also developing a '''Hybrid Archive mechanism''', which will archive data up to a particular date, or keep rolling data later than the specified period into the archive, making the queries even smaller.



= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T05:56:56Z

Jeff:

OdataLink Error Code 9004: Xero imposed a limit of 5000 calls per day on this data file

2025-03-14T05:55:25Z

Jeff:

An '''Error 9004''' occurs when more than 5000 calls per day are made to a single Xero organisation file.

The [https://developer.xero.com/documentation/api/accounting/overview Xero API] has an internal limit of 5000 calls per day per datafile.

Past this point, Xero will reject  any queries sent to the affected datafile(s).

OdataLink has implemented code-level optimizations as per the recommendations from Xero.

For each query, Xero returns line-item details for 100 endpoint items which support pagination.

A '''Query''' constitutes an '''API call sent to Xero'''. Each page sends a new API call.

One page of '''Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals''' contains line-item details for '''100 Invoices, Credit Notes, Contacts, Bank Transactions and Manual Journals respectively'''.

Xero allows users to retrieve Journals in batches of 100. If the journal lines exceed 5 million (100 lines x 5000 calls), Xero will block the datafile for 24 hours.

Xero has stated that it is not suitable for those businesses which have very high transaction volumes. In those cases, alternative solutions architecture involving '''Static Archived Models''' can be used to store historical data. This mechanism ensures only the latest, small volume of data, is queried from Xero.

OdataLink is also developing a '''Hybrid Archive mechanism''', which will archive data up to a particular date, or keep rolling data later than the specified period into the archive, making the queries even smaller.



= Reference =
[https://developer.xero.com/documentation/best-practices/integration-health/rate-limits/#api-rate-limits Xero API Limitations]

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

OdataLink Error Code 4004: Data file is not licensed

2025-03-14T05:12:24Z

Jeff:

'''Error 4004''' will be logged if your [[Data Files|data file]] is not assigned a license in OdataLink.

This error can be resolved by [[Selecting the licensed data files|selecting the data file license]] if you have spare licenses or [[Subscribing to OdataLink|adding additional data file licenses to your subscription]].

= Related Topics =
[[OdataLink OData feed error codes]] 
[[Troubleshooting Guides]]

Creating additional OdataLink accounts

2025-03-01T10:04:02Z

Jeff:

== Overview ==

OdataLink provides the ability to create additional [[Account|accounts]]. This is useful for accounting firms and report writers to setup accounts for individual clients.

Note that you each account requires a [[Subscribing to OdataLink|separate subscription]].

== Steps ==

To create an additional account, follow these steps.

# Go to [https://app.odatalink.com app.odatalink.com].
# Click on '''Accounts''' in the left-hand side menu.
# Click the '''Create Account''' button.
# Enter the '''Name''', '''Address''' and select the '''Time Zone'''.
# Click the '''Create Account''' button.
#: When creating an [[Account|account]], OdataLink will also create a default [[Models|model]] as well as add your current [[IP Addresses|ip address]] to the list of authorised [[IP Addresses|ip addresses]].

Once the [[Account|account]] is created, you will need to [[Configuring models|configure one or more models]] and [[Adding data files|add one or more data files]].

= Related Topics =
:[[Getting Started Guide]]
:[[Managing my account]]
:[[Transfer Account Ownership]]

Creating additional OdataLink accounts

2025-03-01T10:03:13Z

Jeff:

Creating additional OdataLink accounts

2025-03-01T10:02:34Z

Jeff:

Creating additional OdataLink accounts

2025-03-01T10:02:20Z

Jeff:

Default Date Range

2025-02-23T01:34:42Z

Jeff:

[[OdataLink]] has [[Models]].

A Model is a container to store settings.

One of those settings is a '''Default Date Range'''.

This is controlled via a '''Start Date''' and an '''End Date'''.

When a model is first created it gets allocated a default '''Start Date''' and '''End Date''' within a couple of years.

The intention of these defaults is to keep intial refreshes manageable.

When downloading data via OdataLink, any date filter applied to your Power Query will take precedence over these default values. However, if you do not apply a date filter, these defaults will be used.

The '''Default Start Date''' is used to exclude transactions dated prior to this date.

The '''Default End Date''' is used to exclude transactions dated after to this date.

You can leave the values blank to not restrict the amount of data download. This will come at the cost of reduced performance.

It's important to note that if a date filter is applied to the OData feed via Excel, Power BI or another client, these defaults will not be used.

= How to change the Default Start Date and End Date =

To change the models default start date and end date, follow these steps.

# 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 [[Default Date Range]] and update the values.
#: These dates will apply when no date filters are applied via the [[OData client]].
#: You can leave the values blank to not restrict the amount of data download. This will come at the cost of reduced performance.
# Click '''Save'''.

= Related Topics =

:[[Editing a model's details|Editing models]]
:[[Models]]

OdataLink

2025-02-23T00:42:23Z

Jeff:

OdataLink is a cloud connector which provides [[Odatafeeds]] to Accounting Data Sources such as:

MYOB AccountRight

MYOB Business

Xero Accounting

Xero Practise Manager

App: https://app.odatalink.com

Website: https://odatalink.com

OdataLink

2025-02-23T00:42:04Z

Jeff:

OdataLink is a cloud connector which provides [[Odatafeeds]] to Accounting Data Sources such as:

MYOB AccountRight

MYOB Business

Xero

App: https://app.odatalink.com

Website: https://odatalink.com

OdataLink

2025-02-23T00:41:18Z

Jeff:

OdataLink is a cloud connector which provides [[Odatafeeds]] to Accounting Data Sources

App: https://app.odatalink.com

Website: https://odatalink.com

OdataLink

2025-02-23T00:40:00Z

Jeff:

OdataLink is a cloud connector which provides Odatafeeds to Accounting Data Sources

App: https://app.odatalink.com

Website: https://odatalink.com

OdataLink

2025-02-23T00:39:01Z

Jeff:

OdataLink is a cloud connector which returns data from Accounting Data Sources via an Odata Feed

App: https://app.odatalink.com

Website: https://odatalink.com

Main Page

2025-02-23T00:38:26Z

Jeff:

[[OdataLink]] is an cloud-based solution developed by [https://accountingaddons.com.au Accounting Addons] to allow [[OData]] consumers such as [[Microsoft Excel]] and [[Microsoft Power BI]] to download data from MYOB.

== What's New ==

The latest version is [[What's new in OdataLink|OdataLink v2025.2.12.249]].

== Guides ==

The following Guides should assist you in setting up and using OdataLink.

[[Getting Started Guide]] 
[[How To Guides]] 
[[Troubleshooting Guides]] 

== Links ==

App: https://app.odatalink.com

Website: https://odatalink.com

__NOTOC__

Main Page

2025-02-23T00:37:47Z

Jeff: /* Application */

OdataLink is an cloud-based solution developed by [https://accountingaddons.com.au Accounting Addons] to allow [[OData]] consumers such as [[Microsoft Excel]] and [[Microsoft Power BI]] to download data from MYOB.

== What's New ==

The latest version is [[What's new in OdataLink|OdataLink v2025.2.12.249]].

== Guides ==

The following Guides should assist you in setting up and using OdataLink.

[[Getting Started Guide]] 
[[How To Guides]] 
[[Troubleshooting Guides]] 

== Links ==

App: https://app.odatalink.com

Website: https://odatalink.com

__NOTOC__

Main Page

2025-02-23T00:37:08Z

Jeff: /* Application */

OdataLink is an cloud-based solution developed by [https://accountingaddons.com.au Accounting Addons] to allow [[OData]] consumers such as [[Microsoft Excel]] and [[Microsoft Power BI]] to download data from MYOB.

== What's New ==

The latest version is [[What's new in OdataLink|OdataLink v2025.2.12.249]].

== Guides ==

The following Guides should assist you in setting up and using OdataLink.

[[Getting Started Guide]] 
[[How To Guides]] 
[[Troubleshooting Guides]] 

== Application ==

https://odatalink.com

https://app.odatalink.com
__NOTOC__

Main Page

2025-02-23T00:36:53Z

Jeff: /* Application */

OdataLink is an cloud-based solution developed by [https://accountingaddons.com.au Accounting Addons] to allow [[OData]] consumers such as [[Microsoft Excel]] and [[Microsoft Power BI]] to download data from MYOB.

== What's New ==

The latest version is [[What's new in OdataLink|OdataLink v2025.2.12.249]].

== Guides ==

The following Guides should assist you in setting up and using OdataLink.

[[Getting Started Guide]] 
[[How To Guides]] 
[[Troubleshooting Guides]] 

== Application ==
https://odatalink.com
https://app.odatalink.com
__NOTOC__

Main Page

2025-02-23T00:36:23Z

Jeff: /* Application */

Main Page

2025-02-23T00:36:11Z

Jeff: /* Application */

Main Page

2025-02-23T00:35:54Z

Jeff:

OdataLink

2025-02-23T00:34:13Z

Jeff: Created page with "OdataLink is a cloud connector which returns data from Accounting Data sources via an Odata Feed"

OdataLink is a cloud connector which returns data from Accounting Data sources via an Odata Feed

Default Date Range

2025-02-23T00:32:47Z

Jeff:

[[OdataLink]] [[Models]] have a '''Default Date Range''' whose purpose is to filter the records to a manageable amount until filters are applied in Power Query

This is controlled via a '''Start Date''' and an '''End Date'''

When downloading data via OdataLink, any date filter applied to your Power Query will take precedence over these default values. However, if you do not apply a date filter, these defaults will be used.

The '''Default Start Date''' is used to exclude transactions dated prior to this date.

The '''Default End Date''' is used to exclude transactions dated after to this date.

You can leave the values blank to not restrict the amount of data download. This will come at the cost of reduced performance.

It's important to note that if a date filter is applied to the OData feed via Excel, Power BI or another client, these defaults will not be used.

= How to change the Default Start Date and End Date =

To change the models default start date and end date, follow these steps.

# 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 [[Default Date Range]] and update the values.
#: These dates will apply when no date filters are applied via the [[OData client]].
#: You can leave the values blank to not restrict the amount of data download. This will come at the cost of reduced performance.
# Click '''Save'''.

= Related Topics =

:[[Editing a model's details|Editing models]]
:[[Models]]

Default Date Range

2025-02-23T00:32:32Z

Jeff:

OdataLink [[Models]] have a '''Default Date Range''' whose purpose is to filter the records to a manageable amount until filters are applied in Power Query

This is controlled via a '''Start Date''' and an '''End Date'''

When downloading data via OdataLink, any date filter applied to your Power Query will take precedence over these default values. However, if you do not apply a date filter, these defaults will be used.

The '''Default Start Date''' is used to exclude transactions dated prior to this date.

The '''Default End Date''' is used to exclude transactions dated after to this date.

You can leave the values blank to not restrict the amount of data download. This will come at the cost of reduced performance.

It's important to note that if a date filter is applied to the OData feed via Excel, Power BI or another client, these defaults will not be used.

= How to change the Default Start Date and End Date =

To change the models default start date and end date, follow these steps.

# 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 [[Default Date Range]] and update the values.
#: These dates will apply when no date filters are applied via the [[OData client]].
#: You can leave the values blank to not restrict the amount of data download. This will come at the cost of reduced performance.
# Click '''Save'''.

= Related Topics =

:[[Editing a model's details|Editing models]]
:[[Models]]

Default Date Range

2025-02-23T00:31:16Z

Jeff:

A [[Model]] has a '''Default Date Range''' whose purpose is to filter the records to a manageable amount until filters are applied in Power Query

This is controlled via a '''Start Date''' and an '''End Date'''

When downloading data via OdataLink, any date filter applied to your Power Query will take precedence over these default values. However, if you do not apply a date filter, these defaults will be used.

The '''Default Start Date''' is used to exclude transactions dated prior to this date.

The '''Default End Date''' is used to exclude transactions dated after to this date.

You can leave the values blank to not restrict the amount of data download. This will come at the cost of reduced performance.

It's important to note that if a date filter is applied to the OData feed via Excel, Power BI or another client, these defaults will not be used.

= How to change the Default Start Date and End Date =

To change the models default start date and end date, follow these steps.

# 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 [[Default Date Range]] and update the values.
#: These dates will apply when no date filters are applied via the [[OData client]].
#: You can leave the values blank to not restrict the amount of data download. This will come at the cost of reduced performance.
# Click '''Save'''.

= Related Topics =

:[[Editing a model's details|Editing models]]
:[[Models]]