View Categories

Create a Data Source

4 min read

Table of Contents

A data source is the read-only bridge between your SAP system and Power BI. It bundles one or more SAP OData services, a selection of entities and fields, and optional row filters into a single endpoint URL. After it has been saved, Power BI Desktop can load the data source like any other OData feed.

i

Before you start

  • You can sign in to Power BI Connector for SAP. If you can’t, ask an administrator to grant you the user role.
  • An SAP destination is configured by an administrator. The destination is what gives the connector access to SAP services; without it the service catalog is empty. The back-end side of this setup is described in SAP On-Premise Setup for OData and Access.

1. Open the data sources list #

Sign in to the connector. The Data Sources page opens by default. Select Create in the top-right corner of the list toolbar.

01 list empty

2. Open the Create data source form #

The form opens with three text fields and a placeholder for SAP services. A red asterisk marks required fields.

02 create empty form

  1. Name (required). A short, unique label that identifies the data source in the list. Up to 255 characters.
  2. Description (optional). Free-form text that explains what the data source contains. Visible in the list. Up to 255 characters.
  3. Shared with (optional). Email addresses of co-workers who should be able to read the data source. Type an address and press Enter to add it as a token. Recipients get read-only access to the data source and to its OData URL.
  4. Add Service. Opens the SAP service catalog.

3. Add an SAP service #

Select Add Service. The Add SAP Service dialog opens.

03 add service dialog

  1. Search. Type at least part of a service name and wait for results. The catalog is fetched from your SAP destination on the first call and cached afterwards.
  2. Pick a service. Select a row to add the service to the data source. Services that have already been added show Already added and can’t be picked again. To attach more services, repeat this step.

Loading metadata for a large OData service can take up to a minute on the first request. Wait for the Loading service metadata indicator to disappear before continuing.

4. Select entities and fields #

When metadata has loaded, the service appears as an expandable panel on the form.

04 service entity expanded

  1. Service panel. Lists every entity the SAP service exposes. Expand it to see them.
  2. Entity. Each entity becomes its own expandable panel. Select the header checkbox to add every field in the entity, or expand the panel to pick fields individually.
  3. Filter. Optional row-level filter applied at query time. See step 5.

Each field shows a display label and, in parentheses, the raw OData property name and type. Select a field’s checkbox to include it in the data source.

05 fields selected

5. (Optional) Filter rows in an entity #

Open Filter inside an entity. Two editor modes are available:

  • Basic — a guided builder with field, operator, and value pickers, plus AND/OR grouping. Best for straightforward conditions.
  • OData — a free-text editor for OData v4 $filter expressions. Use it for conditions the basic editor cannot represent.
06 filter basic
07 filter odata

The OData editor validates expressions as you type. Save is blocked while any filter is invalid; the message under the editor explains the first parse error.

Supported in OData mode

  • Comparisons: eq, ne, gt, ge, lt, le
  • String functions: contains, startswith, endswith
  • Grouping with parentheses
  • Combining with and / or

Not supported: null literals, arithmetic, not, in, has, and lambda operators.

6. (Optional) Preview the result #

Use the buttons in the footer to verify the selection before you save.

  • Preview returns a sample of the rows for the current selection and filters.
  • Preview ERD opens an entity-relationship diagram of the entities you have added. Useful when more than one entity is combined.

Preview doesn’t persist anything; it only queries the back end.

7. Save #

Select Save. The data source is created and you return to the Data Sources page. The new row’s URL column shows the unique OData endpoint to use in Power BI Desktop.

08 footer save

If saving fails

  • Name is required — the Name field is empty.
  • At least one SAP service is required — no service has been added.
  • Cannot save: one or more filter expressions are invalid — fix the expression in the highlighted entity and try again.

What’s next? #

  • Connect Power BI — Paste the data source’s OData URL into Power BI Desktop’s OData feed connector.
  • Share a data source — Grant read access to other users without giving them ownership.
  • Edit a data source — Adjust selection, filters, or sharing after creation.