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

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

Limits differ depending on whether you query during or outside business hours.

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.
Row limit	Reports are limited to the top 5,000 rows — roughly 5,000 appointments or 5,000 individual jobs.
Blocked queries	Unfiltered or inefficient queries (for example, requesting all records with no filter) are automatically blocked.
$skip filter	$skip filters are blocked.

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.
Row limit	No limit.
Blocked queries	Unfiltered or inefficient queries are automatically blocked.
$skip filter	$skip filters are blocked.

Note

OData reports are not real-time. Data is synchronised from BUZ periodically and can take up to 24 hours to appear in your OData reports after being created or updated.

Caution

Restrictions may change over time. Check this page regularly for the current limits.

What happens if you hit a restriction?

• You’ll receive an HTTP 400 or 500 error response.
• The data may be truncated, or the request may fail entirely.

Best practices

To avoid hitting restrictions and to improve performance:

• Always apply a date filter.
• Don’t use $skip filters.
• 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.