Skip to content

AB#129357 - Enable calculated fields to select from a child resource and enable sorting and filtering by those calculated fields#1230

Open
Joselgc1 wants to merge 5 commits intonextfrom
AB#129357
Open

AB#129357 - Enable calculated fields to select from a child resource and enable sorting and filtering by those calculated fields#1230
Joselgc1 wants to merge 5 commits intonextfrom
AB#129357

Conversation

@Joselgc1
Copy link
Copy Markdown
Contributor

@Joselgc1 Joselgc1 commented Apr 24, 2026

Description

Builds on top of AB#128193. This change adds a new related-child calculated field syntax. For example, {{data.teststatus(first: 1, sortField: "grade", sortOrder: "desc").grade}}. It wires it into the backend aggregation pipeline early enough for parent grids and cards to display, sort, and filter on it, preserves the newer :text display-mode calculated field behavior, and also updates the Back Office editor autocomplete so users can discover both raw/text field placeholders and reverse child relation selectors.

How to use: create a child resource and form, add a resource field pointing to the parent resource, set a unique relatedName on that field, create child records linked to parent records, then add a calculated field on the parent resource using {{data.(first: 1, sortField: "", sortOrder: "desc").}} and display it in the parent grid or card.

Useful links

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (refactor or addition to existing functionality)

Checklist:

( * == Mandatory )

  • * I have set myself as assignee of the pull request
  • * My code follows the style guidelines of this project
  • * Linting does not generate new warnings
  • * I have performed a self-review of my own code
  • * I have put the ticket for review, adding the oort-backend team to the list of reviewers
  • * I have commented my code, particularly in hard-to-understand areas
  • * I have put JSDoc comment in all required places
  • * My changes generate no new warnings
  • * I have included screenshots describing my changes if relevant
  • * I have selected labels in the Pull Request, according to the changes with code brings
  • I have made corresponding changes to the documentation ( if required )
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

AntoineRelief and others added 5 commits April 13, 2026 18:42
---------

Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net>
Co-authored-by: Jose L. Garcia <42015332+Joselgc1@users.noreply.github.com>
# [2.16.0](v2.15.0...v2.16.0) (2026-04-13)

### Bug Fixes

* Editing record with fields not defined in resource could fail ([#1217](#1217)) ([480929c](480929c)), closes [AB#125221](https://github.com/AB/issues/125221)

### Features

* add clone record action in dashboards ([#1208](#1208)) ([43559db](43559db)), closes [AB#118658](https://github.com/AB/issues/118658)
* Admins can configure auto redirection after cloning from dashboard ([#1212](#1212)) ([9de1a8c](9de1a8c)), closes [AB#118658](https://github.com/AB/issues/118658)
* Display only resources question ([#1214](#1214)) ([b9402aa](b9402aa)), closes [AB#122462](https://github.com/AB/issues/122462)
* Enable menu and account on one line, and icon-only menu items ([#1213](#1213)) ([30345c4](30345c4)), closes [AB#121668](https://github.com/AB/issues/121668)
* People picker in forms  ([#1216](#1216)) ([544b5ab](544b5ab)), closes [AB#68534](https://github.com/AB/issues/68534)
…ource and enable sorting and filtering by those calculated fields
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants