Search of CMD field in an overview creates wrong query

Hi,

if i have an overview model based on a CDM data model.
Model: Person < - > Adress

In the overview it’s possible to filter for all field e.g. add a filter for the city field of the address model.

For this this query is executed:

{
  "jsonrpc": "2.0",
  "method": "QUERY",
  "id": "OverviewEngineDataProvider-12",
  "params": {
    "query": {
      "projectionName": "cdd",
      "targetDocumentModel": "pwitha",
      "paging": {
        "pageSize": 10,
        "pageNumber": 0
      },
      "constraint": {
        "operator": "exact_match",
        "field": "/ptoA/adress/city",
        "value": "Hamburg",
        "caseSensitive": true
      }
    }
  }
}

But this looks to be wrong there should be a has operator used to follow the links?

Is this a bug?
Has this been dropped for A12 2025?
Will this be implemented again?

Cheers
Julian

If this needs to be custom build let us know.

But i fear the complexity of a recursive constrain builder and don’t see this in custom code.

Hey @julian-typed-spruce ,

With the new Query API introduced in 2025.06, the old search/filter behavior on CDDs (based on a separate index created sync/async on save) is no longer available.

Although it is documented in the DS documentation, it is clearly a bug, that you can still model this in the Overview Model Editor. We are working on a fix there.

The good news: With 2026.06, we introduce new modeling capabilities to Filter along Relationships (whether in CDMs or starting from “regular” documents). With this feature you will be able to model Filters on linked documents with predefined, complex Filter Definitions or with user inputs.

Let me know, if upgrading to 2026.06 is not an option for your project or if you want to filter/search on Fields that are computed by a Computation in the CDM.

Cheers Felix

Hi,

we have a custom implementation now. It works by modifying the created query so the the correct “has” constrains are added.

Works okay for now.