View blogs by industry experts on topics such as SSAS, SSIS, SSRS, Power BI, Performance Tuning, Azure, Big Data and much more! You can also sign up to post your own business intelligence blog.
Power BI Publish to Web for Anonymous Access is Here
Earlier this week on Wednesday the Microsoft Power BI made an incredibly exciting announcement and released Power BI “publish to web” as a preview feature. This is HUUUUGE news! This was probably the top requested feature and its finally here thanks to the hard work and dedication of the Microsoft Power BI team!
Read Getting Started with R Visuals in Power BI
Power BI “publish to web” allows you to easily expose a Power BI report to the world through an iframe that can be embedded wherever you like.
To publish your Power BI report to the web, log into your Power BI site.
Find the report that you want to share and click File in the top left.
You’ll see a message pop up box similar to below. Click the yellow button to create the embed code.
This is where you’ll see a very important warning!
WARNING: Reports that you expose through the “publish to web” feature will be visible to everyone on the internet! This means NO AUTHENTICATION is required to view the report that is embedded in your application.
Once you do that, you’ll receive an embed code that you can then use to expose your Power BI report within your blog as seen below!
As you can see the report maintains all the interactivity features of Power BI. And as your Power BI report updates and changes, those changes will be reflected in your embedded Power BI reports!
Read the Power BI “publish to web” announcement here.
Let me know what you think of this feature or if you have any questions. Leave a comment down below.
In a previous post I wrote about how you can use embedded custom code to extend the capabilities of Reporting Services. This week I will show you another method of using custom code but this time with external assemblies. Ideally when using custom code you would choose to do so using external assemblies. External assemblies help developers manage code from outside Reporting Services and share the exact same code across multiple report. Here’s a few of the pros and cons of using external assemblies for custom code.
In this example I’m going to walk you through beginning to end of an example of how to create an external assembly then use it in Reporting Services. Our goal is to compartmentalize our code into and assembly so every developer does an age calculation the same way. Calculating age can easily be done in the expression language the Reporting Services provides but using the assembly assures It’s done the exact same way every time. These steps will walk you through:
Public Class Age
Public Shared Function CalculateAge(ByVal BirthDate As Date) As Integer
Return DateDiff("yyyy", BirthDate, DateTime.Now())
I hoped this step by step helps. If this topic is something that interest you then you may also be interested in a SSRS Master (Advanced) Class I’m teaching. You can find when the next one is here.
Other posts by DevinKnight