auto pop Infopath 2010 form intergrated with SQL 2012 based on logged in user. - InfoPath Dev
in

InfoPath Dev

auto pop Infopath 2010 form intergrated with SQL 2012 based on logged in user.

Last post 08-25-2013 04:31 PM by Patrick Halstead. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 08-19-2013 09:20 AM

    auto pop Infopath 2010 form intergrated with SQL 2012 based on logged in user.

     I am building a form to be used in a workflow in sharepoint 2013 for approval of expenses submitted.

    I have created the form in InfoPath.

    The problem is I want to auto populate the information in the form from an SQL 2012 database based on the user that has logged in.

    I need this for security reasons so others cannot see others information and rate of pay.

    Is this possible. I have tried other methods of doing auto populate based on pulling information from Active directory but I do not have full rights to AD to pull information and i have full control over the SQL 2012 box.

    Any help is greatly appreciated.

  • 08-25-2013 04:31 PM In reply to

    Re: auto pop Infopath 2010 form intergrated with SQL 2012 based on logged in user.

    Hi Richaanth1,

    Sorry for the delay in responding.

    Unfortunately, using BCS on top of the database won't guarantee security.

    You could use a Web service such as Qdabra's DBXL (http://www.qdabra.com/en/products/DBXL.aspx) to easily set this up. There's a generic QueryDB Web service with various methods and lots of information under downloads. The QueryDB Web service would allow anyone to query it, but they would have to know the query syntax. Since a browser form doesn't expose the Web service call, it's practically secure, and more so if the users don't have access to the XSN. However, if they guess the Web service, they could use it to query data. To make this totally bulletproof, you would have to either customize permissions for QueryDB (one of the articles in downloads describes this), or use QueryDocumentNodeSets and store the data to be queried in XML.  We have many customers that use both.

    I think the QueryDB approach is easiest for browser forms since users won't probably guess the Web service and the form would force query using their username. For perfect security, you could customize the QueryDB permissions or convert your data into XML (using our XLStoXML tool) and call QueryDocumentNodeSets.

    We'd be happy to help you implement either solution.

    Regards,

    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.