Current State:
During Assets Discovery import in assets, when an Application or Database object name exceeds 255 characters, the import is rejected at the API level by the Assets platform. Discovery passes the full string without truncation, causing the import to fail silently or error out — with no automatic handling or user-facing guidance to resolve it.

Proposed Future State:
Assets Discovery should automatically truncate the Name attribute value to 255 characters before passing it to the Assets API, preventing import failures. Optionally, the full untruncated string should be stored in a separate Textarea (or equivalent high-capacity) attribute for audit and reference purposes, ensuring no data loss while maintaining platform compatibility.

Workaround:
Apply a one-line truncation in the relevant scan pattern's processing code before the name is assigned, so the value passed to the API stays within the 255-character limit. If the full string is needed for audit purposes, store it separately in a Textarea or another attribute with a datatype that supports more than 255 characters.