Hey all,
Today something about search configuration in SharePoint 2007. When you use the AdvancedSearchWebpart, you can set (custom) property definitions. This way you can search directly on one metadata (i.e. "Street"). The creation of these custom properties I will not describe in this article.
When you have created your AdvancedSearchWebpart you can start testing it. You will see that the standard fields ("All words", "Any Words", etc) will give much more results as when you use the custom properties. So when you enter "fleet" in the "All words" field, you will also get "fleetstreet". But when you enter "fleet" while using the custom property, you won't find anything. This is because the option "AllowOpContains" is set to false by default in the XML behind the AdvancedSearch Webpart.
So go to your page and select "Modify shared webpart". Then in the properties tab, locate the properties field and open the XML that is inside. On the top of the XML, you will find the line
Thursday 10 June 2010
Wednesday 19 May 2010
Difference between InfoPath preview and InfoPath form in production
Hey all,
A couple months ago we developed a cascading drop down function in the C# code behind our infopath webform. There is 1 master field (a dataconnection to a SP list) and 1 slave field (dataconnection to a SP list). So when a user selects a value in the master field, only the corresponding values to that master value appear in the slave field. The weird thing was, everything worked fine in the infopath Preview mode. But when we published and activated the form template to our site, it did not work anymore. After analyzing the code we knew that the problem was somewhere in InfoPath. And so we stumbled upon the properties of the 2 fields in InfoPath :-).
When you double click the field in InfoPath you will see a tab called 'Browser Forms'. By default, the postback setting is set at 'Only when necessary for correct rendering of the form)'. Unfortunately this setting did not work for us in production so we changed it to 'Always'. This finally solved the problem. Hopefully this could help any of you in the future.
Thibaut
A couple months ago we developed a cascading drop down function in the C# code behind our infopath webform. There is 1 master field (a dataconnection to a SP list) and 1 slave field (dataconnection to a SP list). So when a user selects a value in the master field, only the corresponding values to that master value appear in the slave field. The weird thing was, everything worked fine in the infopath Preview mode. But when we published and activated the form template to our site, it did not work anymore. After analyzing the code we knew that the problem was somewhere in InfoPath. And so we stumbled upon the properties of the 2 fields in InfoPath :-).
When you double click the field in InfoPath you will see a tab called 'Browser Forms'. By default, the postback setting is set at 'Only when necessary for correct rendering of the form)'. Unfortunately this setting did not work for us in production so we changed it to 'Always'. This finally solved the problem. Hopefully this could help any of you in the future.
Thibaut
Monday 17 May 2010
First Post
This is a first post. This blog will contain messages about my experiences with MS SharePoint 2007 & 2010, Joomla CMS and other stuff.
Subscribe to:
Posts (Atom)