-
The new data connection you added will have query fields and data fields. Add a rule to set the query field for ID in the new data connection to the ID field in your main data source. Then add a rule to run the query.
-
You are having an issue because this is a list form and attachments are handled differently there - you'll notice the attachments field isn't repeating. If you attach some files in preview and go to File > Save As and look at the XML, you'll see that there is nothing stored in the attachments node.
The only work around I can ...
-
Just wanted to update this thread - it appears the issue had to do with special chars in the file name. As a work around, the GetAttachmentAttribute command can be used to get back the filename, and then the /namexpath parameter can be used in SubmitToSharePointList to submit a name without special characters. I'm going to add a bug to our bug ...
-
Found one more approach:
not(d:Title = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:Select)
I've also attached a sample based on this thread.
-
Cool. I'll put a sample up later today that uses an XML data source for the dropdown so you can see how the general idea works in a sample.
-
Hi - I think this has been resolved, right? You emailed support that it was a local loopback issue that was blocking installation?
-
Try this? not(d:Title = current()/preceding-sibling::my:SharePointListItem_RW/my:Select)
-
Okay, I had this wrong - http://www.infopathdev.com/blogs/matt/archive/2006/05/23/Filter-a-Repeating-Drop_2D00_Down-List-on-Previous-and-Future-Selections.aspx got me squared away. What is the full XPath to the field bound to the dropdown? You can right click the field in the Fields task pane and select Copy XPath.
-
Okay. Is "InfoPath Main" the data source for your dropdown?
-
Can I see a copy of your form? Under the Options tab you can attach a file.