STRUCT-MAX-LENGTH - Maximum cell length from taxonomy metadata (no columns in eba-4.0-errata5)

Official control text (EBA, verbatim)

This check has no official EBA W1 control text: it is a product mechanic of the structural layer (metadata-driven maximum cell length, blueprint task F2.E3.T1). No length limit is ever invented by the product - the limit comes exclusively from the curated taxonomy metadata (max_length per column).

What this rule checks

The check reads the max_length attribute of every column from the curated taxonomy metadata and reports one blocking finding per cell whose value is longer than the column's limit. The finding parameters carry both numbers: maxLength (the limit) and actualLength (the length of your value).

Measured on eba-4.0-errata5: every one of the 120 columns carries max_length: null - the frozen EBA artifacts define no per-column length caps, so on the current taxonomy this check never fires. The mechanics stay wired to the metadata: if a future curated taxonomy version sets limits, they are enforced without a code change. The product never invents a limit of its own.

This is a structural check in the RoI Builder (STRUCT layer, severity: blocking). It maps to no W1a/W1b control at the ESAs - the official validation does not technically reject a package on receipt for this finding. The RoI Builder blocks the final export on it, so the issue is caught before filing.

Most common causes

• On the current taxonomy (eba-4.0-errata5) this check cannot fire: no column carries a length limit.
• If a future taxonomy version sets a limit, the typical way to exceed it is pasting a value with surrounding text (e.g. a whole address block or a note) into a single cell.

How to fix it, step by step

1. Read the finding parameters: maxLength is the column's limit, actualLength is the length of your value.
2. Shorten the flagged cell below the limit - remove pasted surroundings, keep the bare value.
3. Run the validation again and confirm the finding is gone.

Example: fails vs passes

Measured on eba-4.0-errata5 there is no real failing example: no column carries a length limit, so this check reports nothing today. The mechanics, for a future column with a limit L:

Value length	Result
longer than L	fails - the finding carries maxLength = L and actualLength
L characters or shorter	passes
(empty)	passes - an empty cell has no length to check

Related rules

• STRUCT-DATE-FORMAT, STRUCT-INTEGER-FORMAT, STRUCT-DECIMAL-FORMAT - the same per-cell, metadata-driven family of the structural layer; unlike them, this check currently applies to no column.
• STRUCT-ENUM-VALUE - dictionary membership is also driven purely by the curated taxonomy metadata.