Business Intelligence Blogs

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.

«February 2016»

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.
Power BI publish to web

You’ll see a message pop up box similar to below. Click the yellow button to create the embed code.
Power BI publish to web preview

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.
warning 2

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!

Pretty awesome!

Additional Resources

Read the Power BI “publish to web” announcement here.

Read the Power BI “publish to web” documentation here.


Let me know what you think of this feature or if you have any questions. Leave a comment down below.

Read more


Non Empty vs NonEmpty

Hey everyone, in this blog I want to address a very common MDX Question. What is the difference between the NON EMPTY keyword and NONEMPTY function? To take it a step further which one should you use?

Non Empty keyword VS NONEMPTY Function.

The big difference between the NON EMPTY keyword and the NONEMPTY function is when the evaluation occurs in the MDX. The NON EMPTY keyword is the last thing that is evaluated, in other words after all axes have been evaluated then the NON EMPTY keyword is executed to remove any empty space from the final result set. The NONEMPTY function is evaluated when the specific axis is evaluated.

Should I use NON EMPTY keyword or NONEMPTY function?

Ok Mitchell, so you told me when each of these are evaluated but really you haven’t told me anything up until this point. Can you tell me which one I should use already? Well, unfortunately, it depends. Let’s walk through an example of each using the BOTTOMCOUNT function.


In this example I’m returning the bottom ten selling products for internet sales. Notice that I have returned all products that have no internet sales, this is not necessarily a bad thing, maybe you want to return products that don’t have sales.


However if you don’t want to return these products then we can try using the NON EMPTY keyword. In the below example you can see the results when I add NON EMPTY to the ROWS axis.


WHOOOAAA, what happened?? A lot of people would have expected the results here to show the bottom ten products that DID have sales. However, that is not the case, remember that I said the NON EMPTY keyword is evaluated LAST after all axes have been evaluated. This means that first the bottom ten selling products which have $0 in sales are first returned and then the NON EMPTY keyword removes all that empty space from the final result.

BOTTOMCOUNT function with NONEMPTY function.

So let’s try this again, if you want to return the bottom ten products that had sales then we must first remove the empty space before using the BottomCount function. Take a look at the code below:


In this code we first remove the empty space before using the BOTTOMCOUNT function. The result is we return the bottom ten products that had internet sales. Once again neither one is right or wrong here it just depends on what you want in your final result.

NON EMPTY Keyword vs. NONEMPTY Function – Performance

There is a very common misconception that the NONEM

Read more

SSIS 2012 XML Task - Namespaces in XPath

  • 7 April 2012
  • Author: Russel Loski
  • Number of views: 8269

You have an XML document.  You want to get the text from the first node named "i."


So you decide to try your hand at using the XML Task.  You select the XPath operation type, you enter the XPath "(//i)[1]" which means give me the first i node text.  But it doesn't do anything.

The problem is that there is a default namespace defined in the document.  What the XPath "(//i)[1]" is translated to is not "give the first i node." Rather it is translated "give the first i node with no namespace."

In previous versions of SSIS, you were limited to using the no namespace in your XPath.  There was no way to declare the namespace context for your XPath. It led to some very interesting XPath such as "(//*[local-name()='i'])[1]" which gets the first node that has the local-name (ie the name with out a namespace) i.

In SSIS 2012, this has finally changed.  The team at Microsoft have added the means to associate the namespace with your XPath.  The process is similar to the process of creating a XPath XML Task in previous versions of SSIS.  You specify the source and output.  However, notice that I can use a namespace prefix (i:) in my XPath (the SecondOperand).  This prefix refers to a namespace that I specify in the Namespaces collection.

XML Task Editor for XPath Operation Type

You enter some prefix that you will be using to reference this namespace (test.uri).  Note that it does not have to be the same as the prefix used in the document, as long as the namespace uri in the XML document matches the namespace uri in the Namespaces collection.  So I click on the elipsis to the right of the Namespaces collection box.

Namespace declarations edit screen

Note that you can't leave the Prefix blank and expect it to work as the default.  You have to assign a prefix.

This is a major improvement to the SSIS XML processing. I am currently reading several nodes in a document that specifies the namespace (as should all useful XML documents). It is a pain to have to dance around the XML Namespaces issue.

Day one of my adventures in SSIS 2012 complete and it is definitely Christmas (call me wierd, my daughters do).  I look forward to digging deeper into more.

Categories: Analysis Services
Rate this article:
No rating

Please login or register to post comments.