Troubleshooting
400 Bad Request
- "BI Endpoints application is not activated" — no subscription is activated. In Business Central, search for BI Endpoints Setup and create the subscription. See BI Endpoints Setup.
- "This endpoint requires a Premium subscription" — the endpoint is not on
the Free tier. Each endpoint's tier is on the category pages and in
biEndpoints. - Otherwise the query itself is invalid. Read
error.message; check quotes around text values and that the field exists withproperties.
401 Unauthorized
- Verify the app registration is enabled on Microsoft Entra Applications in Business Central.
- Check that the client secret has not expired.
- Ensure admin consent has been granted for the API permissions.
- Verify that you send the bearer token with the request, and that it has not expired. See Authentication.
403 Forbidden
- Verify the appropriate permission sets are assigned in Business Central — DTW BI ENDPOINTS, plus read access to the source table for a custom endpoint. See Permissions.
- Check that the company ID in the URL is correct.
404 Not Found
- Verify the extension is installed and enabled.
- Check the endpoint name and the URL format. Entity set names are
camelCase, for example
glEntries. See Construction of the URL. - Ensure you are using the correct environment name.
429 Too Many Requests
- Implement retry logic with exponential backoff.
- Spread requests over time for large data extractions.
- Limit the number of records returned per request with the header
Prefer: odata.maxpagesize=500.
Timeouts on large tables
Request smaller pages with Prefer: odata.maxpagesize=5000, filter to what
changed with systemModifiedAt, and $select only the fields you need. See
Querying the endpoints and
Incremental loads.
Still stuck?
Email support@datawareness.com with the
request URL (without the token), the full error message and the version from
applicationInfo.