---
title: "Important: A partner role sorts its partnerships on its own"
manual: "Academic Partners"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-partners:important-partner-role-sorts-its-partnerships@main"
source: "Changelog/3.0/Important-PartnerRoleSortsItsPartnerships.rst"
rendered: "2026-10-08T23:49:53+00:00"
---

# Important: A partner role sorts its partnerships on its own {#important-partner-role-sorts-its-partnerships}

## Description {#description}

A partnership is an inline child of two records at once: of its partner page,
and of the role it is filled with. Both relations wrote the same `sorting`
column, because the role relation declared no `foreign_sortby` of its own
and TYPO3 then falls back to the manual sort field of the table.

`RelationHandler::writeForeignField()` numbers the children of the record
being saved 1..n in the order of its form, so saving a role renumbered its
partnerships *across every partner page that owns one of them*. An editor who
had arranged the partnerships on a partner page saw that arrangement replaced
by the order of an unrelated role form - in the backend and, since partnership
lists and teasers render in `sorting` order, in the frontend as well.

The role relation now has a sort column of its own,
`tx_academicpartners_domain_model_partnership.role_sorting`, and orders by
it. The partner page keeps `sorting`, so nothing that renders today
changes.

## Impact {#impact}

Saving a role no longer changes the order of any partner page, and a partner
page no longer changes the order a role form shows. Both arrangements are kept
side by side.

A partnership that joins a role afterwards is appended to the end of that
role's list, whether it was created in the role form, given its role in the
partnership form on a partner page, copied or localized. Changing the role
moves it to the end of the new one; clearing the role removes it from the list
altogether.

The new column is added by [`ext_tables.sql`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/ExtTablesSql.html#file-extension-ext-tables-sql): **run the database analyzer
once after updating**. Every partnership that existed before carries `0`
in it, so the upgrade wizard *Seed the partnership sort order of academic
partner roles* fills it with the order the role forms show today - the current
`sorting` of each partnership, with `uid` settling ties. Run it once;
it reports nothing to do afterwards. Until it has run, a partnership saved in the backend keeps no position of its own:
the wizard is the one that knows the order the roles show today, so a partnership
whose list is still unseeded is left to it. Running the wizard again is
harmless: it appends
what has no position yet and never renumbers what has one, so an arrangement
made in a role form is not reset by it.

## Affected Installations {#affected-installations}

Every installation of this extension that fills partnerships with roles.