-
Yep. I created a dbxl.domain.com to prep for SSL and it made the installation fail because I did not add it to local loopback at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
All good now. Thanks,
-
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.
-
I use info path 2010. I was able to figure this out by linking rules to a section that has sub questions within it. That only took a life time.
I thought it was maybe not something infopath did but once people confirmed yes I tried some more methods :)
Thanks guys!
-
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.
-
Still shows all of the items. For now I've put a workflow in place that sets a 'Selected' field in the data list and I'm filtering off that. I'll have to play with this more tomorrow, again thanks for your help.
-
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)
-
/dfs:myFields/dfs:dataFields/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.
-
Yes. I have
Name (going to the data list, dataFields: d:SharePointListItem_RW:Name) NotEquals Name (going to data connection to the current list, dataFields: d:SharePointListItem_RW:Name)
I edited my response above to show a little more my process in doing this. Thanks for you help in looking into this!