InfoPath Dev

That worked, this time it also associated itself with the correct content type.  i do have two Product Fields now, but at least it works.  Thanks again!!!

Hope that title made sense.   When I published my form, I was promoting a Product field which is drop-down field.  I expected that field type to be single line of text, but it came as Multiple line of text. I can not seem to find a way to update/specify what field type to promote. sharepoint 2010, infopath 2010  As always, ...

Okay, removed the on-loads and there is still the error. Correlation ID is pretty useless. 

When I click Add Document or  New Document in the ribbon I get:  Error: There has been an error while loading the form. I have the InfoPath form compatiblity set, the sharepoint form library set to open in browser and there are no errors in design checker nor logic inspector.  When I switch the library settings to open in ...

I was hoping to start a thread to talk about issues with SharePoint migrations.   Infopath is holding our migration hostage and I dont want this to happen to anyone else. UCDX Connections are definitely best practice.    submittal data connections have to be manually configured any hard coded server references need ...

Thank you for the quick post, after trying your suggestions, I realized the GUID was incorrect.   Pardon and if this post should be deleted..

  We have an issue (many) while migrating 2007 to 2010.   The data connection to an XML in 2010 is not working.  We are using this command:  _vti_bin/owssvr.dll? 2007 http://[MyServer]/sites/[MySite]/_vti_bin/owssvr.dll?cmd=Display&List=%7BC73DBC61%2D1995%2D481C%2DB0B4%2DF1A9A77E4F32%7D&XMLDATA=TRUE 2010 - What ...

Cleared the internet cache and temp files.   Worked.   It seems like Infopath tries opening in a browser behind the scenes which temporarily locks the record while the client is attempting to open.

We are working with a migration expert and have found a snag.   Migrations and infopath xml’s not migrating properly when the xml’s are in one library and the associated form template (.xsn) is in another.  This allows us to have version on the .xsn itself.  The issue is that the data connections for the forms are ‘hard-coded’ ...

Same issue here.  We are using the client application and not browser enabling.   Doesnt work in the print or print preview.   Print preview crashes the form.