Ask Me Anything Unanswered Chat Questions Answered

Last week, I participated in an “Ask Me Anything” session where I answered questions around both Paginated Reports in Power BI, as well as questions around SQL Server Reporting Services and Power BI Report Server.

As I wasn’t able to get to all the questions posted in the chat, I said I’d answer those I didn’t get to in a follow-up post on my personal blog.  So, without further adieu, here’s a recap of the related unanswered questions with my responses.  I’ve broken them into sections focused on Paginated Reports in the cloud, as well as the on-prem offerings (SSRS/PBIRS).

Paginated Reports in Power BI

“any update on parameters? right now they are only on the page header, any chance that this area will get a makeover?”

– You’ll see us doing work to rationalize the toolbar in paginated reports with Power BI reports to the extent it makes sense.  There are certain patterns for paginated reports authors prefer in terms of parameter layout/grouping that we don’t want to disrupt, but the idea is to make the chrome around the reports look/feel similar across both report types.

Will the RLS will be available in paginated reports too?”

– Yes, when paginated reports support connecting to Power BI datasets, we will respect RLS.  We’ll also support it against other data sources when we support user-based authentication for them.

“Is there a recommended resource for testing / exploring paginated reports – i.e., a sample paginated report that can be used as a template?”

– Great question.  I’ll put together a list of resources in a follow-up post, but at a minimum recommend you download Report Builder and follow the tutorial.

“Is printing of multi-page table the main advantage of SSRS reports over Power BI tables/matrix?”

This is another good question – it isn’t an either/or, but rather which is the best tool for what you need to accomplish.  I’m going to cover this in a separate post as well.

“Is there plan to allow embedding Paginated report in SharePoint Online as we can today with PowerBI Report?”

– Yes, this is planned.

“power BI service will we get subscriptions for paginated reports in the same way we have now in SSRS? Also will this be extended to Power Bi reports and dashboards in Power Bi service. Including Data Driven Subscriptions?”

Yes!  You’ll see the current subscriptions in Power BI evolving to give you the options you have with SSRS today for both report types.  This includes scheduling, the ability to send with specific filters/parameters applied, attachment support, etc.

“for now I’m not able to find paginated reports using the search function on the Home page. Any timing when/if this is coming?”

This is a known bug that we’re working with other teams to get resolved.  You should see this fixed in the next couple months.

Power BI Report Server/SSRS

“can we share a .pbix report through emails?”

We aren’t planning to add subscription support for Power BI Reports in Power BI Report Server in the short term.

“Would love to hear about how RLS will be implemented to PBIRS.”

This work is well underway for the January 2019 release of Power BI Report Server.  It will be similar to what you do in the service today, where you set the roles in the desktop and assign users to those roles in the server through the web browser.

“And along the same lines, what about standard templates, such as headers/footers?”

This is an improvement we’d like to look at for the Power BI service as it relates to Paginated Reports, so we’d also look to bring it back to the on-prem product as well.

Looks like the other questions related these areas were all addressed either in the session or in the chat itself.  If you have additional questions, feel free to check the existing FAQ, or leave a comment in the blog comments below!

Download Paginated Report Bear’s sample paginated report for Power BI

image

Hi everyone, it’s guest blogger Paginated Report Bear!

Well, actually, Mr. Chris agreed to type for me since I don’t have fingers.  Anyways, if you watched my intro video, I promised you all I’d make a sample report and share it by the end of the week.  Since I always keep my promises (EDITOR NOTE: no he doesn’t), here is my first paginated report that you’re free to download and try out in Power BI!  It uses the Enter Data feature that was introduced a few months ago, so you can upload it as is into your Power BI (Premium) workspace and give it a try.  If you don’t have Premium capacity, use the steps in Mr. Chris’s last blog post to spin up a capacity and try it out yourself.  The report sample has a couple cool tricks in it, like dynamic images based on the parameter you select, so it might be a nice reference for you in the future.

I’ll be creating more samples and talking more about paginated reports in the future (or not, depending if my son gets tired of doing this).

Thanks for reading!

Paginated Report Bear Sample Report

How to use A SKU’s to try out Paginated Reports in Power BI without upfront cost or long term commitment

image

Since the Eagles game doesn’t start until later, thought I’d put this together for folks.

As many of you know, earlier this month we announced a preview of Paginated Reports in Power BI.  While folks were excited about this, there were those who were disappointed it was only available (for now) if you had Power BI Premium.

“I don’t have Premium (yet . . .),” they said,  “But I still want to try this out and use it.  How can I do so without committing to it for a month and paying $5000?”

The good news is, there is an easy way to do this.  See, as I’ve stated in previous interviews, you can try all the functionality out by spinning up an Power BI Embedded A SKU capacity, which is available to purchase through Microsoft Azure.  While normally A SKU’s are specifically used for embedding scenarios, there is no licensing restriction against using them internally if you’d like.  However, generally this makes little sense vs. purchasing a P SKU for most use cases, since each user would still need a Pro license to access the Power BI portal AND it’s almost $1000 more per month if you run it all the time.

But if you just want to try out the new functionality that is available only on Premium capacity, the big advantage of A SKU’s is you can stop/start them just like any VM in Azure, and you’re billed by the minute vs. having an initial upfront monthly cost.  This means you can spin up an A SKU, turn on the paginated reports capability in your Power BI portal, and start using it.  And when you’re done, you can go into Azure and pause the capacity until you want to use it again.  Since you’re only billed for the time it’s running, you can try this new functionality out for around 14 cents a minute! (this figure is based on my fuzzy math being done while my son is playing Fortnite right next to me, so forgive me if this is off by a few cents one way or another).  Let’s walk through how you’d go set this up yourself –

I have my own Power BI subscription (yes, I pay out of pocket for this), since I like to have access to the exact same experience as all of my users do (or I forgot to turn it off when I joined the team . . .).  In any event, I have a Pro license, but when I check the Admin Portal, I can see I have no Premium capacities right now.

image

Note another tab there which says “Power BI Embedded” – I don’t have any of those capacities, which you purchase in Azure, spun up currently either.

image

To get one of those going, I’m going to head to the Azure Portal and login with my credentials that I also use for Power BI.  Why? Because I’m the only user, so I’m also the admin.  Now, I can do a search for “Power BI Embedded”.  This will take me to the management page, which looks like this

image

I hit the “Create Power BI Embedded” button, which, if you haven’t signed up for an Azure account yet, you’ll be prompted to do so, and this includes a $200 credit for 30 days.  If you have signed up for Azure, you will skip this step (duh).

image

Now that I have that setup, I’ll go back to the portal and get back to the previous screen.  Here, I can click the button again to setup a new Power BI Embedded A SKU.  You need to select at least an A4 capacity size or higher to use Paginated Reports, so I’ll pick an A4 in my home location to spin up.  (NOTE: Paginated Reports are also supported in multi-geo scenarios, even during our public preview, so I could choose other regions outside my home region if I wanted to.)

image

Everything looks good, so I’ll hit create and wait for it to finish deploying.

image

If I check my Power BI Portal, I see that it is also showing as being deployed there under the Capacity Settings –> Power BI Embedded tab
image

Once it’s completed deployment, when I click on the capacity name, I’ll see I can manage this capacity just like I would any premium capacity in Power BI.

image

Under the Workloads, I see the two new preview workloads, and I’ll set Paginated Reports to “On” and assign 50% of the memory to that workload.  I can also try out the new Dataflows workload as well, but I’ll save that for another time.

image

After a few moments, I’ll see the message has changed from starting to Ready, and my workload is now ready to use.  I’ll assign all (one) of the workspaces for my organization to this new capacity.

image

Cool!  Now, I can upload my first paginated report to the workspace and view it.  I’m using a vintage Halo sample report, and it renders without a hitch.

image

But now I want to stop using the capacity and not get charged (since I finished this blog post).  No problem – I can go back to the Azure portal and just pause the capacity until I want to use it again.

image

When I’ve paused it, I can no longer view my paginated reports in Power BI, but they aren’t deleted or otherwise affected.  They’re still there waiting to be used again when the capacity is started up, and I can delete them if I need to.

image

And that’s it – in less than an hour, including the time it took to type this blogpost, I created a new Azure subscription, created my first Power BI “Embedded” A4 capacity, turned on the Paginated Report workload, assigned a workspace, uploaded and viewed my report, and then paused the capacity to stop the billing on it.  Whew!

Thanks so much for reading through the post today, and I hope you all take some time to try out the new paginated reports in Power BI Premium.  And if your organization doesn’t already have Power BI Premium, use this walkthrough to give it a try yourself!

Happy Thanksgiving (week)!

Adventure Works brand package now available!

image

Super short post today.

With the release of an updated test/demo Azure VM for Power BI Report Server on Monday, we thought it made sense to provide a new Adventure Works brand package for everyone to use in their demos/presentations to go along with it.  Feel free to download and use with Reporting Services 2016/2017 or Power BI Report Server – https://1drv.ms/u/s!Au6-0xX27UdgnOIapntXPaoPcqqOWQ

Thanks!

Tiggee, Batman and Power BI Premium

WP_20130922_114

On the eve of the Microsoft Data Insights Summit, I thought I’d finally write the story behind the picture I’ve included with this post.  How does this story relate to the recent announcement around Power BI Premium?  Well, I’ll leave that up to you to decide if it does, or if it’s simply a cute little story that involves my son Matthew (who has been bugging me to write about him on here).

A couple years ago, my son asked his sister Caitlin and I to play Monopoly with him.   We happily agreed, and went downstairs to the family room.  But we didn’t see the usual setup.  Instead, we were greeted with what you see in the picture.

“What the heck is this?” his sister asked.  “This isn’t Monopoly!”

“I know – now it’s AWESOME Monopoly!” he replied.

“Awesome Monopoly?  That sounds stupid.  I don’t want to play that.”

“C’mon, please – it’ll be fun.”

“No it won’t – it looks dumb.  I’m going back upstairs.”  With that, she turned and stomped out of the room, taking Happy Bear with her.

I winced.  This had played out many times before, and the ending had always been the same.  I glanced towards the kitchen, seeing if the tissue box was still sitting on the counter from an earlier incident.  But it wasn’t needed – he just smiled, sat down and started re-arranging Batman to make room for me.

“She’ll be back,” he said.  “You’ll still play with me, won’t you dad?”

“Um, sure.  Awesome Monopoly sounds, um, awesome,” I said, not quite sure what I was in for.

He tried to explain the rules , and I’ll admit, they seemed pretty confusing the first time he explained them to me.  I don’t remember everything he laid out, but one rule he mentioned during this initial explanation was if you rolled a 12 and landed on “Chance”, Batman got put in jail for a turn OR you had to draw a playing card.

“Buddy, I gotta be honest – I don’t fully understand some of these rules you’ve added.” I told him.  “Do you think we could make it a little less confusing?”

“What do you mean?  We haven’t even started yet.”

“Yeah, I know, but some of these rules . . .”

I didn’t want to push too hard, but at the same time, I couldn’t imagine the game going well if the Elf on the Shelf remained the banker for the entire game.

“Okay, new rule!  We can always change the rules if we decide they’re dumb.”

“Really?” I asked.

“Yep – that’s why it’s Awesome Monopoly.  We can keep making it more and more awesome together!”

I shook my head and laughed.  “Sure, pal, that sounds fair.  I’ll let you go first.”

We went a few rounds, me laughing and him asking me each time someone went how he could make it even more “awesome”.

“I’ll admit, pal, this is a lot of fun.”

“Yay – I knew you’d like it!  Can you go tell Caitlin how much fun it is?”

“Sure.”

I nodded, left the room, and came back with her having agreed to play after hearing how it great it was (and Happy Bear even came back too).

“Caitlin’s back – woohoo!”  He proceeded to run around the room and make sounds like a choo-choo train.  “Yayyyy!”

The game played out, and any time someone thought of a way to make the game even more awesome, we talked about it, tweaked the rules and kept making the game more and more awesome!  (My kids used to like to say awesome A LOT).

So what’s the moral of the story?  It’s either –

1. Batman cheats

or

2. Power BI Premium = Awesome Monopoly.

or

3. Chris needs better blog topics

If you’re coming to Seattle for the conference, I’ll see you next week!

Using URL parameters with Mobile Reports in Reporting Services

image

One area I’ve found folks looking for additional information recently has been how to use URL parameters with Mobile Reports in SQL Server 2016 Reporting Services.  This was a fairly popular feature in Datazen, so naturally people want to use it in SQL Server 2016 as well.

Quick background for folks who don’t know what URL parameters are in the context of mobile reports.  You can create a mobile report with parameters in SSRS 2016 so you and your report readers can filter your reports.  This is helpful when you have a large dataset, for example, so not all the records are loaded at once (If you aren’t familiar with how to write a shared dataset query with parameters in Reporting Services, you can learn more about that at this link – https://msdn.microsoft.com/en-us/library/dd239345.aspx).  Sometimes, you’ll want to provide those parameters as part of the URL for the report.  This can be useful if the report is a drill-through target from another report you’re viewing, for example.

First off, there is support for this feature.  You can find documentation on MSDN for it here – https://msdn.microsoft.com/en-us/library/mt772301.aspx

The article, however, only covers the basic scenario around using a dataset parameter.  Dataset parameters are passed on to the shared dataset that they were specified for when you created the mobile report. The parameter name must be specified as:

<Dataset Name>.<Parameter Name>

Below is a sample URL for supplying a value for the @Reqtype parameter of for an ExecutionLogs dataset:

http://rsserver/Reports/mobilereport/ExecutionLogs%20with%20Filter?ExecutionLogs.@Reqtype=Subscription

There are also parameters that are tied to the selection state of the control in the mobile report it was specified for.  These can be thought of as selection control parameters.  An easy way to find the name of the selection control to use in your URL is on the “Set drillthrough URL” screen in Mobile Report Publisher.

image

Like dataset parameters, the parameter name must specified in the following manner:

<Control Name>.SelectedItem
<Control Name>.SelectedItems

Below are sample URLs for specifying these:

http://rserver/Reports/mobilereport/ExecutionLogs%20with%20Filter?SelectionList.SelectedItem=Subscription

http://rsserver/Reports/mobilereport/ExecutionLogs%20Multi?SelectionList.SelectedItems=Subscription,Interactive

A special type of selection control in Mobile Reports is the Time Navigator control.  The time navigator control supports the following properties you can set in your URL –

– SelectedStartTime
– SelectedEndTime
– ViewportStartTime
– ViewportEndTime

The values for these properties are date time values formatted like this – “2017-02-15T00:00:00”.

Please Note: the “:” character needs to be URL encoded as “%3A” (browsers will usually do this automatically for you).

Now please read carefully the following item, because here’s where folks often run into trouble – if a user specifies a dataset parameter value via the URL and there is also a selection control wired up to supply values for the very same dataset parameter, a conflict occurs. The mobile report resolves this conflict by applying the dataset parameter value supplied via the URL (and discarding the initial selection control value). Note that this is true even as the user starts interacting with the report and chooses other selection values!

You can easily avoid this by supplying a selection control parameter via the URL instead of a dataset parameter.  The MSDN article is being updated to reflect this information as well, but keep this in mind when you are designing your mobile reports.

Finally, there is an item you can apply to your entire report via URL, and that’s to enable/disable showing the report title.

To disable the title, simply add “?title=false” to your URL, so it looks like the following –

http://rserver/reports/mobilereport/Claims%20Trends?title=false

If you want to show the title, just don’t add this to your URL.  Simple enough, right?

Hope this has been helpful for you and helped clear up a few things on this topic.  I want to give a special thanks to Andre M. from the engineering team for helping me with this blogpost.

How to insert a live Power BI report from SQL Server Reporting Services into a PowerPoint slide

image

Yay – the long awaited installable version of the Technical Preview of SQL Server Reporting Services is finally here.

Though very similar in functionality to what was first released on an Azure VM back in October, one item now officially supported that wasn’t previously is using https on your report server.  With this change, you can now use the Web Viewer add-in for PowerPoint 2013/2016 to surface live Power BI Reports from your server.  This is the same functionality already available for both paginated and mobile reports that I’ve walked through previously.  Here’s how you can try this functionality out as well with the Technical Preview –

1.  Go to the Insert Tab in PowerPoint.  You should see the Store Add-In in the ribbon.  Click it to open the App Store –
OfficeSnip
2.  A pop-up will open with the apps available in the store.  You can now run a search for the app you wish to use
image

Type Web Viewer into the search bar and hit Enter.  You see the Web Viewer app created by Microsoft, which is what we’ll use.

image

From here, you’ll need to enter the address for your Power BI report (and make sure you have https configured for your server!)  You need to use the “rs:embed=true” url pattern in the address, which we first introduced in SQL Server 2016.  Otherwise, you will see the following error –

When I use that address, it works just as one would expect in the preview –

image

You can also take advantage of row-level security in your report, which will flow through to the PowerPoint slide, by either using Kerberos or EffectiveUserName for your Analysis Services data source.

image

One suggestion is that you don’t use self-signed certificates with this feature – I have found the web viewer control doesn’t always work well with these (as anyone who saw my attempt to demo this at PASS can attest to.)

Thanks for reading and give this a try – it’s something we’ve heard from a lot of people wanting to take advantage of!