Jump to content

Import XML with XSL


This topic is 2596 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I am getting an error importing my xml with my custom stylesheet.  Where am I going wrong?


I am importing the following xml:


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <name>Abraham Lincoln High School</name>
        <district>School District No. 1 In The County Of Denver And State Of C</district>
        <name>Academia Ana Marie Sandoval</name>
        <district>School District No. 1 In The County Of Denver And State Of C</district>


I am using this stylesheet:


<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="no"/>
<xsl:template match="/">
<FMPXMLRESULT xmlns="http://www.filemaker.com/fmpxmlresult">
    <PRODUCT BUILD="" NAME="FileMaker" VERSION="ProAdvanced 12.0v2"/>
        <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="enrollment" TYPE="TEXT" />
        <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="districtId" TYPE="TEXT" />
        <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="district" TYPE="TEXT" />
        <xsl:for-each select="./schools/school">
            <ROW RECORDID="" MODID="" >
                <COL><DATA><xsl:value-of select="name"/></DATA></COL>
                <COL><DATA><xsl:value-of select="type"/></DATA></COL>
                <COL><DATA><xsl:value-of select="enrollment/></DATA></COL>
                <COL><DATA><xsl:value-of select="city"/></DATA></COL>
                <COL><DATA><xsl:value-of select="state"/></DATA></COL>
                <COL><DATA><xsl:value-of select="districtId"/></DATA></COL>
                <COL><DATA><xsl:value-of select="district"/></DATA></COL>

Link to comment
Share on other sites

I am getting an error importing my xml with my custom stylesheet.


1. Always post the exact error message you get. Also please use the "code" option when posting XML.


2. Mind your quotation marks: they need to be closed ( "state" on line 14, "enrollment" on line 23).

Link to comment
Share on other sites

This topic is 2596 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 account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Pavel Smirnov
      How I can import XML file that is about 12 GB.
      I have an error after about 4 hours of parsing file, with no text in error dialog window.
    • By William Keyte
      Has anyone used the 'Import XML data over http' feature at all? It could be one of the most powerful tools in the product if only they had developed it properly and finished the job! Sorry I'm having a bit of a whinge here as I cannot quite believe that no facility has been created for allowing proxy details to be entered. This is one of those slightly hidden or 'less-known-about' features of Filemaker which could now prove to be one of the post powerful. As demand for web usage and interoperability increases etc. how can this feature be left not fully developed?! I'm staggered.

      The reason we want to use this - and I'm interested to know if anyone else has used it, is we develop shrink-wrapped 'application'- like databases that are locked down but upgradeable. This means that the database has to behave like a real compiled application. It will not be accessed by developers once installed on the customer's computer and has to stand on its own feet, as it were. Customers' data sets are imported and exported in their entirety.

      But we were looking for ways for the database, once out there on its own, to access critical data (usually some sort of 'meta' data) from our servers. This allows us centrally, to control some of the behaviours of the product in copies already out there. Now the import xml data over http is such a slick and easy way to allow a database to 'draw-in' data without having it fully 'connected' to another database. All you need is an 'http' URL. It's utterly brilliant…

      Except, of course, Filemaker have only done half a job. They've implemented this feature without any proxy control. That means that this feature will not work on any organisation networks where they don't allow unfiltered internet on port 80. If any proxies are involved and the router/firewalls are not set to accept requests on port 80 it's utterly useless. In actual fact, that means this feature is useless in 90% of educational establishments, most of Asia where proxies are normal even on home connections and certainly a majority of businesses where their IT departments are particularly security-minded. So… that's most of the world then. Filemaker, how and where are you intending this feature to be used, exactly?

      Sorry to sound so irritated but, really! I think what winds me up so much about this is just how good this would be if it were finished off! The fact that Filemaker Server can serve xml data as a specific service is an indicator of how seriously Filemaker has taken it at that end of the equation. So how on earth is it that this feature can ever be used?!

      Does anyone use it successfully? And if so how are you getting around the proxy/gateway issue? Many thanks for reading by rant! I'm just so disappointed.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.