InfoPath Dev

There was no way. So I created a different archival process, one that would store the necessary information in a table, without the forms. It wasn't pretty, lost some secondary data, but did the job. Things might have changed now that three years have passed, but I wouldn't bet on it - Microsoft products don't appreciate people ...

 Hi, I had the same problem and have found the following solution (in C#):             System.Diagnostics.Process proc = new System.Diagnostics.Process();             proc.StartInfo.FileName = ...

Can you provide a link to that article here?

 No, I was unable to interact directly with the picker. All I could do was manipulate the data structure it provides to make sure that the first element is always selected. I do not have the code on hand right now (and won't until Monday), but the idea itself is pretty simple - you address the DOM node like an array (i.e: ...

 I use an administrator approved browser-enabled content type in my form library that also provides the columns for it. When I updated the content type with a few more columns (promoted), they didn't show up in the library for some reason. I even tried creating a new library, but it would still use the old version of the content type, ...

 The simplest solution would be to use position(0) or first() directly in the rules section, but, these functions are forbidden for some reason. So I resorted to addressing the first element of the list in the code via an xml statement. ( ...[1] )

 Hi Sweta,   I asked the same question recently, and got an answer from Greg here. To be a little more precise, each web service that can accept parameters has query fields in its DOM. So, when you want to pass a parameter to the webservice, you can create a rule that does this by assigning a value to the necessary query fields. Then ...

 One such solution is described here.

Aha, not so obvious,but still easy. Shouldn't have shied away from the content type management in the first place. Anyhow, this works, so thanks a bunch!

How can I do that in a browser enabled form? Normally a trivial XPath expression like "mynode[1]" or "mynode[number()=1]" or "mynode[position()=1]"  does the trick - but no luck there: the former two get an "The following expression could not be parsed because of a syntax error or because it uses an ...