Custom import - InfoPath Dev
in

InfoPath Dev

Custom import

Last post 12-02-2005 01:32 AM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 12-01-2005 12:35 PM

    Custom import

    I create a form using a given schema memo.xsd .
    When this form is saved , it has ns1 as the namespace. and the two lines of
    <?mso-infoPathSolution solutionVersion="1.0.0.41" productVersion="11.0.6565" PIVersion="1.0.0.0" href="file:///D:\A_IMI_NET\CDA3Import\bin\Debug\CDA3Import.xsn" name="urn:schemas-microsoft-com:office:infopath:CDA3Import:-myXSD-2005-09-23T00-43-14" language="en-us" ?>
    <?mso-application progid="InfoPath.Document"?>

    I modify the manifest to allow for import of files based on myschema.xsd :
    <xsf:importParameters enabled="yes">
    <xsf:importSource name="" schema="memo.xsd" transform="ImportMemo.xslt"></xsf:importSource>
    </xsf:importParameters>

    When I try to import an xml file based on memo.xsd, using the ImportMemo.xslt, I get errors , This form has an unknown structure.
    #65279;#65279;
    What is the correct xslt file to do the job given that xml file will:
    1- have its own namespace declaration
    2- not have the mso instruction lines

  • 12-02-2005 01:32 AM In reply to

    The schema is bad. Each XSLT has to have an XSD attached to it. See the out-of-box samples Meeting Agenda and Issue Tracking for examples.

    Patrick Halstead [InfoPath MVP]
    InfoPathDev
    Patrick Halstead
    Project Manager at Qdabra
Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.