InfoPath Dev

To get your info from one form to the other you could use input paramters. I'm sorry, but I don't know if managed code is allowed in form templates used in form web parts. Here's a blog post on InfoPath input parameters: http://blogs.msdn.com/b/infopath/archive/2007/02/26/passing-data-into-a-form-input-parameters.aspx If you ...

Did you try my suggestion above? Add a button to your form that has a rule action to execute the Submit connection you created to the UpdateListItems method - this way you can make sure the submit connection is executing without issue. One thing I also found odd - you mention the Error node is blank, and the Results node unchanged. That makes it ...

So, the XPath for your filter gets a little more complicated, because you have to get the display name for the ID in your main data source category field in order to find the correct products. Can you attach your template to a reply, under the Options tab?

So, CheckOutItems fails, you get an error in the browser with a correlation id, and the id isn't present in the logs? Usually, if something works in client but not in browser, the first thing I look at is postback - do you have postback set to always on the control that is running the command? You could also try adding a button that just ...

You can't find the error in the SharePoint Log files? Do you have access to the server to look? Are you using ShP 2007 or 2010? Let me know if you need the file path to the log files - I generally trigger the error, get the correlation ID and go look in the logs right away to make it easier to find the error info.

This could be the data connection to the SharePoint Lists web service. It would be good to test your environment and see if other SharePoint web services work from IPFS - for example, create a simple form that uses the CheckOutFile method.

Hi - Your main data source node isn't repeating, so current() shouldn't come into play. I just tried this - and my drop downs cascaded nicely: /dfs:myFields/dfs:dataFields/d:SharePointListItem_RW[d:Category = xdXDocument:get-DOM()/pr:properties/p:properties/documentManagement/ns2:Category] So, what I'd check first is that the ...

Hey, Scott, thanks for sharing this!

Do make sure that the field isn't marked as "Cannot be blank" - you mention it is optional, so I assume you've already checked that, but if you are having trouble with Jimmy's suggestion, that check box may have gotten selected in the field's properties.

Hi: I'm afraid I don't understand the second part of your question. As to the first part, when you convert a data connection to a UDCX, you have the option of using a centrally managed data connections. Here's a good MSDN post on these options that may help you.