Defaults not populating from Secondary DS - InfoPath Dev
in

InfoPath Dev

Defaults not populating from Secondary DS

Last post 06-19-2006 11:29 AM by Quin. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 06-19-2006 09:58 AM

    • Quin
    • Not Ranked
    • Joined on 06-19-2006
    • USA
    • Posts 3

    Defaults not populating from Secondary DS

    Problem Using SharePoint Mult-Page Meeting Workspace Document Library columns as Secondary Data Source in an InfoPath Form.

    I have fields on my main form whose default values are set from a Secondary Data Source. These fields should be populated automatically when the form opens (“Automatically retrieve data when form is opened” is checked). When I#%92m in Designer and I preview the form, all the fields populate perfectly. But, when I save and publish the form and then go to open it, the fields are blank (or zero). After much testing (adding Refresh buttons, Query Buttons, different SDS#%92s , creating lots of little “test forms”, etc) I was able to determine that this only happens when the Secondary Source is a Document Library in a Meeting Workspace. Regular Lists work fine and Document Libraries that are part of a Team Site work as well. Each time, if I re-open the form in Designer and “modify” the SDS connection, the fields faithfully populate in Preview. Has anyone else had this problem and is there a workaround? I would like to keep the forms and the SDS together in the same Meeting Workplace sub-site. The Meeting Workplace (Multi-Page) template was selected for the sub-site because it#%92s perfect for organizing the content of this project. Each Tab is dedicated to a different KPI area within the overall project.
  • 06-19-2006 11:29 AM In reply to

    • Quin
    • Not Ranked
    • Joined on 06-19-2006
    • USA
    • Posts 3

    Re: Defaults not populating from Secondary DS

    I did some more testing on this. My secondary data source is actually a list that is created by promoted fields from another Infopath form. When I created a 'normal' custom list and applied it as the secondary data source, it works perfectly. So, the issue may be tied to using InfoPath-promoted fields as a SDS.
Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.