You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have two sections: Organisation Entries and Job Entries. Each Job Entry has a "organisation" relationship field that selects one organisation. In the organisation entry itself we added a many-to-many relationship field called "relatedJobs".
There is no way to filter the organisation entries to only show organisations where the relatedJobs is not empty.
Testing this with the built-in relationship field on the job entries this is working without an issue.
Steps to reproduce
create two section types
add on relationship field and one many-to-many relationship field on the entries
query for both with queryargument ":notempty:"
queryGetOrganisationsWithJobOffers {
organisationsEntries(relatedJobs: ":notempty:") {
...onEntryInterface {
title
}
...onorganisations_organisation_Entry {
relatedJobs {
title
}
}
}
allOrgEntries: organisationsEntries {
...onEntryInterface {
title
}
...onorganisations_organisation_Entry {
relatedJobs {
title
}
}
}
jobsEntries(organisation: ":notempty:") {
...onjobs_jobOffer_Entry {
titleorganisation {
title
}
}
}
}
Still looking into this, I'm not sure why, but the arguments aren't even being picked up for the field! But this may very well be related to craftcms/cms#3538
Describe the bug
We have two sections: Organisation Entries and Job Entries. Each Job Entry has a "organisation" relationship field that selects one organisation. In the organisation entry itself we added a many-to-many relationship field called "relatedJobs".
There is no way to filter the organisation entries to only show organisations where the
relatedJobs
is not empty.Testing this with the built-in relationship field on the job entries this is working without an issue.
Steps to reproduce
Result:
Craft CMS version
4.5.6.1
Plugin version
3.0.4
Multi-site?
No
Additional context
No response
The text was updated successfully, but these errors were encountered: