Default Date Range: Difference between revisions
Created page with "The 'Default Start Date' and 'Default End Date' reduces the amount of transactions data downloaded via the endpoints. Leave blank to not restrict the amount of data at the co..." |
No edit summary |
||
| Line 1: | Line 1: | ||
== Overview == | |||
The '''Default Date Range''' reduces the amount of transactions data downloaded via the endpoints. | |||
''' | 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. | |||
Revision as of 22:13, 30 July 2023
Overview
The Default Date Range reduces the amount of transactions data downloaded via the endpoints.
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.