[Bug]: Using filter on multi-level nested objects causes runtime error (GraphQL, CosmosDB)

What happened?

Simplified version of the schema looks like:

type EmployeeAggregate @model {
  id: ID
  Payload: Payload
}

type Payload {
  Id: ID
  Jobs: [Job]
}

type Job {
  Fte: Int
}

Config looks like:

"entities": {
    "EmployeeAggregate": {
      "source": "employeeAggregates_v2",
      "permissions": [
        {
          "role": "anonymous",
          "actions": [
            "*"
          ]
        }
      ]
    },
    "Payload": {
      "source": "employeeAggregates_v2",
      "permissions": [
        {
          "role": "anonymous",
          "actions": [
            "*"
          ]
        }
      ]
    },
    "Job": {
      "source": "employeeAggregates_v2",
      "graphql": {
        "type": {
          "singular": "Job",
          "plural": "Jobs"
        }
      }
	}
}

Query looks like:

    employeeAggregates(first: 10, filter: {Payload: {Jobs: {Fte: {eq: 1}}}}) {
        items {
            Payload {
                Id
            }
        }
    }
}

Error looks like:

{
    "errors": [
        {
            "message": "GraphQL type doesn't match any entity name or singular type in the runtime config.",
            "extensions": {
                "code": "BadRequest"
            }
        }
    ]
}

Note Filtering on first-level nested object (e.g. “Payload”) works. However, filtering second-level nested objects (e.g. “Jobs”) fails.

Version

0.7.6

What database are you using?

CosmosDB NoSQL

What hosting model are you using?

Static Web Apps (SWA)

Which API approach are you accessing DAB through?

GraphQL

Relevant log output

{
    "errors": [
        {
            "message": "GraphQL type doesn't match any entity name or singular type in the runtime config.",
            "extensions": {
                "code": "BadRequest"
            }
        }
    ]
}

Code of Conduct

• I agree to follow this project’s Code of Conduct

[sajeetharan]

@Isayaa This limitation extends to queries as well. We will assess and provide you with an update regarding the ETA for the fix.

[Isayaa]

@tarazou9 thanks for your answer. Some feedback and question:

• Your PR only mentions a limitation with mutations. However, in this case we just need to have the queries working. Is it a mistake in the PR description?
• Do you have any plan in fixing the limitation (for queries)? It’s an important info for us because it would mean we need to consider another technology to expose our existing CosmosDB that contains nested objects up to 3 level.