Issue with filtering a list dropdown and making it InfoPath 2003 Compatible - InfoPath Dev
in

InfoPath Dev

Issue with filtering a list dropdown and making it InfoPath 2003 Compatible

Last post 12-05-2012 12:36 PM by kmellenberg. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 12-05-2012 06:40 AM

    Issue with filtering a list dropdown and making it InfoPath 2003 Compatible

    I had created an InfoPath form using InfoPath 2010 that had a dropdown list (populated from a data connection to a custom SharePoint list).  I then filtered the dropdown list based on a field called Event ID which was populated by a variable that was passed (via the URL) when the form was opened (using a jscript onLoad event).  Everything worked perfectly... then the problems started.  A lot of people in our company still have InfoPath 2003 and 2007 (and, no, we don't have Enterprise edition, so we can't just make it a web browser form).  So, I was instructed to plan for the lowest common denominator.  So, I downgraded all the data connections to 2003 compatible and made a few other changes, and all seemed good... except the filtered dropdown list.  The dropdown list shows up empty.  I can remove the filter, and it shows all the items from the SharePoint list, but if I put the filter back on it shows nothing.  I even just tried filtering based on a certain ID, still no results return.  So, my question is as follows, is it not possible to filter a dropdown list using InfoPath 2003 compatibility?  It seems so simple, but I can't find an answer anywhere.  Does anyone have a solution for this that doesn't involve enormous amounts of custom coding?  I really appreciate any help! 

  • 12-05-2012 12:36 PM In reply to

    Re: Issue with filtering a list dropdown and making it InfoPath 2003 Compatible

    I was finally able to figure out how to solve this issue.  I changed the Event ID field from a text field to a dropdown list populated by another custom SharePoint list.  Then, when the variable value was written to that dropdown field, for some reason, it took the value and would filter the other dropdown based on that specific Event ID.  Not sure that explanation makes complete sense, but it did work!  Anyway, I'm replying to my own post just in case it might help someone else with a similar issue somewhere down the road.

Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.