A reference of the errors and dead ends users hit most often, with the symptom, the cause, and what to do about it.
Save validation errors #
“Name is required” #
You pressed Save with the Name field empty. The connector reports the missing required field in a blocking message box.
Fix: dismiss the message, fill in a name, save again.
“At least one SAP service is required” #
You saved a data source with a name but no SAP services attached.
Fix: dismiss the message, select Add Service, pick a service from the catalog, then save again. See Create a data source.
“Cannot save: one or more filter expressions are invalid” #
An OData filter expression somewhere on the data source fails to parse. The entity with the broken filter is highlighted in the form, and the editor under it shows an inline error pointing to the first parse failure.
Fix: open the broken entity, switch to the OData filter editor if you’re in the basic one, correct the expression, and save again. See Filter rows.
Power BI authentication errors #
401 Unauthorized in Power BI Desktop or Power BI service #
Power BI failed to authenticate against the connector. Causes:
- The personal access token used was revoked or auto-expired. Look for it on Access Tokens with status Revoked or Expired.
- The user name in Power BI doesn’t match the connector account that minted the token.
- Power BI cached a stale token after you minted a new one.
Fix: mint a fresh token in the connector. In Power BI Desktop, update credentials under File → Options and settings → Data source settings. In the Power BI service, update credentials on the dataset under Settings → Data source credentials.
403 Forbidden after the data source worked before #
Your token authenticates, but the connector refuses to return data for this data source. Two common causes:
- The owner removed you from the sharing list. See See what’s been shared with you.
- The owner deleted the data source. The URL still resolves but the row is gone.
Fix: ask the owner. If they intentionally removed you, this is the expected outcome.
SAP catalog and metadata #
The SAP service catalog is empty #
The Add SAP Service dialog returns no rows or fewer rows than expected.
- The destination configured in BTP is not reachable. Ask your administrator to test the destination from BTP cockpit.
- The technical user behind the destination has no PFCG role giving it access to the OData services. See the technical guide for the on-premise side.
- The catalog response cached an earlier failure. Try again in a minute or clear the cache from the BTP side.
“Loading service metadata” takes more than a minute #
First-load metadata fetches are slow for large OData services. The SAP back end can take 30–90 seconds to produce the metadata document. Wait it out. Subsequent loads are cached and much faster.
If the indicator never disappears, the SAP back end is likely returning an error the connector swallowed silently. Check Export History for the timing — if you see a 5xx around the time you triggered the load, that’s the actual failure.
Trial and quota #
“Trial plan: you have reached the maximum of 2 data sources” #
Your tenant is on the trial plan and already has 2 data sources. The Create and Clone actions are blocked.
Fix: delete a data source to free a slot, or upgrade in the BTP cockpit. See Subscription plans and trial limits.
Still stuck? #
Open the in-app help dialog (question-mark icon in the toolbar) and follow the Support section. The link there points to the right channel for your tenant.
