I am going through the tutorial and I am a bit confused about the View Tab of the Query Editor.
In the tutorial it's presented as a panel where I would be able to select "Data View" and "Schema View" like here:
When I installed the Power BI Desktop (I tried both 32 and 64 bit versions from here).
I see following items in the View Tab:
I am a bit perplexed whether I am using the same product described in the tutorial since I don't see the expected "Data view" and "Schema view" options.
The tutorial is basing snippets from the Power BI Service, as opposed to Power BI Desktop. Power BI Desktop is the downloadable software that you will use on your local machine. That being said, Power BI Service does allow users to develop reports in the Service. Development in the cloud (Power BI Service) will be very similar to development in Power BI Desktop (the local software), but there are some slight differences. Overall, I believe, Power BI Desktop has more functionality than Power BI Service when it comes to report development.
This may sound confusing, but really its pretty typical of Microsoft's app offerings. Think of Excel and Word, both of which have local software you can download and use. But they also have the minimalized functionality that exists in the cloud.
And to answer your question specifically, no, it appears that Power BI Desktop does not have those views at this time.
Related
I'm researching Microsoft Power BI in order to see if it would be a good fit for my organization. It's important that we can use the graphs made in Power BI on an external facing web application. I've watched videos over Power BI Embedded and all I can find are the solutions that look like an iframe, like a Widget. I want the flexibility to control each component of the report, put the items where they need to get in the web page, but maintain the interactions and data between these elements. Is that possible with Power BI? Does anyone have examples of data visualizations on external facing web applications that aren't wrapped up in an iframe? Any recommended documentation?
Yes you can pick out reporting elements in a Power BI report and embedded them into a web page. The Power BI Javascript api demo, does show some examples
https://microsoft.github.io/PowerBI-JavaScript/demo/v2-demo/index.html
I followed tutorial in the link below to create Power BI Embedded resource.
https://learn.microsoft.com/en-us/azure/power-bi-embedded/power-bi-embedded-get-started
Surprisingly, it failed at step #3 - when i click the Power BI Embedded button, all I get is learn & learn links, no option to create the resource!
Anyone facing this problem?
As far as ventured to solve the problem, I got disappointed as Power BI announced in its website that Power BI service and Power BI embedded came together under a same umbrella beginning this month. So, you need at least Pro license to experience the embedded feature. Closing this as the answer, and thanks guys for all the efforts.
I am currently doing a computer science degree. As part of my industry project for my university, I am developing a BI solution for a client. Having gone though the project I'd like to develop it using Liferay. Does anyone know whether it is possible to embed Microsoft Power BI into Liferay.
The ideal scenario is that the client logs in to a Liferay portal and views power bi dashboards on the portal. Can this be done, is it possible? If so how can this be achieved?
If not what are the alternatives?
I would appreciate your help.
By the way I have to use power bi as part of the project
Well, yes, of course it's possible. What do you need to do? It depends. You can use an iframe immediately or rewrite the reports UI in a portlet. You can even write the whole administrative UI as a portlet. These options were all in increasing amounts of effort you'll have to put into it (and frankly, rewriting all of the UI would be ridiculous, I don't expect you to do this).
You might want to check
Single Sign On for Liferay and BI
Options for BI to be integrated in any other applications, its API (might be: iframe, distinct media - e.g. images, JSON representations of reports etc)
The amount of seamless integration you need - e.g. is an extra click accepted? How many resources (time) do you have to implement the integration?
This was meant to be a comment, but it's too long for that.
PowerBI.com, Power BI for Office 365, or some of the on premises offers like Power View in SharePoint 2013?
For www.powerbi.com, embedding dashboards is something we're looking at. You can vote for it at the link below to keep updated when it is available.
https://support.powerbi.com/forums/265200-power-bi/suggestions/6769940-embed-visualizations-in-an-external-webpage
For Power BI for Office 365, you can embed excel workbooks that contain Power View sheets in web pages, though if you're building an applications this may not be ideal.
Let us know more of the details you're looking for.
Appreciate your using Power BI.
-Lukasz
http://dev.powerbi.com
http://blogs.msdn.com/powerbidev
I am developing a windows 8 app . The app should render the PowerBI charts and reports hosted in a sharepoint site. I need to know whether there is any way to do this. I need to know if it is possible to view the charts made by PowerBI inside a windows 8 app.
Thanks
Thanks for the question. If you'd like to do this with Power View in Office 365, there's a way to do it. You can read about it here:
http://blogs.msdn.com/b/powerbi/archive/2014/12/11/embed-power-view-interactive-reports-in-your-blogs-and-websites.aspx
http://blogs.msdn.com/b/shishirs/archive/2014/02/13/analyzing-search-trends-using-powerbi.aspx
This works for embedding a canned report that is saved somewhere in Office 365. This probably won't work well for your Windows 8 application.
Embedding in applications is something we're looking to add in Power BI, but it's not available right now.
Please submit an idea at the link below to help us prioritize and keep you updated when we add this to the service.
http://support.powerbi.com/forums/265200-power-bi
Appreciate your using Power BI.
Lukasz P.
Power BI Team, Microsoft
If you'd like to stay up to date with the Power BI developer story updates you can register (http://solutions.powerbi.com/appsuggestion.html) or follow our blog (http://blogs.msdn.com/b/powerbidev/)
I've been trying to figure out if it makes sense to use SSRS 2012 with PowerView vs using SSRS 2008.
I've following questions:
What's better in SSRS 2012 without PowerView(ie without using Sharepoint)?
What edition of SharePoint you need to make PowerView work for SSRS 2012?
Does it make sense to learn and use Sharepoint if you can barely utilize the pluses of SharePoint or PowerView instead of SSRS 2008 or SSRS 2012 without PowerView/SharePoint?
I can address the overall question but not the first two bullet points specifically as I have not used Sharepoint enough to give the version differences on it.
Powerview from everything I have ever done is a dll that allows a report like object to be created as an add on to Excel. These objects can then be hosted in Sharepoint in a library. The downside is you need to have the dll's and the add on to Sharepoint to use it. As far as I know you are committing to user's going to SharePoint with this option. They do make it kind of neat though as you generally make what I believe they call a 'PowerPivot' which is just like a client dataset made in the Excel file that you report off of. This option is good for a shop that works with Sharepoint Extensively. I have not heard of too many places using it for client facing front ends or external reporting.
SSRS's newest invocation is SSRS 2012 which from everything I have seen in development is the EXACT SAME THING as SSRS 2008R2 except they put a 2012 in the namespace. There may be minor tweaks on naming and intellisense and under the hood things but the langauge is almost identical. Saying that SSRS 2012 is free with advanced tools for SSRS now and can also port to most front ends you would want: HTML in a form talking to it's service, ASP.NET, a client app like WinForms or WPF. You basically created and host reports and you can access them anywhere.
The real question for most people is: "Which reports look cooler and are easier to use?" I would go with SSRS, but know it is more of learning curve of understanding SQL and a little bit of xml and Visual Studio(very light). However Powerview is more graphical with it's parameters and options to an end user and has highlighted some things it can do with mapping interactivity that SSRS cannot do. The biggest detractor for SSRS IMHO is two things:
It is not event based at all. This shows up whenever you are doing mapping or something you want to zoom or perform actions that then produce other actions or 'events'. It can do a 'click' do something but NOT on the same page necesarrily. Usually you trick it to open a new form for a 'drill through' or use javascript to trick it to do a cheap man's version of hover over reporting by opening a form when you click.
To continue off of one it is this way on default behaviors of values of parameters and passing them down. Everything with SSRS is made to happen once at execution and then anything else happens to leave the form, not stay there.
Saying all that I still like SSRS better. It tends to handle large datasets when PRESENTING them better. Not necessarily all the time at getting them as the PowerView optimizes the set locally but at the expense of huge excel files. Sort of like psuedo cubes. They are fast, but you have a big file size for that expense. But with a lot of data they tend to be clunky as they are Excel based. Yes the query at the end will return faster but you have a huge file. When in reality if you are skilled at SQL SERVER you could be creating a Report Warehouse that is well indexed off of metrics and a cube as well to do this stuff for MANY REPORTS. SSRS is more for developers of TSQL, versus PowerView is more for analysts that know a little SQL but love Excel. They want a 'Select * from (table)' and then form the data, not they know how to do advanced groupings on their set first and then want to present a finished product to someone.
To answer your questions one-by-one:
What's better in SSRS 2012 without PowerView(ie without using Sharepoint)?
In "native mode" SSRS, i.e. a non-Sharepoint installation, there's not an awful lot of new stuff. The renderer now supports Word/Excel 2007-2010 format (i.e. DOCX, XLSX) output and the addition of native mode Data Alerts seem to be the only real difference to 2008 R2.
What's new in SSRS 2012
What edition of SharePoint you need to make PowerView work for SSRS 2012?
Unfortunately, you need SharePoint Enterprise Edition.
Does it make sense to learn and use Sharepoint if you can barely utilize the pluses of SharePoint or PowerView instead of SSRS 2008 or SSRS 2012 without PowerView/SharePoint?
If you are only looking at SharePoint to host/share PowerView and SSRS, it's definitely not worth the investment, in my opinion. There are other alternatives now that are much more accessible to smaller organisations, or those who don't want to invest heavily in SharePoint infrastructure.
PowerView is built in to Excel 2013, which allows users to build their own PowerView reports. Until recently though, there was no way to share these other than passing the Excel files around. However, Microsoft have now released the preview of Power BI, which is an Office 365 based BI platform, essentially providing SMEs with a cheaper and easier alternative to setting up a SharePoint server, and allowing self-service BI. It enables users to upload their Excel files containing PowerViews and share them with their organisation. You can also share other creations, such as Power Query projects, and internal data sources. All without an on-site SharePoint installation.
If you really want to try out PowerView, I'd suggest getting yourself a trial of Excel 2013, or sign up to the Power BI preview and give it a shot. Personally, I wouldn't recommend upgrading to 2012 purely to upgrade your SSRS installation, the new native mode features aren't really worth the cost/effort. If you're looking at upgrading the rest of your infrastructure though, (SQL, SSAS, SSIS) then it's definitely worth doing.
also wanted to add that if your deploying from VS to sharepoint directly; you versions have to be close together i.e. 2008 ssrs on sharepoint 2009 etc. You may not be able to deploy a rdl built in 2008 on sharepoint 2012,13. We had similar issues at one of my previous projects.