Calculated XSL file path produces a SAXParseException (7 Comments)

Issue report by Malcolm Fitzgerald

Product

FileMaker Pro

Version

11.0.3

Operating system version

Mac OS X 10.6.8

Description of the issue

We cannot write portable code for sharing XSL export rules.

Steps to reproduce the problem

I have a file stored in a folder within extensions that contains XSL code. When I hardcode the path to this file using the "File" option the SAX parser is happy. The file path is displayed in the file path dialog box.

If I try to create a calculated version of this path the SAX parser throws an error.

This occurs even when the calculation I use is the exact text string used in the "file" option is copied from the file path dialog box.

Expected result

The SAX parser should accept the calculated file path

Actual result

The SAX parser throws an error whenever a calculated result is used.

Exact text of any error message(s) that appear

SAXParseException: unable to determine file base pathname (Occurred in an unknown entity, at line 0, column 0.)