Issue with nested filters in tabular view: 0 objects shown despite valid data

Hi everyone,

I'm currently using a nested filter in my view, and everything seems to work correctly — except in the tabular view.

Here’s what I observe:

• In the tabular interface, the table shows 0 objects.

•  However, when I click into the table, I can actually see that the instances are present. 

Below is an example of the nested filter I’m using:

Below is an example of the nested filter I’m using:
@view(
  rawFilter: {
    and: [
      {
        nested: {
          scope: ["Cement", "ScenarioContent"]
          filter: {
            equals: {
              property: ["ScenarioContent", "Type"]
              value: "PLANNED"
            }
          }
        }
      },
      {
        nested: {
          scope: ["Cement", "ScenarioContent"]
          filter: {
            equals: {
              property: ["ScenarioContent", "IsLast"]
              value: true
            }
          }
        }
      }
    ]

When checking the request, I see the following error:

{
    "errors": [
        {
            "message": "Client request(POST https://***/models/instances/aggregate) invalid: 400 Bad Request. Text: \"{\n  \"error\": {\n    \"code\": 400,\n    \"message\": \"Nested filter scope can currently only be on the following properties from the cdf_cdm/cdf_idm space: [cdf_cdm, CogniteActivity, assets], [cdf_cdm, CogniteFile, assets], [cdf_cdm, CogniteFileCategory, category], [cdf_cdm, CogniteTimeSeries, assets], [cdf_cdm, CogniteTimeSeries, unit], [cdf_cdm, CogniteEquipment, asset], [cdf_idm, CogniteMaintenanceOrder, asset], [cdf_idm, CogniteNotification, asset], [cdf_idm, CogniteOperation, asset]. Attempted scope: [sp-test_planned_realized-knowledge_graph, Cement, ScenarioContent]\"\n  }\n}\"",
            "locations": [
                {
                    "line": 3,
                    "column": 11
                }
            ],
            "path": [
                "aggregateCement"
            ],
            "extensions": {
                "classification": "DataFetchingException"
            }
        }
    ],
    "data": {
        "aggregateCement": null
    }
}

It looks like the aggregation fails due to the use of a nested scope that isn’t currently supported — which explains the 0 object count.

What confuses me is: Why the objects still appear when opening the table manually.
 

Any insights or suggestions would be greatly appreciated!