AnsweredAssumed Answered

XLSX string import bug

Question asked by PetterDerhaag on Jul 17, 2015
Latest reply on Jul 17, 2015 by philmodjunk

Summary

XLSX string import bug

Product

FileMaker Pro

Version

14.0.1 (but previously also 13)

Operating system version

OS X 10.10.4

Description of the issue

Whenever importing a set of records from an xlsx file, some strings do not get imported correctly into a text based field into filemaker. This specifically occurs for strings starting with 0E... The bug is independent of which data type is set at the excel side, import results in "?".

The issue does not occur if a space is entered somewhere in between or after the 0E part of the string, but does occur if you put a space as first character.

Also, the issue does not occur when importing from an xls file.

Steps to reproduce the problem

using multiple different files
manually entering the strings (in excel) and trying again
setting auto-calc within the field (which evaluates incorrectly because of the '?' that's imported)

Expected result

<0E12345678> - imported in text field in table

Actual result

<?> - imported in text field in table

Exact text of any error message(s) that appear

N/A

There is no error message, which makes the bug all the more sneaky, took me a while to notice it.

Configuration information

The issue occurs independent of FM Version (between 13 and 14 at least) and happens with all different excel files I have tried with so far.

Workaround

Using applescript to automatically save the file as xls has solved the issue for now.

Outcomes