3 Replies Latest reply on Sep 17, 2017 11:52 PM by libby.White

    Attachments with UPPERCASE extension cannot be uploaded in Service Request parameter after upgrade to 2016.2.1

    c.reinhardt84 Apprentice

      Atfer upgrading to 2016.2 (from 2015.2) were are no longer able to upload an attachment to a request offering which has an Uppercase Extension. This belongs to the Attachment widget on a request offering form.

       

      See screenshot. We were able to reproduce the issue with Internet Explorer 11, Google Chome 56 and Firefox 45.4.
      We also tested with different roles but the result is the same. One way to reproduce this issue is to login to the self service and select a offering to create a new service request. Then you need to attach two file for example test.jpg and Test2.JPG, Then you will see that one of them is highlighted and not uploaded after you save the request.

      It seems that the issue only occurs at Service Requests and not in Incidents. We are able to upload files with lower and uppercase extensions to Incidents.

       

      Do you have the same issue?

       

        • 1. Re: Attachments with UPPERCASE extension cannot be uploaded in Service Request parameter after upgrade to 2016.2.1
          c.reinhardt84 Apprentice

          We got Feedback from HEAT Support. It is a known issue in 2016.2 and will be fixed in 2017.3.

          There is a Workaround available. We got some SQL scripts which changes the table frs_def_attachextension to allow duplicat entries e.g: *.jpg and *.JPG

           

          Here is the original script:

           

          --Backup existing data

          select *

          into Frs_def_attach_extensions_temp

          from Frs_def_attach_extensions

           

          GO

           

          --Drop constraint

          ALTER TABLE [dbo].[Frs_def_attach_extensions] DROP CONSTRAINT [UN_Frs_def_attach_extensions_FileMask]

          GO

           

          --Change collation to allow storage of upper case and lower case

          ALTER TABLE Frs_def_attach_extensions ALTER COLUMN FileMask 

                      nvarchar(64)COLLATE SQL_Latin1_General_CP1_CS_AS NOT NULL; 

          GO

           

          --Recreate constraint

          ALTER TABLE [dbo].[Frs_def_attach_extensions] ADD  CONSTRAINT [UN_Frs_def_attach_extensions_FileMask] UNIQUE NONCLUSTERED

          (

                 [FileMask] ASC

          )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)

          GO

           

           

          I added an additional line to instert the same extensions with uppercase:

           

          INSERT INTO Frs_def_attach_extensions (FileMask)

          select UPPER(FileMask) from Frs_def_attach_extensions_temp

          GO

           

          Also you need to update all of your request offerings manualy to enable the "new" extensions for the attachments widget where you used it. For this I used the follwing SQL query. This works for us because the attachment widget is configured the same in each offering. Please don't use if you are not sure that all attachment widgets in your  offerings are having the same properties.

           

          update ServiceReqTemplateParam

           set ConfigOptions = '{"configData":{"height":0,"topMargin":0,"bottomMargin":0,"preserveSpace":false,"fileSizeUploadLimit":100,"fileNumberUploadLimit":10,"fileTypes":"*.avi;*.csv;*.eml;*.html;*.mhtml;*.pfx;*.ppt;*.rtf;*.wmv;*.xml;*.bmp;*.doc;*.flv;*.jpg;*.msg;*.png;*.pptx;*.tif;*.xls;*.xps;*.cer;*.docx;*.gif;*.mht;*.pdf;*.pps;*.rar;*.txt;*.xlsx;*.zip;*.AVI;*.CSV;*.EML;*.HTML;*.MHTML;*.PFX;*.PPT;*.RTF;*.WMV;*.XML;*.BMP;*.DOC;*.FLV;*.JPG;*.MSG;*.PNG;*.PPTX;*.TIF;*.XLS;*.XPS;*.CER;*.DOCX;*.GIF;*.MHT;*.PDF;*.PPS;*.RAR;*.TXT;*.XLSX;*.ZIP","singleSelect":false,"imageWidth":48,"imageHeight":48,"withAdvancedSearch":false,"typeAheadChars":3,"enableHint":false,"usePriceList":false,"noPriceExclude":false,"defaultValueRadioVal":"none","priceQuantityField":""}}' 

          where DisplayType = 'swfupload'

          1 of 1 people found this helpful
          • 2. Re: Attachments with UPPERCASE extension cannot be uploaded in Service Request parameter after upgrade to 2016.2.1
            TomTheiler Apprentice

            I can confirm we have the same issue with 2016.2. Only Service Request affected. I can also confirm that your script works.

             

            Thanks for sharing.

            • 3. Re: Attachments with UPPERCASE extension cannot be uploaded in Service Request parameter after upgrade to 2016.2.1
              libby.White Apprentice

              We had this issue as well - just tested on 2017.2.1.26741  28th August release and can now successfully upload files with extensions with uppercase.