Comments on: Update Infopath forms from within Workflow http://www.novolocus.com/2006/08/15/update-infopath-forms-from-within-workflow/ Whatever Andy Burns is working on... Tue, 6 Jan 2009 02:09:15 +0000 http://wordpress.org/?v=2.5.1 By: dave http://www.novolocus.com/2006/08/15/update-infopath-forms-from-within-workflow/#comment-3028 dave Mon, 06 Oct 2008 16:42:59 +0000 http://www.novolocus.com/?p=168#comment-3028 The code works fine for simple field updates. I tried it for just a text box on a sample form. But, when I have a Contact Selector on the infopath form I get the dreaded "Schema validation found non-datatype errors". This is a repeating object that allows the lookup of a person. If I have this control on the page, and I read and save the form (even without an update) I get the above mentioned error. I have read up on the error and most people experience it when they set a nil value to an object and don't remove the attribute. Any help is appreciated The code works fine for simple field updates. I tried it for just a text box on a sample form.

But, when I have a Contact Selector on the infopath form I get the dreaded “Schema validation found non-datatype errors”. This is a repeating object that allows the lookup of a person. If I have this control on the page, and I read and save the form (even without an update) I get the above mentioned error. I have read up on the error and most people experience it when they set a nil value to an object and don’t remove the attribute.

Any help is appreciated

]]> By: Andy http://www.novolocus.com/2006/08/15/update-infopath-forms-from-within-workflow/#comment-2794 Andy Wed, 30 Jul 2008 08:27:56 +0000 http://www.novolocus.com/?p=168#comment-2794 Hmm. Sounds weird. Have you updated the Infopath form maybe? I've had issues where we've updated the Infopath form - versioning on Infopath forms in SharePoint can be a bit hit and miss. We ended up installing our latest version for as an entirely new form... Hmm. Sounds weird. Have you updated the Infopath form maybe? I’ve had issues where we’ve updated the Infopath form - versioning on Infopath forms in SharePoint can be a bit hit and miss. We ended up installing our latest version for as an entirely new form…

]]> By: Linda http://www.novolocus.com/2006/08/15/update-infopath-forms-from-within-workflow/#comment-2791 Linda Wed, 30 Jul 2008 03:49:01 +0000 http://www.novolocus.com/?p=168#comment-2791 Hi there, Have anyone experience where the schema has change? I used the code and the workflow run somehow the InfoPath Schema of the xml file has change. Regards, Linda. Hi there,

Have anyone experience where the schema has change?

I used the code and the workflow run somehow the InfoPath Schema of the xml file has change.

Regards,

Linda.

]]> By: Andy http://www.novolocus.com/2006/08/15/update-infopath-forms-from-within-workflow/#comment-1431 Andy Wed, 09 Apr 2008 15:41:45 +0000 http://www.novolocus.com/?p=168#comment-1431 You can find this from the form itself. I think it's one of the properties of the .XSN file itself. Try opening the .XSN in Infopath and checking for properties (under the file menu) there. As you've rightly noticed, Infopath creates a unique namespace for your form - based on it's creation/update date, I think. (I'm no Infopath expert!) EDIT: Took a look, and the namespace under the File>Properties isn't quite right - some colons have been replaced by underscores. <a href="http://blogs.msdn.com/mahuja/archive/2008/03/31/passing-query-string-to-a-infopath-2007-form.aspx" rel="nofollow">There is some good advice from Madhur</a> - which is how I think I've done this in the past, actually (a long, long time ago): <blockquote>To find out your namespace, rename the .xsn file to .cab and open the template.xml file</blockquote> You can find this from the form itself. I think it’s one of the properties of the .XSN file itself. Try opening the .XSN in Infopath and checking for properties (under the file menu) there.

As you’ve rightly noticed, Infopath creates a unique namespace for your form - based on it’s creation/update date, I think.

(I’m no Infopath expert!)

EDIT: Took a look, and the namespace under the File>Properties isn’t quite right - some colons have been replaced by underscores.
There is some good advice from Madhur - which is how I think I’ve done this in the past, actually (a long, long time ago):

To find out your namespace, rename the .xsn file to .cab and open the template.xml file

]]> By: Omar Formacio http://www.novolocus.com/2006/08/15/update-infopath-forms-from-within-workflow/#comment-1405 Omar Formacio Fri, 04 Apr 2008 00:14:16 +0000 http://www.novolocus.com/?p=168#comment-1405 What is the NamespaceManager for InfoPath 2007 Form? "http://schemas.microsoft.com/office/infopath/2003/myXSD/2006-06-08T14:13:41");" What is the NamespaceManager for InfoPath 2007 Form?

“http://schemas.microsoft.com/office/infopath/2003/myXSD/2006-06-08T14:13:41″);”

]]> By: Mike http://www.novolocus.com/2006/08/15/update-infopath-forms-from-within-workflow/#comment-17 Mike Fri, 07 Dec 2007 19:45:30 +0000 http://www.novolocus.com/?p=168#comment-17 Thanks for your help! Writing back to Infopath xml should be simple, but has proven rather difficult. Your article saved me hours of work! Thanks for the great post! Thanks for your help! Writing back to Infopath xml should be simple, but has proven rather difficult. Your article saved me hours of work!
Thanks for the great post!

]]>