The property needs to exist in the domain class itself. Or even more specific: In the class the repository is typed for.
Example: If you have A extends B and P as projection for A. With a Repository extends CypherdslStatementExecutor<B>, ... it would be only possible to use the properties of B.
It cannot use A's or P's properties here because this wouldn't be valid for all possible child classes of B.
@gerrit.meier Bugger, that's not what I wanted to hear
Is there an alternative to handle the sorting? We had it working ok using cypher (using :#{orderBy(#pageable)} SKIP $skip LIMIT $limit) and were moving to DSL to clean up lots of conditional WHERE clauses which all worked fine, except for the sorting.
You could create an additional repository for the specific type which contains the property.
It is technically not prohibited to create multiple repositories for the same type.