Infopath 2007 webform - InfoPath Dev
in

InfoPath Dev

Infopath 2007 webform

Last post 11-14-2010 05:46 PM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 11-12-2010 05:29 AM

    Infopath 2007 webform

    Hey guys,

    I'm a newbie at sharepoint etc., so I hope you guyes are able to help me...

     

    I have a infopath 2007 form that I have published to sharepoint 2007. Since I need my user to save the infopath form where they currently are, I've used the following code in tip #3 from: http://blogs.msdn.com/b/uksharepoint/archive/2009/02/03/top-tips-for-infopath-form-development-with-sharepoint-part-1.aspx

    Since I applied that code, DataConnections dont work (the code in that link overwrites the dataconnection(s)). I need my form to look into my sharepoint server and add a dropdown box, so that I can choose data. I only need this done for 1 or 2 colums. The data has to have user security, meaning: if user A in sharepoint has access to view data 1 and data 2, he will be able to use the dropdownbox and apply either data 1 or data 2 to the form. If the user doesnt have access, they they will be invisible.Its important that the user doesnt not see what he doesnt have access to.

     

    Is this possible?

    Looking for a fast responce and thanks in advance! :)

    AT

  • 11-14-2010 05:46 PM In reply to

    Hi AT,

    You don't need code to add a dropdown to your form that looks up data from a SharePoint list or library. Just add a data connection and specify SharePoint. You can also add a data connection that populates a dropdown from a database but Web Services are a best practice for querying databases since the default functionality doesn't allow for parameterized filtering of the data (but with browser-based forms, you may not care if it's server-to-server since there's no huge perf disadvantage to populating thousands of items).

    SharePoint does not provide out-of-box item-level permissions. To restrict read access you will have to either move the data to different lists/libraries, or if using a database, use a third-party tool such as Qdabra's DBXL which does support item level permissions on XML files.

    A partial workaround is to create a separate list that specifies access and keep the item-level access info in a column and just filter on that during form open. The user could still navigate to the list and see all the values, but they wouldn't see them from the InfoPath form and if they don't know the URL to the list you may be ok with this solution.

    Best of luck,

     

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