Error when creating an update template using import functionality

[kateg]

Hello,

In list view when trying to Import and selecting the Update option to create an excel template, it's giving an error "Excel cannot open the file ... because the file format or file extension is not valid...". This error occurs when the option "Include all fields in the template" is ticked and the file size saved is 0. It creates when the field is unticked and able to reproduce the error in any list. The insert option works, only having an issue with update.

Instance is running Istanbul Patch 5 hot fix 1. I've tested in Helsinki and this functionality is working with the include all fields in the template ticked. The user who first reported the issue believes they have used it since moving to Istanbul, but it stopped working about a month ago.

If I filter out all the records and then do the Import with just the list fields the Update works successfully when Include all fields in the template is ticked.

Has anyone else experienced this issue at all or have any ideas as to how I might be able to fix it?

Thank you

[kuba4]

I have the same problem with Istanbul Patch 5 Hotfix 1.

Anyone can help?

[servebot]

Kate,

ServiceNow helped me out with this issue. You can find a workaround here:

ServiceNow KB: Trying to create an xlsx format template fails for tables containing a currency outpu...

1. Set the system property glide.legacy.excel.export to true.
2. During the template creation, choose the XLS file type.
3. Continue the update process using the xls file instead of the xlsx file.

Note: I had to create the property as it did not exist in my environment. Hope this helps!

Thanks,

Mike

[kateg]

Hi Michael,

Thanks for your response. Unfortunately doing that workaround I'm still experiencing the same issue, when importing to XLS the file size is still 0. It does work with the include all fields in the template unticked, so there must still be an error it's picking up in the currency field

[kuba4]

I've tested the solution below. Unfortunately, problem still exists. Again it shows that import file has 0 bytes.