InfoPath Dev

Hi -- Is there conditional formatting on those controls that sets them to read only? I'd probably check for that first....

Hi: First, for item 1 -- this is a common misconception. There is a UI limitation on conditions -- true. IP will only let you add 5. But if you change the first dropdown in a condition to "the expression" you can write your own XPath, like this: my:field1 != '' and my:field2 != '' and my:field3 != '' And so ...

Have you deployed other IP forms (workflow or otherwise) to your production server? I'm wondering if you have a server set up issue, instead of a form issue.

Hi -- What is the syntax for your command? The /id parameter needs to be the XPath to a field in your data source. If you are submitting repeating data, that XPath would be relative (like my:id, if you had a node named "id" in your repeating group). If you are submitting non-repeating data, your XPath will be absolute, like ...

Like I said, this issue gennerally occurs when we have any columns in our SharePoint list that are blank. You may need to try the workaround for mismatched columns posted here.

Are both your servers the same version of SharePoint?

Just wanted to update this with the results from our phone call. An owssvr.dll data connection was added to the form. We used qRules FilterOwssvr and when the field changes, we run the command to return any items from the list that match that number. We added data validation to the field so that it will fail validation if the owssvr.dll data ...

Fantastic, glad you got things working. Trust me, this gets easier with practice -- next time you set up this command you'll be surprised it was such a struggle. :- }

We'd expect the third field to be disabled with the comparision of is not blank -- the comparative is already defined. We select a value in the third drop down when we use something like "equals". Field1 = Field2, for example. But Field1 is blank (is not blank, is present, is not present) is a complete condition. I think ...