ever tried working with SharePoint 2010 from your Ipad, and wondered why not everything is working?
It’s because the webbrowser of the Ipad is not supported by SharePoint.
However, you can “fool” SharePoint in making it believe it’s a supported browser.
Follow this link on the Microsoft SharePoint Blog to find out more.
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
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.
Today i wanted to create some managed metadata terms.
Since i don’t want to type als terms, i decided to upload them using a CSV file. So i exported a list as excel. saved it as csv file and tried to upload this file.
That didn’t work. I got an error about the csv-file, but also an alert telling me to use “importtermset.csv” as an example.
A short journey on my filesystem told me that this file can be found at the following location
/program files/common files/Microsoft Shares/Web server Extensions/14/Template/layouts/<languageID>
Where <languageID> would be 1033 in an english environment.
Download the sample file and use it to upload terms to the termstore.
So you want to develop a custom timer job for SharePoint 2010. You looked around in several books and searched some websites.
Ypou created a custom timer job, you deploy it and it seems to be working. However, everytime you adjust the code, no mather what, the old code is run.
You did keep all rules in mind, regarding to building custom timer jobs.
You declared a featuredeactivating, you retreacted the solution.
Still, the original code is run …
The magic behind this is, that although you deactivate and retract the code, the code is still present on the SharePoint server UNTIL you restart the timer job !
So best thing to accomplish a healthy environment for building custom timer jobs is to add 2 pre-build commands.
Open the configuration of your project and add the following 2 rules as a pre-build command
net stop sptimerv4
net start sptimerv4
Now debug your solution again and see that the new code is run !
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.
Finally.
Someone took the effort to take a look into the templates released by Microsoft for 2007 and released them for 2010.
the first thing that caught my ttention, is that i no longer need to installe the core.wsp.
It seems that the converted templates are “clean” templates now.
Take a look here for more information and downloads.
Packages Impacted
The Cumulative Update packages affected are the Server Packages for SharePoint Foundation, SharePoint Server and Project Server 2010, specifically;
- SharePoint Server Package 2394320
- Project Server Package 2394322
go here for more information
Don’t know if you ever heard of the tool, but i like it.
When analysing (big) log files, it’s nice to have a tool that can help you with that.
the log files that SharePoint creates are not very friendly. this tool comes to the aid.
Get it here: http://code.msdn.microsoft.com/ULSViewer
Ever seen this message.
It seems that when you have Office 2010 64bit isntalled, or no office at all, this message is generated by SharePoint when trying to open a list in Datasheetview.
The reason is that it depends on functionality that is part of office 32bit.
So , how can we fix it. According to Microsoft there are 2 methods. Take a look at this page to see which methods.
I think there is only one (is also mentioned on the MS support page). Install the 2007 Office System Driver: Data Connectivity.
After installing everything is working as intendend.
regards,
Eric