Build a Simple Language Translator using InfoPath and No Code – Part 1 of 2

One of the most useful features of InfoPath, is the ability to easily set up and use data connections from so many sources. Using data connections to web services, InfoPath can be used to create a form that passes data onto a third party website where the data is acted upon in some way and a response passed back to the end user.

A simple, yet practical example of this is this simple text translator. This was built on the back of a customer request to have forms available in multiple languages. No code is used in this development, but we do make use of the “Rules” functionality by which Business Logic and in-form workflow can be built.

While the result of some InfoPath experimentation presented here will not be putting any multi-lingual technical translating staff out of business I’m sure you can think of other applications which could benefit from a Web Service interface such as this.

Ok – so how do you go about creating a translation form? It’s as simple as baking a loaf of bread, so let’s start by looking at the ingredients we will need!

Recipe for InfoPath Translator – Serves 5 ( English, German, Spanish, French and Italian!)

Ingredients:

Instructions

  1. In InfoPath 2010 Designer create a new Blank Form and create a table with six rows and two columns
  2. Create a Data Connection – Not built one of these before? – Don’t worry a wizard makes this really simple!
    1. From the ribbon select Data / From Web Service /From SOAP Web Service and enter in the web service URL as below:

3.Now from the list of Services select Translate

4. On the next screen you will see a list of Parameters that are used by the web service – Enter your Bing Application ID here by using the Set Value button (You do have an app id don’t you? If not, sign up at http://www.bing.com/toolbox/bingdeveloper/) In the content type and category parameters set the values to ‘text/plain’ and ‘general’ respectively

5. The next screen should be skipped – hit the Next button

6. Now we are on the final screen for our data connection set up. Deselect the “Automatically retrieve data when form is opened” check box – Best practice for forms is to only use data connections when needed, and we will only be calling this service when a button is clicked

Build a Simple Language Translator using InfoPath and No Code – Part 2 of 2

7. After you have finished your data connection you will have two data references in your InfoPath project – Main and the Translate service you just created will be labelled a secondary connection…

You will see from the view above that the data connection is in two parts “query fields” and “data fields”. Put simply, the query fields enable you to pass information through the data connection and the data fields represent what you get back!

8. Enter text labels in the left hand column of the table you created in step 1 and drag the text field and the TranslateResult fields from the fields pane on the right into the form layout 

9. Now switch to the Main Data view in the fields pane and add two dropdown list controls and label LanguageFrom and LanguageTo… This will create two extra field references in the Myfields folder of the Main view of the Fields pane as in the screenshot below. These two fields will be used to provide data to the “From” and “To” query fields of the Translate data connection

10. Enter the values as in the screenshot below to the Drop Down List Box properties for the LanguageFrom field

11. And enter the values as in the screenshot below to set up the LanguageTo Dropdown List Box properties: Yes, pretty much identical to the LanguageFrom field!

For this example I have only added five languages and their associated codes , but you can add additional languages to these controls if they are supported by the Microsoft Translate API.

12. Now finally we just need to add a button to our form and attach some logic to the button so that when pressed the following will happen:

  • Populate the “From” query field of the Translate data connection with the value selected in the LanguageFrom Dropdown List
  • Populate the “To” query field of the Translate data connection with the value selected in the LanguageTo Dropdown List
  • Run the web service to see the translate result

This is achieved simply by adding a button from the Controls section of the Home ribbon and adding a Rule with three actions as below:

The three actions are

  1. Set a fields value (select the “from” field from the Translate data connection and make equal to the LanguageFrom field from the Main data connection)
  2. Set a fields value (select the “to” field from the Translate data connection and make equal to the LanguageTo field from the Main data connection)
  3. Query using a data connection (select the Translate data connection)

Conclusion

Well, that’s all there is to it! Test the form in preview mode and add some simple sentences and combinations of From and To languages. If you have been successful, you will appreciate how InfoPath can be used to address some fairly complex Business scenarios in a straightforward manner with NO CODE REQUIRED!
J

Do you have any similar examples of code free web service based InfoPath development – we’d love to hear from you!

ISC London: Quickly Delivering Business Applications on SharePoint 2010 Session

I’m looking forward to talking about quickly delivering business applications on SharePoint 2010 at The International SharePoint Conference London 2012 in April. I’ll be co presenting with one of our customers.

When the tools available in SharePoint 2010 are used appropriately, it can be phenomenally productive. In my session, we take a look at how it was possible to build a fully featured business application, with forms, workflow and reporting in a matter of days – and without writing any code. Using Purchase Order management as an example, I’ll review the business requirements and explain why SharePoint was chosen for the application, before getting hands on with some demos and looking at how SharePoint capabilities were leveraged to quickly deliver the application at an engineering company.

Full agenda of speakers can be found here. It’s shaping up to be another excellent event!

Register ICSLondon

Click here to regsiter: http://www.internationalsharepointconference.com/Pages/Register.aspx

I Love PointBeyond

Keep seeing these labels. Our fame is spreading!

Back to PointBeyond web site

SharePoint 2010 Standard or SharePoint 2010 Enterprise?

I’ve been speaking with IT directors/CTOs at two different large organisations in the past week. Both are in similar positions in that they are considering moving to SharePoint 2010, and need to decide whether or not to go for Standard or Enterprise edition.

One of the big challenges that they both faced was knowing the capabilities of each product. One of them was seriously considering purchasing an expensive BI solution even though they have quite modest BI needs. They and their teams were simply unaware that there is BI capability within SharePoint 2010.

The second challenge was around the departmental versus organisational view of the world. What do I mean by that? In both organisations, departments were commissioning their own business applications. Most of the time these applications were custom coded, and although they sometimes integrated with SharePoint, the integration only meant display of the custom application within a SharePoint site. There are several problems with this approach:

  • Independently implemented applications leads to siloes of information, inconsistencies in functionality/look and feel, and a larger training requirement
  • Areas of common functionality were being “reinvented from scratch” each time
  • There is always risk involved in any custom development project
  • Perhaps most critically of all: In most cases the applications in question could be quickly delivered using the composites capability of SharePoint 2010 Enterprise. The cost of a single departmental level application was typically less than the cost of implementing SharePoint 2010 Enterprise. However, taken together the cost of implementing all of the applications together was significantly more than the cost of the Enterprise licences.

In this situation a decision to move to SharePoint 2010 standard would have been a bad strategic decision. It would have resulted in business applications being delivered more slowly, at higher risk and cost, and with less consistency and integration with each other.

So when making the decision between Standard and Enterprise it is essential to have all the facts to hand. In particular:

  • What are our business requirements and priorities?
  • What are the capabilities of the different editions, and which of these capabilities aligns with our requirements?
  • What is going on within business units, departments, or teams? In particular would putting in a platform to facilitate quick delivery of applications with little or no custom coding be cheaper in the medium to long term than custom code or purchase of individual solutions? With the people I was speaking to, a back of the envelope calculation indicated a payback time of 6 to 12 months.

If more investigation is needed, it is worth knowing that a 180 day evaluation copy of SharePoint 2010 Enterprise can be downloaded from the Microsoft web site. This can be used for a pilot before committing to licence purchase. We have helped several organisations with this low risk approach.

Back to the PointBeyond web site.

SharePoint and Project Server for New Product Development

Companies are increasingly looking for efficiency gains with New Product Development and yet struggle to find a tool that can accommodate their supporting business processes. This is because each company’s culture is different and only a set of tools that can quickly adapt to support their unique Business Processes and ways of working can add benefit.

New Product Development  is the art and science of bringing products to market, from idea generation through to prototyping and the first production run, and can be considered from two viewpoints – Strategic and Tactical. Project Server which is built on the SharePoint Enterprise platform is an ideal choice for meeting both the Strategic and Tactical requirements of a New Product Development system

Strategic:  
The strategic viewpoint looks at the selection and approval process to ensure that products with the best potential are brought to market as efficiently as possible.

Project Server is ideally suited for the development of a Strategic New Product Development Framework offering the following features out of the box:

  • A  Stage gate approval model – used to ensure that the right products are passed through for development. An example five phase workflow is provided or workflows can be configured using Visual Studio or third party products such as Nintex Project Server Workflows.
  • Portfolio Analysis – Set strategic drivers and objective criteria, which assist in scoring each product proposal, and help determine a mix of new products that is most aligned with company strategy
  • Create product focussed projects – assign resources (people and materials) to these projects and view resource commitments across a portfolio of projects / new products. Avoid resource bottlenecks
  • Use Project Plan schedule templates to set up predefined high level plans for new products. Develop your own best practice templates through your company’s experience and create effective development pipelines
  • Manage Assumptions, Risks and Issues across all product developments
  • Reporting – Harness the capabilities of Project Server and SharePoint Business Intelligence with powerful tools such as
    • Reporting Services for database reports,
    • Excel Services for dynamic charts and data grids or OLAP reporting
    • Visio Services for colourful dynamic data driven diagrams
    • Performance Point Services for the creation of Scorecards and Dashboards with multi-dimensional “slice and dice” data analytics

Tactical
The Tactical viewpoint concerns the day to day practicalities of  introducing a new product to market, and includes activities such as packaging /design workflows and the set up of design workshops.

For the tactical activities, SharePoint (which is part of a Project Server installation) has many features which enable the rapid creation of a New Product Management System including:

  • Create collaborative workspaces for product based teams to share and develop ideas
  • Utilise the integration between SharePoint and Project Server to raise issues and risks at a local level for visibility and review by senior portfolio managers
  • Create document approval workflows for key documents such as specifications
  • Create record centres for key documents with features such as version and archive control
  • Create wikis to capture and develop team generated ideas or use team blogs to update others on progress
  • Create custom list templates and custom electronic forms either Out of the box or through enhanced toolsets such as SharePoint Designer or InfoPath and set validation rules or attach the forms data to a workflow

Back to PointBeyond website

Multimedia Learning Centre Gets The Point Across

Every organisation knows the benefits of providing high quality, easily accessible information to employees. However the reality is that training materials often sit on corporate intranets or in email inboxes without ever being looked at by staff.

A partnership between SharePoint application specialist PointBeyond, and multimedia experts Just90.tv seeks to change that. They have created a package to change training material, organisational policies, and procedures into engaging, easily digestible 90 second video bursts. The videos are then kept in a specially designed SharePoint multimedia learning centre, which can be either on premise, or in the cloud.

Why 90 second video bursts? Richard Adams of Just90.tv explains: Click here to watch video

Just90.tv was created to reflect a world where people are busier, seem to have less time and yet have more to do and must perform at a higher level. The growth and increased use of video streaming means that there are ways to learn that respect the way we live now. Personal development and gaining new knowledge does not have to be squeezed out of the diary.

The multimedia site is easy to use and manage, especially if users are already used to SharePoint. Documents and online questionnaires can be associated with videos, so for example a new starter may watch a video on a procedure, download a checklist to follow, and take a short test to confirm that they understand the procedure. Reporting allows management to see what is popular and who is viewing what.

Multimedia Learning Centre

Two Out of Three Organisations Say Growth and Profitability Constrained by Existing IT, According to Survey of IT Leaders in New Whitepaper from PointBeyond

PointBeyond are proud to announce our latest whitepaper The Business Applications Deficit is now available for download.The Business Applications Deficit Whitepaper

Research led and technology neutral, the whitepaper makes compelling reading for both IT and business leaders and is supported by headline facts such as 66% of organisations surveyed believe that technology is constraining their growth and profits, and 52% regret the decision to select at least one application and are now living with the consequences.

In September 2011, over 200 IT decision makers from large organisations were invited to participate in PointBeyond’s Business Application Strategy Survey, answering a series of detailed questions on the issues impacting the delivery of business applications in their organisations.

Based on the survey responses, The Business Applications Deficit, provides expert analysis and commentary on the results.  It introduces the new concept of the Business Applications Deficit – the gap between the applications businesses need to be successful and competitive and the reality they are facing in today’s challenging environment.

Applications are essential to running a successful business and in the whitepaper PointBeyond provides further guidance and information on:

  • Getting business application delivery right first time
  • The issues facing IT decision makers in large organisations
  • The importance of having an application strategy
  • Improving the success rate of business application projects
  • Delivering applications efficiently and cost effectively

Organisations have never been so spoilt for the choice of tools with which to deliver their applications. However, in the absence of an application strategy and without being able to measure the ROI of application projects, PointBeyond suggest that many organisations are compromising their ability to succeed. By contrast, organisations that think and act strategically will engage more effectively with new technologies and be able to deliver better applications more quickly and at lower cost.

You can download your copy of The Business Applications Deficit here.

Cascading Dropdowns in InfoPath 2010

This is a robust way to implement cascading (sometimes called nested) dropdowns in InfoPath 2010, that also works with InfoPath Forms Services in SharePoint 2010. The approach in this article expands upon the demo that I gave at SharePoint Saturday UK on 12 November 2011.

There are numerous other blog articles out there explaining how to achieve cascading dropdowns in InfoPath, and I have had varying degrees of success with them. Some work okay but are complex, others seem to be a bit buggy. So the approach I take here will (hopefully!) provide a good solution – but comments welcome as always!

Objective: On an InfoPath form I wish to have an arbitrary number of dropdowns. Selecting an item in the first dropdown determines the items available in the second, selecting an item in the second dropdown determines the items in the third, and so on. A user should be able to go back to a previous dropdown and make a change. Users should be forced to select in order, so that until an item in the first dropdown is chosen, the second dropdown is disabled, and so forth.

Preparing the Data Source

For the example below our data source for the dropdown items is SharePoint lists. However the method could be modified to use other data sources such as a database or a web service. In the dropdowns users will select a region, then an office, then a team.

I have created three lists for the example and will create three dropdowns.

The “Regions” list is a custom list with no extra columns added. It is populated as follows:

The “Offices” list is a custom list with one extra column added, which is a lookup to “Regions”. It is populated as follows:

The “Teams” list is a custom list with one extra column added, which is a lookup to “Offices”. It is populated as follows:

Designing the InfoPath 2010 Form

Launch InfoPath 2010 and create a new blank form (or open the form to which you wish to add your dropdowns).

Add three text fields as follows:

Repeat for “Office” and “Team”.

Now drag-and-drop each field onto the form.

Without any formatting your form will look like this:

Right-click each textbox and choose “Change Control > Drop-Down List Box”.

The form will now look like this:

Now we need to create three data sources, one for each dropdown.

Click on the “Data” menu at the top of the window, and then “From SharePoint List”.

We’ll do “Region” first.

Enter the location of the SharePoint site. Note that the lists can be on a different site to the site that our form is going to end up in.

Click “Next”. Select the “Regions” list.

Click “Next”. Select “Title” and change the sort order to “Title”.

Click “Next”. Click “Next” again on the offline option page.

Accept the options on the final page.

Click “Finish”.

Now repeat this process for Offices and Teams, but with the following two changes:

First, include the related column in the fields to select from. So for Offices the wizard will look as follows:

Teams will look similar, but with the “Office” column selected.

Second, uncheck the “Automatically retrieve data when the form is opened” option. For all but the first dropdown, we won’t be getting the data until the previous dropdown is changed.

Ok now we need to hook up our dropdowns to our data sources. Right click the “Region” dropdown and choose “Drop-Down List Box Properties”. In the “List box choices” section choose “Get choices from an external data source”. Make sure the data source is “Regions” and amend the “Display name” field to Title (using the button on to its right) so that the form looks as follows:

Click “OK” and repeat for the “Office” and “Team” dropdowns, choosing the appropriate data source in each case. Make sure the “Value” and “Display name” fields are always correct. So for “Office” the form looks as follows:

If you preview your form at this point then the “Region” dropdown should be populated but the other two should not.

Finally we need some rules to make it all work.

Select the “Region” dropdown, then on the “Home” tab at the top, choose “Manage Rules”.

On the “Region” dropdown we will add a single rule. Choose “New, Action”.

Change the “Details for” to read “Populate Offices”.

Now choose “Add, Set a field’s value”.

The field we will set is the “Region” field on the “Offices” data connection. This will act as a filter on the list of offices, only displaying those that have the correct region.

Click the button to the right of “Field”. Change the dropdown at the top to “Offices (Secondary)” and expand “queryFields” to select “Region”.

Click “OK”. Now click the “fx” button to the right of the “Value” field. Click “Insert Field or Group…”

Choose “Region”.

Click “OK”. The formula shows as follows:

Click “OK”.

Now add another action to the rule, again to “Set a field’s value”. This rule will simply set the “Office” field to blank, to clear out any old values.

Now add an action to “Query for data”.

Set the data connection to “Offices”. Click “OK”.

If you preview your form now you should be able to select a region and see the correct list of offices populated.

Now we set up the rules on the Offices dropdown. Select the dropdown and click on “Manage Rules”.

Add a new formatting rule:

Change the details to “Disable if Region Blank”. Click on “None” under “Condition. Set the condition as follows:

Select “Disable this control”.

Next add a new action rule.

Call this rule “Populate Teams”.

Add an action to set a field’s value.

Pick the Teams/Office query field.

Set the value equal to “Office”.

Add another action to set “Team” to blank.

Add a final action to query the teams data connection.

Finally add a formatting rule to the “Teams” dropdown. This rule will disable the control if “Office” is blank.

Now preview your form and check everything works!

Provided all is okay you can publish your form. If you want to use InfoPath Forms Services within SharePoint 2010, it should work fine.

Back to PointBeyond web site.

When Collaboration Becomes a Commodity, How Do You Choose a Platform that Adds Value?

When SharePoint was first released, the idea of a web site where users could upload documents, and manage their own lists, calendars, etc was quite novel to many people. It was, as we all know, a runaway success and SharePoint has been widely adopted across many organisations. Many other software vendors, as well as Microsoft, also provide collaboration platforms.

Now more and more collaboration platforms are becoming available, with cloud offerings such as Box.net, Huddle, Google Docs and many others being added to the mix.

One of the differentiators of SharePoint 2010 is that you can use it as a platform for the delivery of business applications, as well as for straightforward collaboration. Even the entry level SharePoint 2010 Foundation gives you:

  • Out of the box and custom lists and views. These lists can be linked to deliver simple data driven applications
  • Built in security model. You can set permissions to control who can see and do what
  • Ability to build workflows using SharePoint Designer
  • Forms that use the InfoPath client (part of some editions of Microsoft Office)
  • Core Business Connectivity Services functionality, for interacting with data in other systems
  • An open platform for enhancement through custom development and integration with other systems
  • Possibility to use SQL Server Reporting Services in SharePoint integrated mode to build reports and dashboards

Once you move up the licencing scale to SharePoint Server 2010 Enterprise, you get the “Composites” functionality that adds significantly to the toolset available for building applications. This includes

  • Excel Services, for interacting with and publishing parts of Excel spreadsheets through the browser
  • InfoPath Forms Services, that takes InfoPath forms and renders them in the browser
  • Visio Services, for publishing data driven diagrams
  • Access Services, for converting Access Databases to SharePoint lists and forms, and allowing browser based interaction
  • Enhanced Business Connectivity Services
  • Various web parts and out-of-the-box workflows

This rich toolset for quickly delivering business applications sets SharePoint apart from many collaboration platforms, and it should be a major consideration for many organisations when choosing a collaboration platform.

Our technology neutral white paper, “The Business Applications Deficit” looks at the drivers behind the need for business applications, and the challenges faced by organisations in implementing applications. To receive your complimentary copy please click here.

Next Page »



Follow

Get every new post delivered to your Inbox.