OData restrictions
To protect system performance, security, and fair usage across all customers, BUZ applies specific restrictions to OData feeds. These limits stop large, unfiltered queries from slowing down your system or affecting other users. This page explains the restrictions in place and how to work within them.
Why restrictions exist
Section titled “Why restrictions exist”OData gives you real-time-style access to your BUZ data through tools like Excel and Power BI. Left unrestricted, very large queries can:
- Slow down your own reports and system.
- Create unnecessary load on the server.
- Interfere with data processing.
- Lead to timeouts or failed queries.
To keep things running smoothly, BUZ applies filtering and query controls.
Types of OData restrictions
Section titled “Types of OData restrictions”Limits differ depending on whether you query during or outside business hours.
Not every organisation has limits applied. Where they are, they are set for your organisation and apply only during your own working hours. If you are unsure what applies to you, contact BUZ Support.
During business hours
Section titled “During business hours”| Restriction | Detail |
|---|---|
| Date range | Reports are restricted to 12 months. |
| Date filter required | Every report must apply a date-range filter (for example OrderDate or CreatedDate), including a Date From and Date To. |
| Rows per batch | Large reports are returned in batches, sized to the limit set for your organisation. You still get every row — Excel and Power BI ask for the next batch automatically until the report is complete. |
| Blocked queries | Unfiltered or inefficient queries (for example, requesting all records with no filter) are automatically blocked. |
Outside business hours
Section titled “Outside business hours”| Restriction | Detail |
|---|---|
| Date range | No limit. |
| Date filter required | Every report must still apply a date-range filter, including a Date From and Date To. |
| Rows per batch | No batching — the whole report is returned at once. |
| Blocked queries | Unfiltered or inefficient queries are automatically blocked. |
What happens if you hit a restriction?
Section titled “What happens if you hit a restriction?”- Missing date filter, or a range longer than 12 months — the report is refused and you’ll see an error. Add or narrow the date filter and run it again.
- A report larger than one batch — nothing is refused and nothing is lost. It arrives in batches and takes a little longer to finish.
Best practices
Section titled “Best practices”To avoid hitting restrictions and to improve performance:
- Always apply a date filter.
- Fetch only the fields you need.
- Pre-filter your data wherever possible (for example, by status or branch).
- Test queries on smaller datasets before scaling up.
For step-by-step setup, see Excel reporting using OData or OData reporting on a Mac.