InfoPath Dev

Hallo,
we use XML Specifications in 2 ways (standard xml and infopathform)
publishing the ip-forms to sharepoint is no problem
but we also want to manage our standard xml specs with sharepoint

with sharepoint 2003 i created a formlibrary and modified the initial template with infopath, in this blank template i created some textfields and named them like the nodes in the xmls. i published the template and selected the fields which should be shown as meta data columns in my form library. after this i could upload the xml files and the entries become mapped automatically to the columns like the ip-xmls

now we want to use moss for managing our files
and there (together with IP2007) i tried to do it in the same way
but it doesn't work, the the columns become not mapped

what can i do?
what's the difference betweed 03 & 07 in this case?

Hello and welcome to our forum!

This is interesting. I know exactly what you're talking about. You're using a lesser known feature of SharePoint 03. I don't know why it wouldn't work in SharePoint07. It may be because of the new content types architecture they've introduced in the latest version. Since your XMLs won't have the InfoPath PI in them SharePoint 07 must be ignoring them for the purposes of property promotion.

Something to try is to manually inject the InfoPath PI at the top of your XML file and see if it promotes the properties anyway. That would provide a clue as to what is happening.

today i've tested it in 3 steps
1. inject the infopath pi manually in the head of the xml
-> doesn't work
2. step 1 + <my:myFields>*</my:myFields> around the data tags
-> doesn't work
3. steps 1+2 + rename the affected tags to IP conforming tag e.g. <SpecId>123</SpecId> to <my:SpecId>123</my:SpecId>
-> it works, but this is not the solution it wanted to have

so it seems, that moss and ip 2007 don't supports this feature anymore
maybe because of the deeper integration and using of metadata of the templates