The Best Blog for Customization using JQuery
http://weblogs.asp.net/jan/Default.aspx?PageIndex=4
Thanks to Jan Tielens
http://weblogs.asp.net/jan/Default.aspx?PageIndex=4
Thanks to Jan Tielens
Wednesday, August 31, 2011
Querying SharePoint List Items using jQuery
A sample of how you can make use of the jQuery Javascript library in your SharePoint sites. This example uses SharePoint’s Lists.asmx web service to retrieve all the list items of a specific list. Let’s use jQuery in a plain Content Editor Web Part.
To try this sample navigate to the home page (usually /default.aspx) of a SharePoint site that has a list with some list items in it, in my code I’ll use the Task list of a plain vanilla Team Site. Switch the page to Edit mode (Site Actions, Edit Page), and add a new instance of the Content Editor Web Part to the page. In the properties of that web part, copy and paste the following code using the Source Editor button.
<script type="text/javascript" src="http://jqueryjs.googlecode.com/files/jquery-1.3.2.min.js"></script>
<script type="text/javascript">
$(document).ready(function() {
var soapEnv =
"<soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'> \
<soapenv:Body> \
<GetListItems xmlns='http://schemas.microsoft.com/sharepoint/soap/'> \
<listName>Tasks</listName> \
<viewFields> \
<ViewFields> \
<FieldRef Name='Title' /> \
</ViewFields> \
</viewFields> \
</GetListItems> \
</soapenv:Body> \
</soapenv:Envelope>";
$(document).ready(function() {
var soapEnv =
"<soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'> \
<soapenv:Body> \
<GetListItems xmlns='http://schemas.microsoft.com/sharepoint/soap/'> \
<listName>Tasks</listName> \
<viewFields> \
<ViewFields> \
<FieldRef Name='Title' /> \
</ViewFields> \
</viewFields> \
</GetListItems> \
</soapenv:Body> \
</soapenv:Envelope>";
$.ajax({
url: "_vti_bin/lists.asmx",
type: "POST",
dataType: "xml",
data: soapEnv,
complete: processResult,
contentType: "text/xml; charset=\"utf-8\""
});
});
url: "_vti_bin/lists.asmx",
type: "POST",
dataType: "xml",
data: soapEnv,
complete: processResult,
contentType: "text/xml; charset=\"utf-8\""
});
});
function processResult(xData, status) {
$(xData.responseXML).find("z\\:row").each(function() {
var liHtml = "<li>" + $(this).attr("ows_Title") + "</li>";
$("#tasksUL").append(liHtml);
});
}
</script>
$(xData.responseXML).find("z\\:row").each(function() {
var liHtml = "<li>" + $(this).attr("ows_Title") + "</li>";
$("#tasksUL").append(liHtml);
});
}
</script>
<ul id="tasksUL"/>
On the first line the jQuery library is loaded from googlecode.com. To make this your, your client browser needs to have Internet access of course. Alternativly you can host the jQuery library yourself (see my previous examples) or even load the jQuery library in every page using the SmartTools.jQuery component. After that a function is attached to the jQuery document ready event. In this function the SOAP envelope message is constructed (the soapEnv variable). If you’d like to see the code getting list items from another list than the Task list, you’d have to change the listName element. The second part POST-ing the SOAP envelope to the web service by using jQuery’s ajax function. When the web service comes back with the result, the processResult method is called. In this function a loop is created over every row element (in the namespace z). Notice that "z:row" escapes in Javascript to "z\\:row". For every row element a new li HTML element is added to the ul element with ID tasksUL. And that’s it! You can see the result in the screenshot below.
Creating a Custom Theme for SharePoint 2010 using PowerPoint
Create simple yet professional-looking branding for our client’s new SharePoint site, avoiding CSS and Master Page edits where possible. I needed a set of custom colors, to match the customer’s website palette as closely as possible, which is why none of the preinstalled SharePoint themes worked for our needs.
According to Technet: “Themes enable lightweight branding of a SharePoint Server 2010 site by allowing a site owner or a user with designer rights to make changes to the colors and fonts of user interface elements of a site. Themes are applied and customized directly in the user interface, and do not require knowledge of cascading style sheets or master pages.”
A common analogy is that themes are like the paint on the walls of your home. You can browse the predefined SharePoint themes under Site Actions > Site Settings. Under Galleries, select Themes.
Let’s dig into how it’s done. I’ve divided the process into five major steps: A through E.
For this project, I used my SnagIt Editor to detect the RGB #s from our customer’s website, so I had a list of colors to start from.
Alternatively, you could choose a theme to start with from the Colors drop-down – if you don’t care about looking closely at the colors in the body of the PPT.
2. Ensure you have your “starting point” theme selected. In the following screen shot, I have the “Aspect” theme currently selected.
If you want to use one of the built-in themes as is, without customizing individual colors, then skip to Step C. The built-in themes within PowerPoint are different than the predefined themes in SharePoint, so this would be a perfectly valid solution.
If you want to customize the built-in theme: Click the Colors drop-down, then choose “Create New Theme Colors.”
3. From this window you are able to customize 12 colors: 10 theme colors & 2 hyperlinks.
Theme colors: The top 4 colors – Dark 1, Light 1, Dark 2, and Light 2 – are used significantly throughout SharePoint, for both text elements & background elements, so these should be selected pretty carefully. I recommend that you stick to using dark or light colors as it suggests for each name - I tried to invert them in order to accomplish what I wanted with no success.
Name: This is the name which will be used within PowerPoint. You’ll see it listed as part of Custom Themes in the Colors drop-down, so you can use it again in the future.
Save button: This only performs a save action within PowerPoint. It does not generate the export file you’ll need for SharePoint.
Each time you click the Save button, PPT will append a digit to the end. If you go through a few iterations you’ll start to see the custom names stack up near the top of the Colors drop-down. Just right-click the old custom names that you don’t need & delete them.
There’s not an undo function within the “Create New Them Colors” window.
2. Click the “More” down arrow in the Themes area.
3. Select “Save Current Theme.”
4. Save the .thmx file.
File name: I suggest incorporating the word “custom” somewhere in your naming convention – that’ll help it stick out in the list within SharePoint.
The default file location it uses is C:\Users\<UserName>\AppData\Roaming\Microsoft\Templates\Document Themes\<FileNameYouProvide>.thmx. You’ll want to note this location, as you’ll need to browse to it from within SharePoint to upload the file.
1. Go to Site Actions > Site Settings. Under Galleries, select Themes.
2. Navigate to the Documents tab. Choose Upload Document. Navigate to the custom .thmx file saved in the previous step, and choose OK.
You should now see your custom file listed in the Theme library. But, you’re not done yet. At this point it’s available for use only.
Requires Design, or Full Control, permissions in SharePoint.
1. Go to Site Actions > Site Settings. Under Look and Feel, select Site theme.
2. Find your theme from the list (this is why I find that having “custom” in the theme name is really useful), and then Apply.
3. Browse around the various SharePoint pages to see how the theme looks. Chances are you’ll need to go back through Steps B-E a few times to get it right. I found myself switching colors from Dark 2 to Dark 1, and things like that, to see the effect.
If you’re not sure where one of the 12 theme color choices will end up (especially ones like accent 4, 5, and 6), I’d suggest making it darker rather than lighter because of the likelihood that it’s used somewhere in SharePoint for a label.
According to Technet: “Themes enable lightweight branding of a SharePoint Server 2010 site by allowing a site owner or a user with designer rights to make changes to the colors and fonts of user interface elements of a site. Themes are applied and customized directly in the user interface, and do not require knowledge of cascading style sheets or master pages.”
A common analogy is that themes are like the paint on the walls of your home. You can browse the predefined SharePoint themes under Site Actions > Site Settings. Under Galleries, select Themes.
Versions
Office 2007 theme files are not compatible with SharePoint 2010. Only SharePoint 2010 can upload a theme (.thmx) file, generated by PowerPoint 2010, to apply the colors and fonts to a SharePoint site.Let’s dig into how it’s done. I’ve divided the process into five major steps: A through E.
Planning for How the Site Should Look
If you’re like me, you know what you like when you see it – but getting to that “Ooh, Yeah, I Like It” point can take more iterations than I’d prefer sometimes. Whatever pre-planning that can be done ahead of jumping with with both feet should be worth the effort. Even if you are able to have the RGB # list of complementary colors available beforehand, you can still expect to spend some time on getting the combinations just right.For this project, I used my SnagIt Editor to detect the RGB #s from our customer’s website, so I had a list of colors to start from.
Generating a New Custom Theme in PowerPoint 2010
1. Launch PowerPoint 2010 and navigate to the Design tab. Browse around the Themes choices in the middle of the ribbon, and pick the one closest to the palette combination you think you’ll end up with. If you don’t pick a different theme to use as a starting point, you’ll be using “Office” which is the first theme listed. Picking a built-in theme that’s somewhat close you what you want would, ideally, save you a bit of time later.Alternatively, you could choose a theme to start with from the Colors drop-down – if you don’t care about looking closely at the colors in the body of the PPT.
2. Ensure you have your “starting point” theme selected. In the following screen shot, I have the “Aspect” theme currently selected.
If you want to use one of the built-in themes as is, without customizing individual colors, then skip to Step C. The built-in themes within PowerPoint are different than the predefined themes in SharePoint, so this would be a perfectly valid solution.
If you want to customize the built-in theme: Click the Colors drop-down, then choose “Create New Theme Colors.”
Theme colors: The top 4 colors – Dark 1, Light 1, Dark 2, and Light 2 – are used significantly throughout SharePoint, for both text elements & background elements, so these should be selected pretty carefully. I recommend that you stick to using dark or light colors as it suggests for each name - I tried to invert them in order to accomplish what I wanted with no success.
Name: This is the name which will be used within PowerPoint. You’ll see it listed as part of Custom Themes in the Colors drop-down, so you can use it again in the future.
Save button: This only performs a save action within PowerPoint. It does not generate the export file you’ll need for SharePoint.
Each time you click the Save button, PPT will append a digit to the end. If you go through a few iterations you’ll start to see the custom names stack up near the top of the Colors drop-down. Just right-click the old custom names that you don’t need & delete them.
There’s not an undo function within the “Create New Them Colors” window.
Exporting the Custom Theme File out of PowerPoint
1. When you’re happy with the 12 colors you have selected, it’s time to export. First, make sure your chosen theme (whether it’s a built-in or a custom you just saved) is the one that’s actively selected under the Colors drop-down. The active theme is denoted by the orange circle.2. Click the “More” down arrow in the Themes area.
3. Select “Save Current Theme.”
4. Save the .thmx file.
File name: I suggest incorporating the word “custom” somewhere in your naming convention – that’ll help it stick out in the list within SharePoint.
The default file location it uses is C:\Users\<UserName>\AppData\Roaming\Microsoft\Templates\Document Themes\<FileNameYouProvide>.thmx. You’ll want to note this location, as you’ll need to browse to it from within SharePoint to upload the file.
Uploading the Custom Theme File into SharePoint
Requires Contribute, Design, or Full Control permission for this document library in SharePoint.1. Go to Site Actions > Site Settings. Under Galleries, select Themes.
2. Navigate to the Documents tab. Choose Upload Document. Navigate to the custom .thmx file saved in the previous step, and choose OK.
You should now see your custom file listed in the Theme library. But, you’re not done yet. At this point it’s available for use only.
Applying the New Site Theme
Important! This step always needs to be done - even if you just uploaded a theme that already existed & replaced an existing file, SharePoint needs this step so it can recognize the new file.Requires Design, or Full Control, permissions in SharePoint.
1. Go to Site Actions > Site Settings. Under Look and Feel, select Site theme.
2. Find your theme from the list (this is why I find that having “custom” in the theme name is really useful), and then Apply.
3. Browse around the various SharePoint pages to see how the theme looks. Chances are you’ll need to go back through Steps B-E a few times to get it right. I found myself switching colors from Dark 2 to Dark 1, and things like that, to see the effect.
Where the Theme Colors Appear in SharePoint
It took me a while to determine which of the 12 color choices affected which area in SharePoint. The following sketch is just a start, but it illustrates my point. See the 4 places where Dark 2 is reused? A limitation I ran into again and again was the reuse of each color – for example, the “Dark 2” color is used for the strip across the top of the page, and the headings in the Quick Launch, and the primary text in the body of the page. In my situation I wanted an orange strip across the top – but I sure didn’t want orange text on the page! A goal was to avoid editing the master page in order to stick with a quick “out of the box” type of solution (because it’ll be easier for our customer to maintain). For the color combination I wanted, this much reuse was a limitation rather than a convenience – though next time the level of reuse could be terrific with a different set of colors.If you’re not sure where one of the 12 theme color choices will end up (especially ones like accent 4, 5, and 6), I’d suggest making it darker rather than lighter because of the likelihood that it’s used somewhere in SharePoint for a label.
What’s New in PerformancePoint 2010 Services and SharePoint SP1
The SharePoint 2010 Service Pack 1 (SP1) for PPS release is scheduled for the end of June, and as Jason mentioned at the end of his kickoff blog, I’m releasing content for the month of June, around the PPS aspects of SP1. Of course, SP1 is an Office 2010 service pack, and the number of updates included for PPS are relatively few when you count them against Office as a whole, but if you’re reading this blog, you obviously care very much about that subset for your favorite dashboarding tool . . . PPS.
I know that you want me to dispense with any small talk about things other than what’s been updated in PPS. But before I do that, I want to let you know what’s in store for the month’s blog. In this post, I’m going to tell you what’s included in the list of SP1 features and fixes. There are actually many more items than what I list here, and many of those things aren’t relevant to the discussion, so I left them out. As a result, I’ve narrowed the list to some of the more relevant and customer-oriented topics. So, without further delay, here is a table listing what the major features and updates include for SP1 and PPS.
So, those are the major ones. By far, the COOLEST thing coming in SP1 is the addition of cascading filters. A lot of thought went into the design, making them quite robust and “feature-rich.” They will certainly please users who have been asking for this functionality.
The rest of the changes coming in SP1 – like fit and finish updates, unicode character handling, minor localization changes, error handling, etc.
Thanks for Kevin Donovan.--Program Manager for PP Services
I know that you want me to dispense with any small talk about things other than what’s been updated in PPS. But before I do that, I want to let you know what’s in store for the month’s blog. In this post, I’m going to tell you what’s included in the list of SP1 features and fixes. There are actually many more items than what I list here, and many of those things aren’t relevant to the discussion, so I left them out. As a result, I’ve narrowed the list to some of the more relevant and customer-oriented topics. So, without further delay, here is a table listing what the major features and updates include for SP1 and PPS.
| Product Area | Explanation |
| Dashboard | We fixed an issue that prevented users from exporting or viewing reports or scorecards opened using the Display Report option in a PerformancePoint Content List. |
| When you deploy a dashboard, we now place the prior version in SharePoint's Recycle Bin. | |
| Server | You can now specify a specific web front end URL when connecting to a site collection from Dashboard Designer. |
| We fixed an issue where users could not render a dashboard as anonymous on an extended web application (e.g. on a different zone) if the default zone web application didn’t allow anonymous access. | |
| We added the ability for PPS to support database failover and the ability for administrators to name the PPS database. Administrators can also specify an empty database for PPS rather than having SharePoint create it during provisioning. | |
| We better handle cache memory consumption, which increases user throughput and reduces server memory use. | |
| We decreased Analysis Services CPU load by up to 37% by adding special logic around schema query calls. | |
| Added event logging for removing trusted locations using cmdlets. | |
| Updated WSDL and DISCO files for the authoring and the decomp tree web services. | |
| Reports | Fixed an issue where, if users have a “%” sign in a dimension member name column on a scorecard, the Comments, Show Details, and Analyze in Decomp Tree menu items are not enabled when a user right-clicks a cell. |
| Fixed an issue where the decomposition tree web service returns error when a member's name contains single quote. | |
| Fixed an issue where some users experienced an error when clicking on Additional Actions –> Drillthrough in a report. | |
| Fixed an issue where some users always experienced scrollbars, in an Excel Services report, after resizing the report in SharePoint. | |
| Fixed an issue where some users were unable to decomp a scorecard with a connected SharePoint URL (QueryString) filter. | |
| Fixed an issue with a PPS Excel Services report where gradient fill in data bars conditional formatting does not appear in the Excel Services report. | |
| Fixed an issue where the “clear filter” option is disabled for value filters on a bar chart report. | |
| Fixed an issue where, on a scorecard, unchecking a single member in the select members dialog de-selected all of the members, rather than just the one. | |
| Fixed an issue where some customers experienced an unexpected error on a chart with custom MDX when switching the view from the MDX tab back to the design tab. | |
| Fixed an issue with web page report types, where URLs containing spaces and special characters fail to render on a dashboard, but preview fine. | |
| SDK | Custom data source providers are now able to use the SecureCredentialProvider class, which allows them to access the unattended service account. |
| Filters | Added cascading filters |
| Fixed a usability feature where tree filters, with only one root level item, with children, auto expands. | |
| Scorecards | Fixed a scorecard annotation issue in dashboard designer where adding a comment link with the same title as a previously added comment link surfaces an error to the user. |
| Fixed an issue where limiting SharePoint permissions to individual items in a scorecard causes the entire scorecard not to render, or it causes an error to show. | |
| Fixed an issue where scorecards that have an indicator, without an image, fail to export to PowerPoint or to Excel. | |
| Added documentation explaining the need to hold down the shift key when dragging and dropping a dimension over multiple KPI metrics. | |
| Data Sources | Fixed an issue where PPS only returned the default view of list items for a SharePoint list data source. In SP1, all of the list’s columns are returned. |
| Fixed an issue for SharePoint list data sources where updating or modifying the list now invalidates the data source cache. |
So, those are the major ones. By far, the COOLEST thing coming in SP1 is the addition of cascading filters. A lot of thought went into the design, making them quite robust and “feature-rich.” They will certainly please users who have been asking for this functionality.
The rest of the changes coming in SP1 – like fit and finish updates, unicode character handling, minor localization changes, error handling, etc.
Thanks for Kevin Donovan.--Program Manager for PP Services
Tuesday, August 30, 2011
How SharePoint Server 2010 can work together with Lotus Notes
We know that Lotus Notes has an own client and we know also that we could reach the Domino server by HTTP. For a couple of reasons http is not enabled and access to the content is only possible through the Notes client. With this post I will explain some ideas what is possible and document some limits.
With SharePoint we have the ability using http:// , https:// mailto: and few more protocols to create links pointing from a SharePoint page to other content. Using the Notes:// protocol is not possible to use in the same way we are using http://. What is now possible and how?
Limits: Where we cannot use Notes:// as a protocol:
Try to create a new Link in a List:
Try to create a new link in Summary Links WebPart:
Edit a page and let’s go through the html source code:
It is also not possible to use <a href="notes://MyServer/db1/folder7/doc8" target="_blank">notes://MyServer/db1/folder7/doc8</a> when editing a page and change the html source by yourself.
By using our search functionality we offer with SharePoint 2010. First you need to crawl the Notes content and we have good documentation how to do that. Please check the following link list.
Crawl Lotus Domino with Lotus Notes Connector in SharePoint Server 2010
http://blogs.msdn.com/b/opal/archive/2010/02/16/crawl-lotus-domino-with-lotus-notes-connector-in-sharepoint-server-2010.aspx
Configure and use the Lotus Notes connector (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/ff463593.aspx
Now a crawl is possible and the search result will be shown with the http:// protocol. How to get the Notes:// into the search result?
In the search administration go through Server Name Mappings:
Add the mapping you want:
A Full crawl is needed after that change and the search result should be now with the Notes:// protocol:
One impact has the ability to get security trimmed search results and to reach that you will need some more administrative tasks.
The idea how to create Links in SharePoint pointing to the Notes content:
- Use search to find “your content”.
- You may use special keywords to only get your one document or all related to a Part-Number or… many ways are possible.
- Copy the URL for the result page and use that as a Link somewhere in your SharePoint Site.
Play a bit with that idea to get a better feeling how that works for you.
Pro: Creating such Links needs a bit more work to find the best keywords and URL’s you can use somewhere else. With implemented security trimming it is a secure way as you are familiar within SharePoint content.
Con: It depends on the infrastructure you have implemented when talking about worldwide unequally distributed server systems with Notes and SharePoint. Federated Search can help here. Notes has a different Authorization behavior and Security trimming is also a time consuming administrative task and has security risks when something is not mapped in the right way.
Idea with an out of the box WebPart:
HTML form webpart gives you the ability to enter Notes:// links:
Edit a page and add the webpart as follows.
Result:
Pro: Using this webpart seems to allow you to enter html source in the way you want. URL’s can be really long.
Con: You need to have some html source knowledge.
Idea with WebPages saved with Word:
Take Word for Windows 2010/2007
Create a new document.
Add a notes Link.
Save the file as a single web page:
Upload that file into a DocLib. To open the MHT file directly in IE you need to set the Browser File Handling to permissive because otherwise you can only save a local copy.
You need to do this in the central admin when administrating the Web Application:
Idea to show the MHT file with the Notes:// Links inside another SharePoint page:
Start with Edit the page and insert the Page Viewer WebPart:
Enter the URL to the MHT file.
Result:
Pro: Edit your own Notes Links in your own document is independent of edit a page. URL’s can be really long. After you saved an edited MHT document the result will be shown immediately where you have added the page viewer WebPart.
Con: You need more steps but when you are familiar with Edit in Word it is easy enough.
Idea with an additional Redirector:
For this idea you need an additional “Service”. You will call the service with a http Url and the IE client will get a Notes:// link back.
Such an URL could look like the following:
http://MyRedirServer/redirect.nsf/goto?ReadForm&rt=Notes://MyServer/db1/folder7/doc8
Pro: You can use the standard way of add a Link in a List or Summary Link WebPart.
Con: It will be not that easy and you will need to double check those Links before others can use your Link list. Also the Redirect Service needs to be up and running all the time and the IT department has one more service to watch.
Thanks to Joerg Sinemus for his excellent solutions..
With SharePoint we have the ability using http:// , https:// mailto: and few more protocols to create links pointing from a SharePoint page to other content. Using the Notes:// protocol is not possible to use in the same way we are using http://. What is now possible and how?
Limits: Where we cannot use Notes:// as a protocol:
Try to create a new Link in a List:
Try to create a new link in Summary Links WebPart:
Edit a page and let’s go through the html source code:
It is also not possible to use <a href="notes://MyServer/db1/folder7/doc8" target="_blank">notes://MyServer/db1/folder7/doc8</a> when editing a page and change the html source by yourself.
Where we can use Notes:// as a protocol:
Idea with Search Results:By using our search functionality we offer with SharePoint 2010. First you need to crawl the Notes content and we have good documentation how to do that. Please check the following link list.
Crawl Lotus Domino with Lotus Notes Connector in SharePoint Server 2010
http://blogs.msdn.com/b/opal/archive/2010/02/16/crawl-lotus-domino-with-lotus-notes-connector-in-sharepoint-server-2010.aspx
Configure and use the Lotus Notes connector (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/ff463593.aspx
Now a crawl is possible and the search result will be shown with the http:// protocol. How to get the Notes:// into the search result?
In the search administration go through Server Name Mappings:
Add the mapping you want:
A Full crawl is needed after that change and the search result should be now with the Notes:// protocol:
One impact has the ability to get security trimmed search results and to reach that you will need some more administrative tasks.
The idea how to create Links in SharePoint pointing to the Notes content:
- Use search to find “your content”.
- You may use special keywords to only get your one document or all related to a Part-Number or… many ways are possible.
- Copy the URL for the result page and use that as a Link somewhere in your SharePoint Site.
Play a bit with that idea to get a better feeling how that works for you.
Pro: Creating such Links needs a bit more work to find the best keywords and URL’s you can use somewhere else. With implemented security trimming it is a secure way as you are familiar within SharePoint content.
Con: It depends on the infrastructure you have implemented when talking about worldwide unequally distributed server systems with Notes and SharePoint. Federated Search can help here. Notes has a different Authorization behavior and Security trimming is also a time consuming administrative task and has security risks when something is not mapped in the right way.
Idea with an out of the box WebPart:
HTML form webpart gives you the ability to enter Notes:// links:
Edit a page and add the webpart as follows.
Result:
Pro: Using this webpart seems to allow you to enter html source in the way you want. URL’s can be really long.
Con: You need to have some html source knowledge.
Idea with WebPages saved with Word:
Take Word for Windows 2010/2007
Create a new document.
Add a notes Link.
Save the file as a single web page:
Upload that file into a DocLib. To open the MHT file directly in IE you need to set the Browser File Handling to permissive because otherwise you can only save a local copy.
You need to do this in the central admin when administrating the Web Application:
Idea to show the MHT file with the Notes:// Links inside another SharePoint page:
Start with Edit the page and insert the Page Viewer WebPart:
Enter the URL to the MHT file.
Result:
Pro: Edit your own Notes Links in your own document is independent of edit a page. URL’s can be really long. After you saved an edited MHT document the result will be shown immediately where you have added the page viewer WebPart.
Con: You need more steps but when you are familiar with Edit in Word it is easy enough.
Idea with an additional Redirector:
For this idea you need an additional “Service”. You will call the service with a http Url and the IE client will get a Notes:// link back.
Such an URL could look like the following:
http://MyRedirServer/redirect.nsf/goto?ReadForm&rt=Notes://MyServer/db1/folder7/doc8
Pro: You can use the standard way of add a Link in a List or Summary Link WebPart.
Con: It will be not that easy and you will need to double check those Links before others can use your Link list. Also the Redirect Service needs to be up and running all the time and the IT department has one more service to watch.
Thanks to Joerg Sinemus for his excellent solutions..
Monday, August 29, 2011
SharePoint 2010: Unable to delete site/web after SP1
While doing some testing after upgrading my dev machine to SP1, I ran into two separate issues when trying to delete a web through the UI by using the “Sites and Workspaces” link in Site Settings. Deleting through powershell worked fine.
Issue #1: Specified method is not supported
This specific error was occurring only on one of my web applications. I had just attached the database for this application to my existing SharePoint 2010 SP1 environment. The error will appear if the database for your web application needs to be updated.
To check if your database needs to be updated, open Central Administration and navigate to “Upgrade and Migration” -> “Review database status”. All of your databases should show a status of “No action required”. If the application you are experiencing the error on is running in compatibility mode, you’ll need to update it using PowerShell. To do this, first get the GUID ID of the database in question by running the following powershell and then copying the ID of the database you wish to upgrade:
Then run the following powershell to upgrade the database using the ID you just copied.
Issue #2: There is no Web named “/YourWebName”
Once my above issue was resolved on the one misbehaving web application, I had consistent behavior across all web applications when trying to delete a web… or so I thought. Turns out – if I create a web right off of the site collection (the RootWeb), then I can successfully delete it using the “Sites and Workspaces” page. Also – I can delete the web successfully if I navigate to the web I want to delete and then use the “Delete this Site” link. This behavior was consistent in a SharePoint 2010 SP1 environment and SharePoint 2010 SP1 + June Cumulative Update. What’s going on here?
Time to open up Reflector. The offending code comes from the Microsoft.SharePoint.ApplicationPages dll located in the virtual directory/_app_bin of your web application. Specifically, the DeleteWebPage class. Here’s the code:
The offending line, using the OpenWeb function, gets passed “/site1” if your web’s name is “Site1”. This will work fine if the web’s url starting from the site collection is “/Site1”. But if your web is a subweb of a subweb (e.g. http://yoursite/someweb/Site1) then it will fail and throw the exception. This looks to be a bug in SP1 and June CU… so we’ll have to wait for MS to fix the issue before we can go this route to delete a web. Instead – use PowerShell to delete the web or navigate to the web you wish to delete and use the “Delete this Site” link.
Issue #1: Specified method is not supported
This specific error was occurring only on one of my web applications. I had just attached the database for this application to my existing SharePoint 2010 SP1 environment. The error will appear if the database for your web application needs to be updated.
To check if your database needs to be updated, open Central Administration and navigate to “Upgrade and Migration” -> “Review database status”. All of your databases should show a status of “No action required”. If the application you are experiencing the error on is running in compatibility mode, you’ll need to update it using PowerShell. To do this, first get the GUID ID of the database in question by running the following powershell and then copying the ID of the database you wish to upgrade:
| Get-SPContentDatabase |
Then run the following powershell to upgrade the database using the ID you just copied.
| Upgrade-SPContentDatabase -Identity YourDatabaseIDGoesHere |
Issue #2: There is no Web named “/YourWebName”
Once my above issue was resolved on the one misbehaving web application, I had consistent behavior across all web applications when trying to delete a web… or so I thought. Turns out – if I create a web right off of the site collection (the RootWeb), then I can successfully delete it using the “Sites and Workspaces” page. Also – I can delete the web successfully if I navigate to the web I want to delete and then use the “Delete this Site” link. This behavior was consistent in a SharePoint 2010 SP1 environment and SharePoint 2010 SP1 + June Cumulative Update. What’s going on here?
Time to open up Reflector. The offending code comes from the Microsoft.SharePoint.ApplicationPages dll located in the virtual directory/_app_bin of your web application. Specifically, the DeleteWebPage class. Here’s the code:
The offending line, using the OpenWeb function, gets passed “/site1” if your web’s name is “Site1”. This will work fine if the web’s url starting from the site collection is “/Site1”. But if your web is a subweb of a subweb (e.g. http://yoursite/someweb/Site1) then it will fail and throw the exception. This looks to be a bug in SP1 and June CU… so we’ll have to wait for MS to fix the issue before we can go this route to delete a web. Instead – use PowerShell to delete the web or navigate to the web you wish to delete and use the “Delete this Site” link.
Thursday, August 25, 2011
SharePoint 2010 SP1 Step by Step Installation steps and Known issues
Please find the SharePoint 2010 SP1 Installation steps and Known issues of it.
Happy SharePointing :D
PerformancePoint 2010 Dashboard Designer – ‘An unexpected system error has occurred’ when adding a data connection
While trying to setup a PerformancePoint 2010 dashboard on my SharePoint 2010 boot to vhd environment today I received this error message – ‘An unexpected system error has occured’…’ when adding a data connection in the Dashboard Designer.
A couple of Google searches didn’t turn up much but did point me towards the ‘Secure Store Service’ – this can be found in Central Administration > Manage Service Applications.
The service was started but when I tried to manage the service I received another error stating that the service was not responding!
It was then that I realised – the environment in question did not contain the pre-requisite WCF hotfix which is required for SharePoint 2010 to install on Windows Server 2008 R2. This machine had actually been been upgraded from Windows Server 2008 x64 to Server 2008 R2 x64 (this was the SharePoint Information Worker VHD) therefore the hotfix did not exist.
I was worried I would have to re-install SharePoint after installing the hotfix but it turns out you don’t need to, just follow the steps below -
A couple of Google searches didn’t turn up much but did point me towards the ‘Secure Store Service’ – this can be found in Central Administration > Manage Service Applications.
The service was started but when I tried to manage the service I received another error stating that the service was not responding!
It was then that I realised – the environment in question did not contain the pre-requisite WCF hotfix which is required for SharePoint 2010 to install on Windows Server 2008 R2. This machine had actually been been upgraded from Windows Server 2008 x64 to Server 2008 R2 x64 (this was the SharePoint Information Worker VHD) therefore the hotfix did not exist.
I was worried I would have to re-install SharePoint after installing the hotfix but it turns out you don’t need to, just follow the steps below -
- Download the Windows Server 2008 R2 WCF hotfix (there are two versions of this patch and the latest is version 2 – ‘Windows6.1-KB976462-v2-x64.msu’), get it from here – KB976462
- Install the hotfix and reboot the machine
- Run the SharePoint Products and Technologies configuration wizard – PSCONFIG
- Proceed through the wizard and it will upgrade your SharePoint farm
- Check in Central Administration and you should now be able to successfully manage the ‘Secure Store Service’ and Dashboard Designer should work!!
Tuesday, August 23, 2011
Disabling Wiki Page Recently Modified section
While creating a SharePoint Wiki Pages, you will get a Recently Modified section at Top Quick launch bar. If you don't want to show this on a page you can restrict this using css change in your masterpage.
If you wanna remove the recently modified link, just a simple CSS modification.
As such:
If you wanna remove the recently modified link, just a simple CSS modification.
As such:
<style type="text/css">
.s4-recentchanges
{
display:none;
}
</style>Enjoy the work with SharePoint 2010.
Monday, August 1, 2011
Reporting Services (SSRS) reports with PerformancePoint
Thanks to Dan for his port on PerformancePoint Services.
Using Excel Services Reports with PerformancePoint Server (PPS). This has been a very popular posting and I thought I would add another one in regards to using Reporting Services (SSRS) reports with PerformancePoint (in PPS 2007 this type of report was called SQL Server Report).
Some of the reason that you might want to include a SSRS report in your PPS dashboard would be because:
My example here used the Contoso Retail DW sample data which is available from the Microsoft downloads here – Microsoft Contoso BI Demo Dataset for Retail Industry. This is also using Reporting Services 2008 R2 which includes the new Map report item, Report Builder 3.0, PerformancePoint Services, and SharePoint 2010 Enterprise.
I have two other postings that I did earlier in the year in regards to the new Map report item here that you can check out if you have questions in regards to that:
You might find this posting useful if you want to reuse the workspace file – Migrating PerformancePoint 2010 Content to New Server.
Enjoy and Happy SharePointing.
Using Excel Services Reports with PerformancePoint Server (PPS). This has been a very popular posting and I thought I would add another one in regards to using Reporting Services (SSRS) reports with PerformancePoint (in PPS 2007 this type of report was called SQL Server Report).
Some of the reason that you might want to include a SSRS report in your PPS dashboard would be because:
- leverage an existing report created by an end-user
- incorporate existing operational reports
- use additional charting options – map, area, range, scatter, polar, bar (not column), funnel, 3D, sparklines, data bars
- need more flexibility and control over reports, styles, colors, scales, etc.
- join multiple data sources into a single report
- combine relational and OLAP data into a single report
 |  |
| Go to Report Library in SharePoint site, select Documents from Ribbon, select New Document, and pick Report Builder Report | This will either launch Report Builder or ask you if you want to run and install the application if you haven’t done so yet |
 |  |
| Report Builder is a ClickOnce application and by clicking Run you will install the application | Once installed the Report Builder application will start up |
 |  |
| In this example we will build a Map | Reposition the map up a bit so it appears above the legends |
 |  |
| A Bubble Map will be used to be able to analyze two metrics | A new data set will need to be added that contains the spatial data |
 |  |
| A new data source will be added connecting to the Contoso Retail DW SSAS database | Use the Sale cube, filter for the United States, setup the Fiscal YQM as a Parameter, pick State Province Name, Sales Amount, and Sales Total Cost |
 |  |
| Use STATENAME and map this to the State Province Name field from the data set | Pick a theme for the style, setup the bubble size to visualize Sales Amount, and polygon color for the Sales Total Cost |
 |  |
| Setup Chart and Legend titles, polygon tooltip, remove color legend, resize/reposition map, and remove default marker size | Save report to SharePoint library |
 |  |
| Now we are going to add a new Report to our existing PerformancePoint Content library | This will launch Dashboard Designer and like the Report Builder you may be prompted to install it (this is also a ClickOnce application) |
 |  |
| If nothing launches then you need to make a small adjustment in your IE security settings to Enable ‘Automatic prompting for file downloads’ | Now we will create the new PerformancePoint Report |
 |  |
| Use the SharePoint Integrated mode, specify the URLs for the Report Server and the RDL file, uncheck the Show toolbar, and specify a name for the PPS report | Next we will create a filter that we can use with the report once it is displayed in the dashboard page |
 |  |
| The filter we will create will be for the Fiscal YQM and we will remove periods that don’t have any Sales Amount | We will use a Tree style display and only allow a single selection |
 |  |
| Name the filter and get ready to create the dashboard | Add a new Dashboard item |
 |  |
| Name the dashboard item, page, add the filter, add the report, and remove the extra column (zone) on the page | Create a Connection (formerly link in PPS 2007) between the filter and the report |
 |  |
| The filter will connect to the DateFiscalYQM parameter on the report and will pass the Member Unique Name (an SSAS member value to the report) | Save the PPS content items and deploy the dashboard to the Dashboards library |
 |  |
| Select the Master Page and whether or not you want to include the page navigation or not | Test out the filter and view the results with the deployed PPS dashboard |
I have two other postings that I did earlier in the year in regards to the new Map report item here that you can check out if you have questions in regards to that:
Download:
Feel free to download the PPS Workspace file (ddwx) and the SSRS report (RDL) file from my SkyDrive which I have included in a zip file. You might find this posting useful if you want to reuse the workspace file – Migrating PerformancePoint 2010 Content to New Server.
Enjoy and Happy SharePointing.
Subscribe to:
Posts (Atom)