Thank you for confirming that this is not currently possible in ExpressionEngine 7.
We would like to formally submit a feature request regarding ordering options in the Relationship field.
At present, the “Order By” setting is limited to Title and Entry Date. For many real-world use cases, this does not provide sufficient flexibility. We would like to request consideration for the following enhancements:
Support for additional “Order By” options within Relationship fields, including the ability to sort by custom fields (such as a numeric priority field or custom date field).
The ability to sort by core fields such as url_title.
Alternatively, the introduction of a documented hook or extension point that allows developers to modify the ORDER BY clause of the relationship query.
Our use case specifically requires more granular control over how related entries are ordered, particularly for editorial workflows where ordering is driven by priority values or non-standard dates rather than Title or Entry Date.
We understand there may be architectural considerations, especially when custom fields span multiple channels. However, even a developer-level override would provide meaningful flexibility without requiring UI-level complexity.
We appreciate your consideration of this enhancement and would be happy to provide additional context if helpful.
Thank you for confirming that this is not currently possible in ExpressionEngine 7.
We would like to formally submit a feature request regarding ordering options in the Relationship field.
At present, the “Order By” setting is limited to Title and Entry Date. For many real-world use cases, this does not provide sufficient flexibility. We would like to request consideration for the following enhancements:
Support for additional “Order By” options within Relationship fields, including the ability to sort by custom fields (such as a numeric priority field or custom date field).
The ability to sort by core fields such as url_title.
Alternatively, the introduction of a documented hook or extension point that allows developers to modify the ORDER BY clause of the relationship query.
Our use case specifically requires more granular control over how related entries are ordered, particularly for editorial workflows where ordering is driven by priority values or non-standard dates rather than Title or Entry Date.
We understand there may be architectural considerations, especially when custom fields span multiple channels. However, even a developer-level override would provide meaningful flexibility without requiring UI-level complexity.
We appreciate your consideration of this enhancement and would be happy to provide additional context if helpful.