>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3613392. --> Reported by: [maheshv](https://www.drupal.org/user/2596242) Related to !54 >>> <h3>Error:</h3> <p>Drupal\Core\Entity\EntityStorageException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'uri' at row 1: INSERT INTO "file_managed" ("uuid", "langcode", "uid", "filename", "uri", "filemime", "filesize", "status", "created", "changed") VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7, :db_insert_placeholder_8, :db_insert_placeholder_9); Array ( [:db_insert_placeholder_0] =&gt; bd5512d3-4007-455d-afd5-be61e96f6ac8 [:db_insert_placeholder_1] =&gt; en [:db_insert_placeholder_2] =&gt; 642 [:db_insert_placeholder_3] =&gt; webimage-portrait-happy-senior-woman-with-trekking-poles-and-backpack-wears-hat-in-the-national-park-for-hiking-active-elderly-female-lifestyle-activity-healthy-adventure-in-nature [:db_insert_placeholder_4] =&gt; <a href="https://assets.ex.com/asset/64fda232-8738-4607/thumbnail/webimage-portrait-happy-senior-woman-poles-and-backpack-wears-hat-in-the-national-park-for-hiking-active-elderly-female-lifestyle-activity-healthy-adventure-in-nature">https://assets.ex.com/asset/64fda232-8738-4607/thumbnail/webimage-portrait-happy-senior-woman-poles-and-backpack-wears-hat-in-the-national-park-for-hiking-active-elderly-female-lifestyle-activity-healthy-adventure-in-nature</a> [:db_insert_placeholder_5] =&gt; image/jpeg [:db_insert_placeholder_6] =&gt; 48759 [:db_insert_placeholder_7] =&gt; 1 [:db_insert_placeholder_8] =&gt; 1785149161 [:db_insert_placeholder_9] =&gt; 1785149161 ) in Drupal\Core\Entity\Sql\SqlContentEntityStorage-&gt;save() (line 817 of /app/docroot/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).</p> <h3>Problem/Motivation</h3> <p> When a user uploads an asset to Bynder, they can either use the file name as the asset title or provide a custom title. Bynder allows asset titles up to 400 characters. </p> <p> The Drupal Bynder connector generates a URI using the Bynder asset URL and title. If the title is sufficiently long, the generated URI can exceed Drupal's <code>file_managed.uri</code> field length limit of 255 characters, causing the asset import process to fail. </p> <p><strong>Example generated URI:</strong></p> <pre> https://assets.ex.com/asset/64fda232-8738-4607/thumbnail/webimage-portrait-happy-senior-woman-with-trekking-poles-and-backpack-wears-hat-in-the-national-female-lifestyle-activity-healthy-adventure-in-nature </pre><p> When the generated URI exceeds 255 characters, Drupal throws a database error while creating or updating the corresponding file entity. </p> <p> As a result: </p> <ul> <li>The asset cannot be referenced in Drupal.</li> <li>Errors are written to Drupal logs.</li> <li>Editors are unable to use affected assets.</li> </ul> <h3>Steps to Reproduce</h3> <ol> <li>Configure the Bynder Drupal connector.</li> <li>Upload an image asset to Bynder.</li> <li>Assign the asset a title between 300 and 400 characters.</li> <li>Allow the asset to finish processing.</li> <li>Log in to Drupal.</li> <li>Create or edit content.</li> <li>Open the Bynder media browser.</li> <li>Select the asset with the long title.</li> <li>Insert or save the asset.</li> </ol> <h3>Actual Results</h3> <p> Drupal attempts to create a file entity and store the generated URI in the <code>file_managed.uri</code> column. </p> <p> The operation fails because the generated URI exceeds the database column length limit. </p> <p> Example error: </p> <pre> SQLSTATEString data, right truncated </pre><p> or </p> <pre> Data too long for column 'uri' </pre><p> The image cannot be imported or referenced successfully. </p> <h3>Expected Results</h3> <p> Assets with long titles should be imported successfully without database errors. </p> <p> The Bynder connector should ensure generated URIs do not exceed Drupal's storage limits, or utilize a shorter identifier that does not depend on asset title length. </p> <h3>Additional Details</h3> <p> The issue appears to be caused by a mismatch between: </p> <ul> <li>Bynder title limit: up to 400 characters</li> <li>Drupal <code>file_managed.uri</code> limit: 255 characters</li> </ul> <p> Currently, the connector does not appear to validate or truncate URI values before attempting to save them to Drupal's file management system. </p> <h3>Impact</h3> <p> Any Drupal user attempting to reference a Bynder asset whose generated URI exceeds the Drupal database limit may encounter this issue. </p> <p> The asset becomes unusable within Drupal and generates errors in system logs. </p> <h3>Possible Solutions</h3> <ul> <li>Truncate title-derived URI segments before saving.</li> <li>Use the Bynder asset UUID instead of the full title when generating URIs.</li> <li>Add validation to prevent oversized URIs from being stored.</li> <li>Provide a configurable maximum title length.</li> <li>Document supported title limits when using the Bynder Drupal integration.</li> </ul> <h3>Acceptance Criteria</h3> <ul> <li>Given I am an authenticated Drupal user</li> <li>When I select a Bynder asset with a long title</li> <li>Then the asset is successfully imported and referenced</li> <li>And no database error is generated</li> <li>And no error is written to Drupal logs</li> </ul> <h3>Environment</h3> <ul> <li>Reproduced in: Non-prod and Prod</li> <li>Drupal Version: 10.*</li> <li>Bynder Module Version: 4.*</li> <li>Database: [MySQL/MariaDB/PostgreSQL]</li> </ul>