InfoPath Dev

Thanks for your response. I looked at using a rule. The problem with that approach is that the conditions on when to apply a rule appear to be limited to <some value> ''is equal to'' or ''is not equal to'' or ''is less than'' etc. <some other value>. I would need the rule to apply whenever the value is *changed*, regardless of how ...

Both ''./'' and ''../'' returned null references. Current() doesn't appear to be allowed in XPath expressions. It says it's an undefined function and asks for an XsltContext to provide a definition. I had hoped to be able to use current() in the context of an absolute XPath. Something along the lines of ...

The ''field'' that changes is actually an attribute within a node of an XmlDocument which is the datasource passed back from a web service. This attribute is the ''sender'' object when the ''on changed'' event fires. The other ''field'' that I need to update within the event handler is a different attribute of the same Xml element. I tried ...

Is it possible to use Integrated Security for a web service used by InfoPath? I have an InfoPath form that uses a web service defined in a UDC in a data connection library. The UDC has UseFormsServiceProxy=''1'' and the roxy account has been setup in SQL Server to have access to the dataset. SQL Server is running on a different machine from the ...

Hi, I have a repeating table with an ''on changed'' event handler for one of the fields in the table. Whenever the value changes, I want to modify the value of a different field in the same row. How can I reference a different field of the current row? (This needs to work in a browser-enabled form, if that makes any difference.) Thanks in ...

Okay, I tried both suggestions and there is no difference. IFS still sends the version updated at the farm level to the browser, and the version that was previously loaded to the Form Templates list to the InfoPath client. Strange.

Another reason I don't think it's a local cache problem is that when I have had a different version cached on my machine in the past, InfoPath pops up a ''Form Template Conflict'' dialog asking me to tell it which one to use. I just got this message for a different form, by the way, and I searched my hard drive for the xsn file, but couldn't find ...

I thought that might be a possibility so I scanned my hard drive for *.xsn files and didn't find anything that appeared to match. Is there a common place where InfoPath form templates would be cached locally? On the other hand, if it *is* a local caching issue, then loading the new version directly to the Form Templates list probably wouldn't ...

Here's what I've figured out so far about the web site serving up the old form: I publish the new version to a directory that is available to the admin account. Then I go into Central Administration | Application Management | Manage Form Templates and I upload the new version choosing the option to upgrade the form template if it already exists. ...

Thanks for your response! I tried it adn it appears that there are multiple, separate problems. 1) In debug within Visual Studio, the format of the fields match and it works. 2) After publishing to OFS and allowing the browser to open the form in the InfoPath client, I get the *old* version of the form without the new fields I added! ...