Use this guide if you're having problems getting data from the Aptem OData feed. For how specific fields are calculated and how to report on them, see OData field reference: calculations and reporting tips and the OData dictionary.
OData feed doesn't return data
Symptom: no data, or only some data, comes back from an OData feed.
Possible causes and fixes:
The OData key belongs to an admin account that has expired or been cancelled. For security, the key is blocked. Reports built with that admin's API key stop working until the key is updated. Contact Aptem Support to resolve this.
The OData key is mistyped in your query, so it's rejected. Check the key.
The admin account's group access doesn't include some learners, so their data isn't returned. Check the group access on the admin account linked to the key.
Your query doesn't name the columns. On large tables, only the first 10 columns are returned by default. Name the columns you need.
The query URL is too long. Naming many columns, such as custom fields and skills radar fields in the Users table, can make the URL very long. For security, request URLs over 8,000 characters are blocked. Split the columns into several queries so each stays under the limit.
Excel shows "We couldn't authenticate with the credentials provided. Please try again." The OData key may belong to an admin account that hasn't been activated yet (its subscription status is still 'Invited'). Once the account is activated, you can use its API key.
Power BI doesn't load Onboarding_ADET_GRModel columns from the Users table
Symptom: your Power BI report fails to load columns from the Onboarding_ADET_GRModel fields in the Users table.
Cause: the OData query URL is longer than the maximum supported length of 8,060 characters. This is most likely if your tenant has a lot of custom onboarding fields, as including them all in one query can push the URL over the limit.
Resolution: either:
Split the query. Divide the Users table query into smaller queries that each stay under the limit. Include
Idin every query, then combine the results in Power BI with a merge or join onId.Select fewer fields. Select only the fields your report needs, rather than every column.
For help building OData queries for Power BI, see Connecting your organisation's live data to Power BI via an API.
Related articles