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

Internal error: Invalid enumeration value. Please call customer support! is not a valid value for this element.

  • 20 August 2012
  • Author: BradSchacht
  • Number of views: 3322

If you have done a lot of work with SQL Server Analysis Services (SSAS) you may have seen this message:

We've all been there. A build error. I tend to get this because I like to forget commas when modifying calculations in the MDX section of the cube editor. It's a fun little game I like to play to keep myself on my toes...question mark?? Anyway, what follows this message box is usually something that you can go fix, like adding the comma or semicolon back into the calculate script. Sometimes, however, you may see the much less friendly:

Internal error: Invalid enumeration value. Please call customer support! is not a valid value for this element.

If you're like me, the first thing you thought was "Well that can't be good." The second thing I thought was "Well of course that's not valid, there is no customer support number listed." But seriously, if you have attended a Pragmatic Works SSAS workshop or a BI Bootcamp with any number of our trainers chances are you have seen this error pop up. Just about the only time I ever get this message is when I am teaching a class and processing the cube over and over and over.

Occasionally I will get this in development, again when doing small cube changes on my laptop and processing the cube a lot. I have never seen this in a production environment, which is not at all to say it hasn't or won't happen.But for peace of mind before people start freaking out this is not a super common error message to see and even less frequent in production from my experience.


Now for the slightly unfortunate part: The Solution. The only way I personally know how to fix this issue is to go to the SSAS server in management studio, delete the SSAS database and redeploy the solution. The unfortunate part is the cube has to be reprocessed along with all the dimensions which could take a long time if you were just making a small calculation change and ended up with this error. The good news is that all your data SHOULD be available in the source system, and you will definitely have all the cube structure still in your solution inside BIDS (or Data Tools)

Note: While the tabular model has not been out nearly as long as multidimensional (and I have not done extensive development in tabular), to date I have only seen this error in the multidimensional format of SSAS.

Have you seen this error before? Did you have a way to fix this without deleting and redeploying? Have you gotten this same error message while working with tabular?

Rate this article:
No rating


Other posts by BradSchacht

Please login or register to post comments.