But the OBA chapter was already quite lengthy, so we decided that putting it here would be fine. InfoPath is a great tool for turning paper-based forms into electronic forms.
InfoPath collects its data in an XML file, which makes it perfect for interfacing with other applications. It also allows you to update a database either directly or via web services. Combine that with forms services and we have a perfect solution for collecting information via SharePoint and utilizing BDC to read from and populate our LOB systems.
Creating an InfoPath form from a web service allows us to design the form based on the parameters within the web method. The web method would be similar to the code for the web part we created earlier, where you create an object for the information you want to create in the database for example, a customer and then your web method would execute the Entity.
Execute method, as shown in listing AddSale web method calls ExecuteGenericInvoker method. These properties are described in the helper class, as shown in listing The virtual directory is created by using IIS, expanding the website, and choosing Create Virtual Directory from the context menu of the website. Once that has been created, you can launch InfoPath and begin to design your form. Make sure you check the Enable browser-compatible features only check box, and choose the Web Service template, as shown in figure Specify how the form works with the web service.
For now, we only want to think about submitting data to our web services, so just select the Submit data option, as shown in figure Choose Submit data for the web service option in the wizard. Enter the URL of our web service, as shown in figure The URL will depend on your web service. Select the web service method you want to submit data to. You can see our example in figure In the Design Tasks panel, you should be able to see the Data Source panel.
This is shown in figure We want to drag the sale object over and drop it into the Fields area. When we let go of the cursor in the Fields section, we get a number of options for how we want to create and display these controls, as shown in figure The options available when you drag an object from the Design Tasks pane onto the form.
You should choose Section with Controls from the context menu. A repeating table is also created for our SalesProduct s. As with the Document Information panel within Office , when you use the Business Data column, your information workers will be required to key in the identifier. Changing the control for the Identifier column is simply a case of right-clicking it and choosing Convert to Drop-Down List.
We can then configure the drop-down list to read from the database again. To configure the connection, navigate back to the Data Source design pane, and toward the bottom, click Manage Data Connections, as shown in figure Choose the option to receive data and enter the URL for the appropriate web method that returns the list of identifiers, as shown in figure Enter the URL of the web method that returns data for the drop-down list. In our example, we select GetSalesPeople as the operation, and click Next.
On the next form, click Store a copy of the data in the form template. On the final form of this wizard, make sure the Automatically retrieve data when form is opened check box is checked. Then click Finish, as shown in figure Provide the connection a meaningful name for later use. Click Finish to close the Data Connections form. Our secondary data source for use in controls such as drop-down lists.
To enable the form to be used on mobile devices, choose Tools, Form Options, and then check the box for Enable rendering on a mobile device. While in the Form Options screen, click the Compatibility option at the bottom left. Check the box to allow the Form template to be opened in a browser or InfoPath.
The Form Options dialog box containing the compatibility settings. Locate the SalesPersonId text box on your form design and right-click it. On the Data tab, in the List Box entries section, select Look up value from an external data source. The form view will now change slightly. Click the button next to the Entries text box so we can select our group of data, as shown in figure Set the options so that the Value column is set as the identifier, but the Display column is set as the display name.
In figure After it was deployed to SharePoint the remaining steps to complete the deployment occurred without issue. Therefore, the pros are: easy to install, quick to build web parts without programming experience, a support web site that has the type of support material needed to successfully deliver the required output and Lighting Tools post support.
At this time, I had not had to engage the vendor nor had I purchased anything. I ran into an issue, after the web part was built, tying two primary keys together to form a unique column. When this issue was detected and reported back to the vendor, they were able to duplicate the problem and then provide a successful fix within a few days.
I was testing two similar products at this time and the competitor had the same primary key constraint. The problem was reported back to this vendor and to my knowledge the issue still exist. Although this was not needed, I felt it would help support the business case when the time came to execute. Due to managements decision to switch project objectives the requirement for a solid BDC solution was moved to the back burner. Therefore, my experience working with Lightings Tools and their commitment to delivering solid products and a service methodology that sets them apart from other vendors was only positive.
Comments 0. Was this review helpful to you? March 01, However, it can be complex connecting to most data sources. Download A Trial. Book A Demo. Core Features. External Content Types without Code. Multiple Data Sources Supported.
0コメント