2657 views

Description

The attachment file extension is removed from the file name if the attachment file name is longer than the maximum length of the sys_attachment column name file_name attribute. In addition, because the Manage Attachment window does not always display the file type correctly (for example, Outlook file type), identifying the type of attachment is even more difficult.

Steps to Reproduce

  1. Log in to the base system instance.

  2. Create or rename files of three different file types for attachments with a name having 125 characters. For example:

    1pleasedonottruncate_2pleasedonottruncate_3pleasedonottruncate_4pleasedonottruncate_5pleasedonottruncate_6pleasedonottruncate.txt
    1pleasedonottruncate_2pleasedonottruncate_3pleasedonottruncate_4pleasedonottruncate_5pleasedonottruncate_6pleasedonottruncate.png
    1pleasedonottruncate_2pleasedonottruncate_3pleasedonottruncate_4pleasedonottruncate_5pleasedonottruncate_6pleasedonottruncate.msg

  3. Navigate to Incident > Open and select an incident.

  4. Click the attachment icon and add these files as an attachment.

    Note that the file names have been trimmed to first 100 characters including the file name. You can also verify the truncation by viewing the sys_attachment table (https://instancename.service-now.com/sys_attachment_list.do?). Also, if an Outlook file is included, its icon does not display correctly.

 

 

Workaround

Increase the maximum length attribute of the File Name column in the Attachments (sys_attachment) table:

  1. Enter sys_attachment.list in the application filter to open the Attachments table.

  2. Right-click the File name column label and select Configure > Dictionary.

  3. Locate file_Name under Column name and increase the Max length value.

    Note that if the file name is longer than this value, the file extension will be truncated.

    Note 2: If you increase the length beyond 255 then it will change the field type to "MEDIUMTEXT" on the backend.
    We do not recommend exceeding this length without thoroughly testing in sub production.

To receive notifications when more information is available about this issue, click the Subscribe button at the top of the article.


Related Problem: PRB584906

Seen In

Berlin Patch 6
Calgary Patch 2 Hot Fix 5
Eureka Patch 2
Fuji Patch 10
Fuji Patch 11
Fuji Patch 7 Hot Fix 5
Geneva Patch 3 Hot Fix 2
Helsinki Patch 4

Intended Fix Version

Madrid

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-08-27 01:45:13
Published:2018-06-15