AnsweredAssumed Answered

WebDirect Export Field Contents Inconsistent with FileMaker Pro

Question asked by JohnDuncan on Mar 19, 2014
Latest reply on May 12, 2015 by TSGal

Summary

WebDirect Export Field Contents Inconsistent with FileMaker Pro

Product

FileMaker Pro

Version

13.0v1

Operating system version

Mac OS X 10.8.5

Description of the issue

The "Export Field Contents" script step produces different results on WebDirect vs FileMaker Pro.  With a text field full of XML (which is really an Excel XML file) if I do an Export Field Contents in FileMaker Pro and specify a file name of "myExport.xls" it will export to a file with the correct ".xls" suffix.  If I export the same field contents on WebDirect it ignores the ".xls" suffix and changes it to ".xml".

If the same text contents are moved into a container field and exported, the result with FileMaker is the same but the result with WebDirect is you get a text file named "myExport.txt" with the content being just "Untitled.txt"

Steps to reproduce the problem

Place XML in a text field and export from FileMaker and from WebDirect giving the file a suffix other than ".xml" and it will respect the suffix with FileMaker Pro and ignore it with WebDirect.  Likewise for exporting the contents of a container field as described above.

Expected result

Expected in both cases to get "myFile.xls" exported from the script step.

Actual result

If exported from a text field the export file has the suffix of ".xml" instead of ".xls".  If exported from a container field it has the suffix of ".txt" and does not contain the text content of the container.

On WebDirect via Windows Internet Explorer 11 it behaves differently and does not provide any suffix for the content downloaded from the text field.

Exact text of any error message(s) that appear

N/A

Configuration information

FileMaker Pro 13.0v1 running on Mac OS X 10.8.5
FileMaker Pro 13.0v1 running on Windows 7 Pro
FileMaker Server 13.0v1 running on Mac OS X 10.9.2
Safari 6.1.2 running on Mac OS X 10.8.5
Internet Explorer 11 running on Windows 7

Workaround

The user is forced to open the .xml document (Mac) or document without suffix (Windows) in Excel.

Outcomes