---
title: "Breaking: #88640 - Database field \"sys_template.nextLevel\" and TypoScript sublevel - inheritance removed"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-88640"
source: "Changelog/10.0/Breaking-88640-DatabaseFieldSys_templatenextLevelAndTypoScriptSublevel-InheritanceRemoved.rst"
typo3-version: "10.0"
typo3-major: 10
type: "breaking"
issue: 88640
forge: "https://forge.typo3.org/issues/88640"
tags: ["Database", "NotScanned"]
rendered: "2026-09-24T12:29:17+00:00"
---

# Breaking: #88640 - Database field "sys_template.nextLevel" and TypoScript sublevel - inheritance removed {#breaking-88640}

See [forge#88640](https://forge.typo3.org/issues/88640)

## Description {#description}

The database field `nextLevel` of the database table `sys_template` where TypoScript configuration
is stored, has been removed.

The field `nextLevel` was introduced in TYPO3 v3.x before TypoScript could be imported from
external files.

Nowadays, TypoScript conditions should be used much more instead of this `nextLevel` feature,
which is kind of a pseudo-condition.

## Impact {#impact}

The database field is removed, and not evaluated anymore in TypoScript compilation.

Requesting the database field in custom database queries will result in an SQL error.

## Affected Installations {#affected-installations}

TYPO3 installations that have `sys_template` records with this flag activated,
or querying this database field in third-party extensions.

## Migration {#migration}

Check for existing `sys_template` records having this flag activated by executing
this SQL command:

`SELECT * FROM sys_template WHERE nextLevel>0 AND deleted=0;`

before updating TYPO3 Core.

Replace the sys_template record (the uid of the record is stored in the "nextLevel" field) with a condition e.g. `[tree.level > 1]` to add TypoScript for subpages.