Is your feature request related to a problem? Please describe.
When Schema Extenders are not being used and fields are created manually, calculated fields are still presented in the Field Source dropdown.
These calculated fields are not actually available because they are never generated.
This creates two usability problems:
- The dropdown contains an unnecessarily large number of entries.
- Users are presented with options that cannot actually be used.
The interface gives the impression that these calculated fields are available when they are not.
Describe the solution you'd like
When calculated fields are unavailable, they should not appear in the Field Source selection.
Additionally, consider displaying a small informational message explaining that certain calculated fields are intentionally hidden because they are unavailable under the current repository configuration.
This helps users understand why they cannot find those fields.
Describe alternatives you've considered
Keeping the current behavior.
Although search is available, users must still navigate extremely large dropdown lists containing many unusable options.
Additional context
This request complements the Schema Extender improvements but addresses a separate usability problem.
Screenshots
- No schema extender configured
- Skipping multiple fields, specifically the sorting
- Still show up and makes the search extremely slow and misleading (as I can pick a calculated field that may be skipped - meaning not available)
Best Regards,
Nuno Aguiar
Is your feature request related to a problem? Please describe.
When Schema Extenders are not being used and fields are created manually, calculated fields are still presented in the Field Source dropdown.
These calculated fields are not actually available because they are never generated.
This creates two usability problems:
The interface gives the impression that these calculated fields are available when they are not.
Describe the solution you'd like
When calculated fields are unavailable, they should not appear in the Field Source selection.
Additionally, consider displaying a small informational message explaining that certain calculated fields are intentionally hidden because they are unavailable under the current repository configuration.
This helps users understand why they cannot find those fields.
Describe alternatives you've considered
Keeping the current behavior.
Although search is available, users must still navigate extremely large dropdown lists containing many unusable options.
Additional context
This request complements the Schema Extender improvements but addresses a separate usability problem.
Screenshots
Best Regards,
Nuno Aguiar