This is call out for some help.
I want to have two seperate word docs running side by side (I have a dual monitor) so I can copy and or compare the two. Before I could im sure in Office 2003. Now I cant in 2007..I want to…
I found a link that shows me how to have them as seperate icons in the task bar but they still run in an a single MDI.
Does this make sense and does anyone have a switch that I need to flick? Im sure it is simple. Help…..
Everyone may know this and it is not a Sharepoint tip at all but an IE tip, I didint know it but thought it was cool so Im posting it and prepared to get told im an IE Noob!
Anyway an easy way to print a document from your libraries is to right mouse click on the document link and click ‘print target’. As shown in the piccy below… I thought it was neat. But as I said it is not a Sharepoint but an IE feature, but handy in Sharepoint.
Yes it has been a while
One thing I try to encourage companies to do who are moving towards MOSS is to use AD groups to define roles for Sharepoint. The only reason really is that there is one place to define security. I am happy for this to debated. Anywayyy
The point is this AD group was wrapped up in a Sharepoint group (which allowed many ad groups to be collected ie admins for each dept). The problem was people in the AD group did not have the approve button on the screen. If I added a user directly to the sharepoint group that user go the Approval capability.
The problem it seemed is a checkbox in the workflow settings for the library. The checkbox is on the second page of the workflow settings…
Assign a single task to each group entered (Do not expand groups)
When this was unchecked the AD user could now approve the pages. The ramifications of unchecking this I have to look at more but it seemed to do the job. I think it handles the users seperatley rather than grouping it all togeather, it sort of makes sense.
If anyone has views on this let me know……
Yes it has been a while.
I have been busy on a few projects inc forms server and a large MOSS project.
Anyway the reason for this post is to highlight something that i wasted a lot of time on with content columns and the meatdata list in the ssp.
The metadata list is used for searching, it allows you to define properties that can be used in the search screens. You can use it like propertytype1:”fred” directly in the search box to only search that property for that value.
Ishai also has poest how to use it for a field in the advanced search screens here…
You can also use them for displaying in the value of the field in the search results the method can be found here….
NOW..the problem
I create a page layout and the created some content columns for it.
I ran a full crawl to load the columns into the meatdata list so I could assoicated properties to them, but they didnt appear….
The short and long of it is it seems after i populated the fields with sample data (ie created a new page based on the contet page i created) i ran another full crawl and slap! there they were.
Im trying to work out why this is, as in my book they should have apparead as the fields have been created. But thinking about it there may be some logic here. When you are creating a page you are only creating a template the fields dont really exist anywhere so they must have some data saved in a site structure in them so they can be used. This is different to adding the columns to a document library as tha list and its fields do exist in a site..
Hope this makes sense if not email me…..
This looks like it is still on track for Sharepoint to obtain this certification (It is from what I understand only for Chapter 2)…
Any way there is more here http://blogs.msdn.com/sharepoint/archive/2007/03/16/status-update-re-dod-5015-2-certification-for-moss-2007.aspx
Personally I do agree with the comment on this entry. It was very short sighted of MS not be more heavily involved with this. A lot of clients hate their existing RM/DM system and would be happy to change but cant change to Sharepoint as they dont have any certification.
Standards are there for a reason (as all developers should know) , they should not be undermined or tacked on as an after thought, they really should be rusted into the application for the go get.
One of the best functions of Infopath is implementing Roles. These allow the InfoPath form to displayed differently (using views) to specific users or groups.
I have recently found out to my grief that Roles are not supported using Form Services! Views can be used but not in conjunction with roles… There is a work around that is not overly glamorous but it seems it will work and it was blogged on the Infopath blog
The link is http://blogs.msdn.com/infopath/archive/2007/01/10/implementing-roles-in-browser-forms.aspx
Im sure there was a good reason for it, as it knows the user who is logged on and can handle views..I am hoping it is a good reason but…
PS Love Form Services SharePoints playing field is getting larger.
This was sent to me by a leading Collaboration and Portal Evanaglist, so I thought I would add it here…
I was trying to use the content query web part on a WSS site but found suprisingly that it does not exist. I found a good site as to what web parts are available in MOSS and WSS (as well as a compaarison with v2).
I really dont know why the content query webpart is not available especially sinceone can use content types in WSS (it seems to me). Can anyone explain this to me.
I suspect I will have to go to using Sharepoint designer to create something.
There seems to be a lot of good excitment about content types and people seem to be pushing them a bit and there a lots of blogs about it.
I left a comment on the blog http://www.sharepointblogs.com/aaronrh/default.aspx where Aaron is writing up about content types. So I thought I would write about the feature that I really enjoy about using content types.
It relates to the use of the Content Type Query Web Part. The webpart allows content types to be aggregated to a single view. The Content Type Query allows you to view all documents (for eg) for a particular content type to be viewed on the parent site no matter what site or sites the content type is in.
A Picture is worth a thousands words as mine dont make sense anyway.
Firstly read the above blog to create a content type and create a few documents and relate them to the new content type (I wont go into detail on how to create a content type as there is alot of blogs about it, but I can if asked).
Move to the site you want the WebPart to view the content, Edit the Page and add the Content Query webpart.
When the webpart is added edit the properties of the webpart. The properties list should look like this
Expand the Query heading which would look like this
I selected the second option to show the items from a certain site and its subsites, select the browse button to select the parent site. The other options will also allow you to select the items from a particular list. Once selected it should look like
We aint done yet. Further down in the Query section you can choose what list types and then what content type from those list types you want to view as shown below
Futher down you can actually filter the values you want further by selecting some filters on the metadata… As well as being able to target them to audiences.
This is great it will allow you to show for example all the approved Policy documents in your clients site structure, without having to navigate to all sites to find all the relevant documents.
So once that is done you should be able to see all documents that match the selected content type no matter what site it is in all rolled up into one view.
It does not stop there you can modify the look and feel of these views as well. I havent done it yet but here are some links to sites that tell you how.
http://www.sharepointblogs.com/vandest/archive/2007/01/08/17581.aspx
http://www.sharepointblogs.com/helloitsliam/archive/2007/01/15/17916.aspx
This post is not of the standard as Liams is but I hope it helps.
Now some may notice a past post about how Im not very keen on rollups. Yes I am changeing a little, but I feel it is most important that when it comes to adding content and seeing the big picture users should be encouraged to go to the site itself.
Firstly I have been quiet because of a move to another company. Its a good one seem progressive, interesting and flexible..all good points. Im largly the Sharepoint, workflow and stuff guy.
Anyway the topic is..
I was setting up a new VM with MOSS, and thinking I was clever (and this was my undoing) and create a seperate instance for MOSS when installing SQL Server 2005, so in the setup of 2005 I created a seperate instance.
When I then ran the Sharepoint Central Admin Wizard I typed in all the details for the instance when creating a new database, and it failed saying it could not locate the SQL Server or the user was wrong or the pasword was wrong etc.
The long and short of it is, use the default instance when install SQL Server 2005 and when using installing MOSS.
And read this series of posts (I am just linking to the page that has the SQL Server entry bit).
http://www.pptspaces.com/sharepointreporterblog/Lists/Posts/Post.aspx?ID=11
Happy New Year guys.
