Very cool, but have you tried this in Sharepoint 2010? I'm trying to build a network of forms that are all created when one master form is submitted, and I followed the steps in this tutorial - the documents appear in the list but cannot be opened as infopath forms, also I can't seem to pull any field values from the original form.. I'm using SP 2010, is this something that relies on anything Microsoft would have changed about the new sharepoint?
@neofunctional Yes, the solution does not work "as is" in SharePoint 2010; you must modify it for it to work in SP 2010. And yes, I think a previous "hole" in SharePoint 2007 was locked down in SharePoint 2010.
@neofunctional I've only tested the solution displayed in the vid in SP 2010, but have not yet had a chance to look deeper into it and modify it for SP 2010.
Why is it necessary to create an XML template in the root folder rather than using the regular template that was already there? Do I need to create an XML template every time I update the template?
There is no logic to this solution. It is just something that works in SharePoint 2007 and might or might not work in future versions of SharePoint. If you use the template that was already there, the workflow will create .xsn files instead of .xml files. The answer to your second question is "yes".
InfoPath forms cannot exist without InfoPath form templates, and InfoPath form templates always need to be published somewhere before you can create InfoPath forms.
Very cool, but have you tried this in Sharepoint 2010? I'm trying to build a network of forms that are all created when one master form is submitted, and I followed the steps in this tutorial - the documents appear in the list but cannot be opened as infopath forms, also I can't seem to pull any field values from the original form.. I'm using SP 2010, is this something that relies on anything Microsoft would have changed about the new sharepoint?
neofunctional 8 months ago
@neofunctional Yes, the solution does not work "as is" in SharePoint 2010; you must modify it for it to work in SP 2010. And yes, I think a previous "hole" in SharePoint 2007 was locked down in SharePoint 2010.
symwongaton 8 months ago
@symwongaton Thanks for the quick reply - have you tried it in SP 2010? Or have any ideas on where I should start to modify the process? Thanks again
neofunctional 8 months ago
@neofunctional I've only tested the solution displayed in the vid in SP 2010, but have not yet had a chance to look deeper into it and modify it for SP 2010.
symwongaton 8 months ago
Why is it necessary to create an XML template in the root folder rather than using the regular template that was already there? Do I need to create an XML template every time I update the template?
Thanks.
Haleh1 1 year ago
There is no logic to this solution. It is just something that works in SharePoint 2007 and might or might not work in future versions of SharePoint. If you use the template that was already there, the workflow will create .xsn files instead of .xml files. The answer to your second question is "yes".
symwongaton 1 year ago
i dont understand why you need to make a template...
jimmyd00gan 2 years ago
InfoPath forms cannot exist without InfoPath form templates, and InfoPath form templates always need to be published somewhere before you can create InfoPath forms.
symwongaton 2 years ago
you are a Genius! thanks for tutorial!! it´s the best!
eligodoy 2 years ago
Glad you found it useful!
symwongaton 2 years ago
you are a genius!
eligodoy 2 years ago
No audio
tomHasani 2 years ago