Understanding The "The key didn't match any rows in the table" Error In Power Query In Power BI Or Excel. You can download my proof-of-concept SSRS project here: One last thing: I think it would great (and involve relatively little dev work) if SSRS supported the creation of Web Slices out of the box. Even with the limitations that having to render to XML imposes I can think of a few useful applications of this approach… maybe I’ll test them out in a future blog entry. This then meant I could see the contents of the table in my Favourites bar whenever I wanted:Īnd whenever the data changes (you can control how often IE polls the original web page in the Web Slice’s properties, and also in the definition of the Web Slice itself) the text in the Favourites bar turns bold: I could then click on either to subscribe to the Web Slice and have it added to my favourites. First, the Web Slice button appeared in the IE toolbar:Īnd when I moved the mouse over the table in the report, it was highlighted with a green box as a Web Slice: When I went back to IE and reopened the report after deployment I could see two new things. Then I went back to BIDS and altered the XSLT file to add the necessary tags for a Web Slice around the main table. &rs:Format=XML&rc:MIMEType=text/html&rc:FileExtension=htm Here’s an example SSRS URL that does this: I was then able to deploy the project and, by using URL access to the report get it to render to XML and get the result treated as html, was able to see the following in IE8: I then added the XSLT file to my project and associated my report with it using the report object’s DataTransform property, so that it was always used when the report was rendered to XML. I then rendered the report to XML, took a look at the XML generated, and created a simple XSLT file that would generate a HTML report from that XML. The first thing I did was create a simple SSRS report in BIDS that brought back values for Internet Sales broken down by country: 
However, it still makes for a fun proof-of-concept 🙂 To be honest this isn’t a satisfying approach for me because it involves a lot more effort to get the report looking the way you want, and of course you have to have control over how the report is rendered. I won’t go into too much detail about how this works once again, Teo has an excellent explanation in his book “ Applied Microsoft SQL Server 2008 Reporting Services” (reviewed here – it’s an excellent book) on pages 263-265. The only way I could get it to work was to render the report as XML and then use an XSLT file to give me complete control over the HTML that SSRS generates. I first looked at using the new rich formatting functionality that’s available in SSRS 2008 that Teo Lachev describes here, but it turns out that you can’t use this to create Web Slices because SSRS doesn’t support the necessary attributes (see here for details – at least I assume this is why, because I couldn’t get it to work). The challenge with implementing web slices is to get SSRS to generate the necessary html when it renders your report. After all, wouldn’t it be cool if you could subscribe to a table in an SSRS report, or even better a cell within a table, and get notified when that value changed rather than have to keep pinging the report yourself? Of course it would! Here’s how to do it… There’s a brief overview of what they are here:Īnd a really good guide to implementing them from Nick Belhomme here:īeing the BI geek that I am, my first thought was to see whether they could be used with Reporting Services reports. One of the new features that caught my eye in Internet Explorer 8 when it came out was Web Slices – the ability for a web developer to carve up a page into snippets that a user can then subscribe to.
0 kommentar(er)
