Is your feature request related to a problem? Please describe.
Schema Extenders expose calculated fields even when those calculated fields have been excluded from repository configuration.
This is especially noticeable for calculated fields that generate very large datasets (for example Group Sorting), although the issue is not limited to that field.
The problem does not occur during indexing.
Instead, it affects the backend because Repository configuration screens attempt to expose all calculated fields available through Schema Extenders.
This results in:
- Slower backend pages
- Unnecessary processing
- Configuration screens becoming increasingly difficult to navigate
Describe the solution you'd like
If a calculated field is disabled or excluded, it should not be exposed through Schema Extenders.
Only calculated fields that are actually available for use should be presented to the user.
Describe alternatives you've considered
- Editing the Schema Extender and excluding some fields
However that proves difficult once the list of fields has grown, because loading and selecting the fields is extremely slow.
- Removing Schema Extenders and creating fields manually.
While this avoids some of the unnecessary processing, it introduces other usability issues (see separate feature request).
Additional context
This request focuses primarily on reducing unnecessary backend processing and improving repository configuration.
Best Regards,
Nuno
Is your feature request related to a problem? Please describe.
Schema Extenders expose calculated fields even when those calculated fields have been excluded from repository configuration.
This is especially noticeable for calculated fields that generate very large datasets (for example Group Sorting), although the issue is not limited to that field.
The problem does not occur during indexing.
Instead, it affects the backend because Repository configuration screens attempt to expose all calculated fields available through Schema Extenders.
This results in:
Describe the solution you'd like
If a calculated field is disabled or excluded, it should not be exposed through Schema Extenders.
Only calculated fields that are actually available for use should be presented to the user.
Describe alternatives you've considered
However that proves difficult once the list of fields has grown, because loading and selecting the fields is extremely slow.
While this avoids some of the unnecessary processing, it introduces other usability issues (see separate feature request).
Additional context
This request focuses primarily on reducing unnecessary backend processing and improving repository configuration.
Best Regards,
Nuno