Add support for explicitly choosing an aggregator in Query Builder

[grantfitzsimmons]

The feature request "Add support for explicitly choosing a formatter in Query Builder" (#1959) did not cover choosing an aggregator.

@maxpatiiuk said in this comment that at one point it was

Fixed both for formatters and aggregators

This code conditionally renders a QueryFieldFormatter component based on the fieldMeta properties. If fieldType is either 'formatter' or 'aggregator' and tableName is a string, it displays the QueryFieldFormatter component with specific props like formatter, tableName, type, and onChange.

Theoretically it already should support this for aggregators, but either due to a bug in the existing code or an oversight, this is not functional at the moment.

This indicates to me that the intention was to have this existing feature request cover aggregators as well (as the logic should be nearly identical).

Expected Behavior

• When adding an (aggregated) line to a query, the user should be able to explicitly define which aggregation to use
• The gear icon should only appear to the right of the (aggregated) line if there are two or more aggregators configured for that table
• This should behave identically to how the user defines an explicit formatter (added back in Add support for explicitly choose a formatter in QB #4615)

This is arguably a bug in the existing implementation, but because it is not functional and outside the scope of the previous issue, I have opened this one. I do see this as one and the same as #1959 at its core.

[CarolineDenis]

specify7/specifyweb/frontend/js_src/lib/components/QueryBuilder/Line.tsx

Line 140 in 3fcba9b

const dataModelField = isFormatted

const dataModelField = isFormatted
        ? undefined
        : getTable(tableName ?? '')?.getField(fieldName);

specify7/specifyweb/frontend/js_src/lib/components/QueryBuilder/Line.tsx

Line 168 in 3fcba9b

fieldType =

else if (isMapped)
        fieldType =
          dataModelField?.isRelationship && relationshipIsToMany(dataModelField)
            ? 'aggregator'
            : 'formatter';

In the case where we add a Formatted resource or Aggregated resource, isFormatted will be true. (isFormatted checks if the field starts with '-', in this case we have '-formatted' and '-aggregated')

Therefore, dataModelField will be undefined in both cases. ==> isFormatted === true ? undefined

Since dataModelField is always undefined, dataModelField?.isRelationship or relationshipIsToMany(dataModelField) will also always be undefined,

In conclusion the value of fieldType will always be 'formatted' with this code

[CarolineDenis]

Start of a fixe in ddebb7a

The aggregator list appear and the value set for the aggregator is correct but the change doesn't show in the query result table

[acwhite211]

This is fixed now on the back-end in #4646
#4646 (comment)

The problem seems to be that the back-end is ignoring the formatter name in the request. It is just getting the aggragator and then getting the formatter that the aggregator is pointing to. I changed the code so that it takes into account the 'formatter name' that is passed in the query builder request.