Metrica
Metrica
✕
  • Home
  • Products
    • Power BI Connector for Salesforce
    • Power BI Connector for SAP
  • Resources
    • Blog
    • Trust Center
Explore Products

Home - Metrica Docs - Filter Rows

Getting Started

  • Welcome
  • Installation Guide
  • Explore Power BI Connector for SAP
  • Quickstart — from Zero to a Power BI Report
  • Installation Guide: Multi-Tenant
  • On-Premise SAP Configuration

Admin Guide

  • Configure the Token Expiry Policy
  • Application Permissions Setup

User Guide

  • Create a Data Source
  • Create an Access Token
  • Connect Power BI Desktop
  • Manage Access Tokens
  • Edit a Data Source
  • Filter Rows
  • Share a Data Source
  • Schedule Refresh in Power BI Service
  • Preview Data
  • Preview the ERD
  • See What’s Been Shared with You
  • Customize the Data Source Page
  • View Activity History
  • View Export History
  • Combine Multiple SAP Services
  • Use Parametrized OData Entities
  • Explore Data Relationships
  • Browse and Search the Data Sources List
  • Transfer Data Source Ownership
  • Clone a Data Source
  • Delete a Data Source
  • Child Entities and Addressability

FAQ & Troubleshooting

  • Troubleshooting
  • Why do my SAP dates show up as text in Power BI?
  • Why do I get 401 from the Power BI service after a successful Desktop load?
  • Why is the SAP catalog showing fewer services than I expect?
  • What happens if I lose a token?
  • Will the recipient see my access token if I share with them?
  • Can a tenant admin see the value of my access tokens?
  • How many data sources can I create?
  • Why is the URL of every data source different?
  • How is Preview ERD different from Data Relationships?
  • Why does the connector limit me to 5 active tokens?
  • What happens to a shared data source if I leave the company?
  • Why does the Basic filter editor sometimes disable itself?
  • Can I share a data source with a user from a different tenant?
  • Why doesn’t the connector cache SAP data?
  • What happens if a service is removed from the destination after I’ve built a data source on it?
  • Can I change the data source URL after creation?
  • Do I have to fill every parameter on a parametrized entity?
  • Can I use the OData URL outside Power BI?

Support

  • Contact Support
  • Pricing and Licensing
  • Subscription Plans and Trial Limits
View Categories
  • Metrica Docs
  • Power BI Connector for SAP Documentation
  • User Guide

Filter Rows

2 min read

A filter limits which rows an entity returns to Power BI. Filters are applied at query time on the SAP side, so unfiltered rows never travel over the wire. Each entity gets its own filter; filters on different entities are independent.

Open the filter editor #

Inside an entity on the create or edit form, expand Filter.

filter 01 basic empty

The editor has two modes:

  • Basic — a visual 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 this for conditions the basic editor cannot represent.

Build a filter in the basic editor #

Select Add condition. Pick a field, an operator, and a value. Repeat for additional conditions; they combine with the connector shown above the list (AND/OR), which you can switch with one click.

filter 02 basic one condition

Use Add group to nest conditions with a different connector — for example, A AND (B OR C).

The operator list adapts to the field’s type: comparisons for numbers and dates, plus contains, starts with, and ends with for strings.

Switch to the OData editor #

Select OData to type the expression as raw OData v4 text. Anything you built in the basic editor is translated and pre-filled.

filter 03 odata valid

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 (any/all).

One-way switch from advanced expressions #

If the OData expression uses constructs the basic editor cannot represent (for instance, a deeply nested expression or an unsupported operator), the Basic button is disabled. Its tooltip explains the reason. Simplify the expression in the OData editor to re-enable the basic mode.

Validation #

The OData editor checks every expression as you type. An invalid expression shows an inline error under the textarea, and Save is blocked while at least one filter on the data source is invalid.

filter 04 odata error

The error message points to the first parse failure (location, unexpected character, missing token). Fix the expression and the error clears automatically.

Related #

  • Create a data source
  • Preview data
Updated on May 19, 2026

Share This Article :

  • Facebook
  • X
  • LinkedIn
  • Pinterest
Edit a Data SourceShare a Data Source
Table of Contents
  • Open the filter editor
  • Build a filter in the basic editor
  • Switch to the OData editor
  • One-way switch from advanced expressions
  • Validation
  • Related
Metrica
Explore Products
Products
  • Power BI Connector for Salesforce
  • Power BI Connector for SAP
Resources
  • Blog
  • Trust Center

Metrica Software builds enterprise data connectors that provide analytics platforms with direct access to complex business systems such as SAP and Salesforce.

The focus is on predictable behavior, controlled access, and long-term operation in production environments.

© 2026. All rights reserved.

Privacy Policy

Terms of Use

    Book a Demo







    Secure & private form

    1-2 min

    ×

      Contact Sales








      Secure & private form

      1-2 min

      ×