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.
While in the process of developing SSIS packages it’s likely you will deal with errors occasionally unless you’re the Superstar developer that never makes mistakes. Of course your first steps to deciphering the problem is to look at either the progress/execution results tab in BIDS. The problem with viewing error messages here is that more than likely the error you receive does not fit on the single line and goes off the screen. So what do you do? Right-click select Copy Message Text and paste it in something like the notepad is what most people do. This is an quick way to view a full error message, but I’m going to share with you another option that can be used during development to view your full error message.
This method involves using a little bit of scripting and taking advantage of Event Handlers.
1. Create an event handler on the package level that will kick off a Script Task when an OnError event occurs.
2. Drag a Script Task from the Toolbox onto the Event Handler design surface then double-click to open it’s editor.
3. Select the System::ErrorDescription Variable From the ReadOnlyVariables list. (This variable is only available in the Event Handler tab) Then click Edit Script.
4. Once the Editor opens scroll down to where it says Add your code here and replace that line with the following code:
This code is looking waiting for this system variable ErrorDescription to be populated and when it is a message box will appear with it’s content.
Now when your package is run if it encounters an error that causes the package to fail you will receive a message box with the same error you would find in the progress/execution results tab. If you have multiple errors you will receive multiple message boxes. This message can easily be copied from the message box by using the CTRL+C if you will wish to copy this to a notepad.
Other posts by DevinKnight