Deploy InfoPath 2010 list form with query filter

What is this about? Well, I needed a custom SharePoint list, with a customized InfoPath form for it, and this form had to read one parameter from the URL. Nothing complicated at all, there are many posts on how to customize forms for SharePoint lists and how to pass an URL parameter for this form. But in my case I needed it all deployable with a package and this puts another level of complexity. Therefore I decided to wrap the procedure in the post below - to make sure that I don’t forget it after a while.

SharePoint No-Coding: Parameter Check

This is the third post from ‘No-Coding Solutions’ series. The first post showed you open any InfoPath form on a custom SharePoint web part page. The second one was on how to customize display values for a form. In this one will show you how to implement simple parameter check on your site pages. Well, this is not exactly no-coding, since the check itself is done with jQuery script, but still the approach is pretty straight-forward and does not require deployment, solutions creation etc. – just a JS file that is included to the pages.

SharePoint No-Coding: Custom values for view form

This is the second post from ‘No-Coding Solutions’ series. The first post showed you how to open any InfoPath form on a custom SharePoint web part page. In this post will show you how to customize display form for a list, and more specific – how to customize display value for a field.
The specific task I had is to show ‘No (click edit to modify)’ or ‘Yes (click edit to modify)’ as display value for a Boolean field when item is in read-only mode. As you know, Boolean fields are usually displayed as a checkbox in InfoPath forms. Of course, you can modify the control type to drop-down, radio buttons, text box, and other. But the type of control you select will be used across all views of the SharePoint form – new, edit and display. In my case I needed to have a checkbox for edit and new, and a simple text for display.

Two of my previous posts ...

Here is a reference to two of my previous posts - I don't want to loose or recreate them :)

SharePoint tips: Working in localized environment
This is a post I created after having problems with a SharePoint (WSS3/MOSS 2007) solution deployed on a localized environment.

K2 [blackpoint] & Web service
This post shows how to consume a web service from K2 [blakpoint].

SharePoint No-Coding: Open any InfoPath Form

On the latest project I was working, had to develop a SharePoint solution by using only InfoPath and SharePoint designer as development tools. Well, at first felt a bit upset, still I am a developer, and someone just took away my most favorite toy – VisualStudio. After a while, accepted the situation as a new challenge and this made things look better. In this, and the posts that will follow will try to cover some interesting moments from the development process on a no-coding solution for SharePoint 2010.

Custom sitemap in SharePoint

In the story today will show you how a sitemap can be used with a SharePoint site to create a custom navigation control for SharePoint.

Scenario

I am having a website, that has few application pages. Those pages have to be linked via custom breadcrumb control. Let's say that this is project management site, and the pages are: Projects.aspx (the list with all available projects), ProjectDetails.aspx (details for a single project), ProjectExpenses.aspx (the expenses details for a selected project) and ProjectResources.aspx (list with employees that are assigned to the selected project). My breadcrumb should have 3 links only: Home -> Projects -> Project Details, but when user opens expenses or resources links, he/she should be able to navigate back to the current Project Info page by clicking on the breadcrumb link.

Save InfoPath Attachment via K2 SmartObject

If you have met K2 during your work, you will know how important is to keep K2 DB clean and less-busy in order to improve performance in workflow execution, reporting etc. One of the ways to improve the performance is removing all attachments from InfoPath forms before they reach to K2 DB, because InfoPath data will be extracted, saved and passed back to the customer by K2. Here is how this can be done (note that I am talking for K2 [blackpoint], but more or less the same procedure can be used for K2 [blackpearl] as well).