InfoPath versus Managed Metadata

Instead of using lookup fields i decided i wanted to use Managed metadata fields.

I’ m working on an solution, in which i have to deploy several 100 sites based on a site template.

In the template i have 2 lookup fields, that lookup data. This is working.

But when i need to update the lookup data, i have to do that on all sites, instead of in 1 location.

Managed metadata would be the perfect way to achive this.

BUt i also work with custom infopath forms for several lists, including the list where i want to use managed metadata fields.

And after some strawling around internet, it seems that this is not possible (yet!).

I turns out that this functionality was present in pre-RTM versions of SharePoint, but not in the RTM.

I really hope this will be re-entered with service pack 1

[Ik] filter optie werkt niet — DUTCH ONLY

Als je in een nederlandse SharePoint2010 omgeving gebruik wil maken van de filter [Me], waarbij je dus een lijst kunt filteren op basis van de naam van de persoon die is ingelogd, dan staat er bij het filter netjes, dat in een Nederlandse omgeving hier [Ik] gebruikt moet worden.

Echter, het zal je opvallen dat dit niet werkt.

Vervang echter [Ik] door [Mij] om de filter wel werkend te krijgen.

De omschrijving klopt niet met de werkelijkheid.

How to quickly change the central administration port (2010)

Sometimes, after installing, you find out that the chosen port number is not the best or preferred number. In my case, an application was installed using the same portnumber as central administration.

This can ofcourse be initiated, by the fact that the final portnumber was not yet known at installation time, OR, you have sharepoint 2010 installed as a standalone installation (you are not allowed to choose the admin port in a standalone administration)

So you want to change the portnumber.

Here is how it is done.
Open the sharepoint 2010 management shell ( yep, powershell to the rescue)
type in: Set-SPCentralAdministration
You will be asked the new portnumber.
Or type in : Set-SPCentralAdministration -Port

It will take some time, but then the portnumber of central administration is changed. Done it several times now, sofar, no issues.

Language packs : you just need to know that ….

When installing language pack there is thing you need to know. And that is the order in which to install.

Seems that microsoft is not using the same update functionality as in other updates.
meaning: with most updates it’s sufficient to update only the last service pack, which usually includes all updates.
For example: when installing a new Sharepoint server, and you need to install SP2, you don’t have to install SP1 first.

So what’s the catch with language packs.

Simple: you always install the base installation before installing a service pack.
Say , i would like to install the dutch language pack on my newly installed Sharepoint server (SP2).

  1.  
    1. Install the wss language pack
    2. Install the wss laguange pack SP2
    3. Install the Moss language pack
    4. Install the Moss language pack SP2

If you know the routine it’s simple, but it is sometimes nice to know the routine. 😀

One thing i haven’t checked out.
Do i need to run the Configuration manager after every update, or only ones at the end of all 4 updates?
If someone knows, please let me know

Eric

BDC picker empty…. why ?

Last week i had to do some maintenance for a customer.
During this maintenance we had serious trouble with the bdc-definition.

We started out because the customer had serious performance issues. We decide to change 2 things, just for the test.
One of them was > recreate the Shared Service Provider

During installation someone installed the SSP on the default webapplication (port 80).
So now the SSP is part of the portal.

We decided this was not a good situation and started planning for a migration.
First, gather all current information about the SSP and check what will be lost and what not.

One big thing at this customers place is that we use a BDC that is vital for the working of the portal.

So we tested in a "test environment" and if we export the application definition file and import it into the new SSP , everything should continue to work. (we had some custom pages that rely on this bdc-file)

First issue : When ssp is configured to use with the default webapplication, the only way to add the default webapplication to the new SSP is to remove the original SSP. Hmm, i didn’t like that, because we might need some information afterwards. But we decided to continue and deleted the SSP (remember : removing the ssp from the default webapplication will NOT remove the webapplication, retaining the default portal)

As it seems everything was working, ……. until we checked the BDC .

After re-importing AND resetting the security> the application was not working !
Checking every website in the google universe , we never found a solution.

The bdc-file was imported correctly, we could set permission on it AND we could see all settings.

But when using the BDC-picker tool, our application was not visible.  :-(
At this moment we were getting desperate, until we found somewhere a note of someone (i really don’t know where) that it could be search related.

And one thing we hadn’t done yet was: Start up search. Because of the impact we decided earlier that day to wait until the weekend. We decided to start the search and wait until the weekend passed.

AND GUESS WHAT : the bdc was working as intended.

what is the bottomline of this story : somehow BDC is relying on a working search environment. Some make sure you run a full crawl to the end, before starting to troubleshoot BDC-related problems.

In our situation: the search had never run before. (Search is part of the ssp)

Hope this will help others,

Kind regards,

Eric

Found on internet : free SharePoint Data Zoom Web Part

When browsing the internet i cam across this webpart.
What it said seemed very interesting. Gonna test it later this week if i have time.

What does the website say:

The SharePoint Data Zoom Web Part is a free tool which allows SharePoint users to easily build dynamic, data-driven content on any page. Data from SharePoint Sites, SharePoint Lists and virtually any other source can be aggregated and formatted with ease. Continue reading

Including Codebehind Files in your WSP

Source (and copied from)  : Paul Willen

I really love the codeplex project “WSPBuilder
WSPBuilder makes life for a Sharepoint Developer a lot easier.
The last two weeks we were working on a solution to copy documents from one document library in a site to an other document library. I’ll blog about that later.
But the thing that bugged us that our codebehind page (.aspx.cs) wasn’t included in the solution which resulted in an error while opening the specific solution page.
We didn’t realise that WSPBuilder, by default, excludes these filetypes.
To change these settings you need to go to the Installation Folder of WSPBuilder. This can be found at “C:Program FilesWSPToolsWSPBuilderExtensions
There you will see a file named “WSPBuilder.exe.config”
Copy this file over to the folder where you see the 12-hive in your solution (The obj and bin folders are also in this folder).
Now you need to change the WSPBuilder.exe.config file. Open this file in Visual Studio or notepad and change the TraceLevel key to value=”5″
By changing this key you’ll receive more information what happens when building the WSP.
Move the line
<add key=”Includefiletypes” value=””> which can be found in the commented part right under the TraceLevel key
add the value “cs” for C# or “vb” for Visual Basic to this key. If you want to add multiple values make sure you seperate them with a comma.
The first part of WSPBuilder.exe.config should look like this:

<?xml version=1.0 encoding=utf-8 ?>
<
configuration
>
<
appSettings
>
<
add key=BuildDDF value=false
/>
<
add key=TraceLevel value=5
/>
<
add key=Includefiletypes value=cs
/>
<!–
Optional settings
You can set the arguments in this file or use them directly in the console.
All arguments has a defualt value. See wspbuilder -help

Save this file and now build the WSP like you normally should.
Now the codebehind file should be included into your WSP file.

To check if the codebehind file is truely included into the WSP file rename “yoursolution.wsp” to “yoursolution.cab” and doubleclick “yoursolution.cab”.

There you can see all the files included into the project.

Setting Up FBA in SharePoint

Microsoft has a few posts about how to set up FBA on sharepoint

Good luck