Vaughan Posted August 28, 2009 Posted August 28, 2009 Hello folks I have a system that does xml exports and xslt transforms. Currently both the FMP database files and the xslt files live on a file share, primarily to make the file paths for the exports easier (it was developed in FMP 6 days I think). I'm converting the system to live on a FMS server, so I'm putting the XSLT files into container fields and using the Export Field Contents script step to put the file into the temp folder from where it can be referenced by the Export REcords script step. The xslt file is getting into the temporary folder and when I open it in TextEdit it looks OK, but the export records step is choking with error 717 (There is not enough XML/XSLT information to proceed with the export or import). The "old" exports are working so there is data to export, so my thoughts ar that the xslt file is getting mangled somehow. Any ideas? Thanks
comment Posted August 28, 2009 Posted August 28, 2009 Try disabling error capture to get a more meaningful error message. BTW, why don't you serve the XSLT files, either on the network or through HTPP?
Vaughan Posted August 28, 2009 Author Posted August 28, 2009 Thanks comment. The error 717 gets returned by the script debugger. Error capture is not turned on in the script (nor in any scripts that call the export script). When the script runs there is no error reported, but the records don't get exported. A silent failure. The web serving of the files is a good idea, but my preference is to not rely on another service. I'm not responsible for the web servers at this org and don't really want to enable web services in the FMS just for a half dozen text files. I can imagine somebody doing a cleanup and deleting them.
comment Posted August 28, 2009 Posted August 28, 2009 (edited) You need to do some eliminations. First, take the exported stylesheet out of temp and place it next to a local .fp7 file. Then do a manual export, pointing to the adjacent stylesheet. If it works, the problem is not with the stylesheet itself. If it doesn't, zip the stylesheet and post it here. don't really want to enable web services Well, the point is that a stylesheet can be practically anywhere. If you don't want to serve it as HTPP, you should still be able to place it somewhere on the network where anyone can access it. Edited August 28, 2009 by Guest
Vaughan Posted August 28, 2009 Author Posted August 28, 2009 The style sheet works next to the fp7 file. But I haven't tested it by copying it directly to the temp directory, as opposed to exporting it from the field. Good idea I'll try this on Monday morning. ;)
comment Posted August 28, 2009 Posted August 28, 2009 I would try placing the stylesheet back into the the temp folder, and testing a manual export again. If it works, there is an issue with the script path. If it doesn't, the issue is with the real path. I recall having some problems before with paths that had elements with spaces in their names.
Recommended Posts
This topic is 5916 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now