Description The import of a requirement with a doc-id exceeded the max size results to an error (that's ok) and a data inconsistency (should be avoid).
A tl_node_hierarchy record is created whereas the associated tl_requirements record is not.
The node hierarchy cannot be destroy without a direct access to the database.
-> The import ends with a low level error. In the requirement navigator, you can see a requirement without doc-id (beginning with a colon ':'). Clicking on the requirement results in the message 'Requirement does not exist anymore.'.