Write, Bureaucrats, Administrators
3,301
edits
Line 32: | Line 32: | ||
=== Recommendations for MYOB === | === Recommendations for MYOB === | ||
MYOB's API is more designed to handle small volume of data. Because of this, using the 'By Year' or 'By Month' option can provide a lot of performance gains. | MYOB's API is more designed to handle small volume of data. Because of this, using the '''By Year''' or '''By Month''' option can provide a lot of performance gains. | ||
We recommend you use the 'By Year' if you have 2,000 transactions per year and require 3 or more years of data. | We recommend you use the '''By Year''' if you have 2,000 transactions per year and require 3 or more years of data. | ||
We recommend you use the 'By Month' if you have 1,000 transactions per month and require multiple months of data. | We recommend you use the '''By Month''' if you have 1,000 transactions per month and require multiple months of data. | ||
In our tests, pulling 20,000 transactions across 10 years from MYOB took: | In our tests, pulling 20,000 transactions across 10 years from MYOB took: | ||
Line 52: | Line 52: | ||
[https://developer.xero.com/documentation/api/accounting/overview Xero's API] is very well structured to handle large volumes of data. | [https://developer.xero.com/documentation/api/accounting/overview Xero's API] is very well structured to handle large volumes of data. | ||
However, Xero have introduced limits to the number of transactions that can be requested at a single time. If you need to report on more than 100,000 transactions, then using the 'By Month' or 'By Year' option is recommended. | However, Xero have introduced limits to the number of transactions that can be requested at a single time. If you need to report on more than 100,000 transactions, then using the '''By Month''' or '''By Year''' option is recommended. | ||
These options will ensure that each request stay below the 100,000 transactions cap. | These options will ensure that each request stay below the 100,000 transactions cap. |