Issue List with HX Through InfoPath? - InfoPath Dev
in

InfoPath Dev

Issue List with HX Through InfoPath?

Last post 04-19-2006 10:15 PM by Patrick Halstead. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 04-18-2006 10:49 AM

    Issue List with HX Through InfoPath?

    I would love to get a printout of a Sharepoint Issue List that has each issue with its history records as child records. Is there a way to do that with InfoPath?

    Thanks,
    Deb
  • 04-19-2006 03:48 AM In reply to

    Re: Issue List with HX Through InfoPath?

    You may need to write a web service to access that data and then have InfoPath call it.
    Jason
    http://www.k2distillery.com/
  • 04-19-2006 08:33 AM In reply to

    Re: Issue List with HX Through InfoPath?

    Why couldn't you use the Master/Detail control and have it link by the Issue ID key field? I've tried to drop in the Master/Detail control, then change the binding of the "master" part of the control to point to my Sharepoint issue list. The problem is that when I do that Master/Detail tab of the Repeating Table (master control) properties dialog is disabled -- every field on the tab is disabled so I can't set it as "master" in order to then change the properties repeating section below it to be "detail."

    I've never used master/detail before, so I'm not sure of even the thought process to troubleshoot this. The Master/Detail tab is enabled if the data source is the form itself, but if I connect it to a Sharepoint list, the Master/Detail tab becomes inactive.

    Thanks for any help

  • 04-19-2006 10:15 PM In reply to

    Re: Issue List with HX Through InfoPath?

    Hi Deb,
    I don't remember, but doesn't the SharePoint list adapter load the data as one collection (flat list)? If so, I'm guessing it's a schema issue. Master/Detail wants you to specify two collections. You could add some code to move the history records into a separate group and then set it up.

    One more note: master detail only works on main data source, so you will have to move the data into your main data source to get it to be enabled in the content model editor (data source pane).
    Patrick Halstead
    Project Manager at Qdabra
Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.