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»
MonTueWedThuFriSatSun
25262728293031
12345

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!

https://msit.powerbi.com/view?r=eyJrIjoiYTNjNzcwNjctNTczMy00ZDMxLWFlMGUtMDViODA1NGZiNmI0IiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9

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.

Feedback

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


Read more
67
8

MDX NON EMPTY KEYWORD VS NONEMPTY FUNCTION

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.

BOTTOMCOUNT FUNCTION with NON EMPTY Keyword

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.

image

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.

image

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:

image

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
91011121314
15161718192021
22232425262728
29123456

Copy and rename a file in SSIS using the File System Task

  • 12 January 2012
  • Author: Keith Hyer
  • Number of views: 170004
  • 0 Comments

"jampa.sb" asked a question about moving files around in SSIS using the File System Task and variables in the SSIS forum.

Based on that question, I decided to put together a "Step-By-Step" walk through demonstrating how to do a portion of the issue. 

From the question, there are 3 folders and to start, 2 files:

  • Folder A\
  • Folder B\
  • Folder C\ 
  • In "Folder A", a file named "a20120111.txt" gets created.
  • In "Folder B", a file named "b20120111.txt" gets created.

 The question ( goal ) is to rename a COPY "a20120111.txt" of the file to "c20120111.txt" which will be placed in the "Folder C". 

I'm going to "stage" some test files as shown below and assume that we've gotten this far successfully. 

Starting point

Ok, with those in place, let's look at that final step:

First, I define some variables.  They're not dynamic ( expression-based ) yet - just regular fixed string variables.

Variable declarations

Next, we will add the expression to the FileNameDate variable to make it "build" today's date at runtime.  To do this, highlight the FileNameDate variable as shown above and then go over to the properties window.  It should look similar to the ( edge of ) the window pictured below:

 

Date variable setup 

For the property for "EvaluateAsExpression" - set this to True.  Then click into the "Expression" property just below it.  An "..." ellipse button should appear.  Click on it, which opens the Expression builder.  Put in the expression as shown here:

(DT_STR, 4 , 1252)DATEPART( "year" , GETDATE() ) + "" + RIGHT( "00" + (DT_STR, 2 , 1252)DATEPART( "month" , GETDATE() ) , 2 ) + "" + RIGHT( "00" + (DT_STR, 2 , 1252)DATEPART( "day" , GETDATE() ) , 2 )

Click "Evaluate Expression" to see the value and ensure that the formula is correct.

If everything is working, click "OK" to save the variable's expression.

 

Now repeat those steps selecting the "DestName" variable - in this example, I have given it  the following expression code:

@[User::DestPath] + "c" +  @[User::FileNameDate] + ".txt"

Note that I assumed a few thing there - I assumed the file would always have the "c" portion and the ".txt" portions on the filename.  If that is not the case, create variables for them - or adjust them accordingly.

 

Finally, repeat the steps again selecting the "SourceName" variable.  I gave that one the following expression code:

@[User::SourcePath] + "a" +  @[User::FileNameDate] + ".txt"

Again, I have assumed what the filename will look like for the source file - you may need to adjust it to your needs.

 

** Make sure you click "Evaluate Expression" after each one as a test.  Also of note:  SSIS doesn't automatically update a variables value until this is clicked - so if you come back and something is blank - go back in and evaluate the expression to see if it shows up the way you expect it to.

Once you're done, your variable window should now look like the following ( with today's date ):

 Final variable setup

 

Now we just configure the File System Task for copying.

File System Task properties

From the top down, we set the "IsDestinatinationPathVariable" to True and set the "DestinationVariable" to our "DestName" variable.

Verify that the Operation is set to "Copy file" - this is the default.

Finally set the "IsSourcePathVariable" to True and set the "SourceVariable" to our "SourceName" variable.

 

Save the package and then it's test time:

Let 'er rip

The package runs successfully and...

New file as expected

When we check "Folder C" - there is our new file as expected.

 

Hope that helps!

Keith Hyer

Print
Categories: Blogs
Tags:
Rate this article:
2.7

Please login or register to post comments.