And your users can also switch to the native version of their app. Please keep in mind: Native apps are the first choice in performance and functionality. Compared to the native app, the functionality of your web app may be limited simply because they are browser-based. If you are meeting some difficulties and would like to ask us questions about embedding apps to your website, or if you want to share your opinion with us, leave us a comment below or contact your Open as App team!
Posted by Angelika Methner on March 23, Topics: Features. The app is inserted after publishing via an HTML snippet. If I clicked in any of the Product or Segment checkboxes called slicers in Power BI , it filters the data and only shows the data from the selected product s or segment s. Power BI includes a good set of built-in visuals, and you can easily go way beyond those by tapping into the large and vibrant Power BI Marketplace, which contains both free and paid visuals that you can use in your reports as well.
Power BI is a platform for business intelligence data visualization. It has a big ecosystem associated with it, so let me clarify some terminology and what parts of it I'll be focusing on in this article. Power BI has several ways users work with it. Power BI Premium depends on how many users you will have and how much guaranteed capacity you need.
Power BI Service lets you view, manage, and configure reports and dashboards that you want to share with other Power BI users through a Web portal interface that is a SaaS application itself. Power BI Mobile is a mobile app that you can use to view reports and dashboards that your Power BI account has access to on your mobile devices. With Power BI Embedded, you can take the reports you design, integrate them into your Web, desktop, or mobile apps, and allow any of your application users to see them without requiring Power BI accounts for each user.
You can still authenticate your users the way you already do, and can pass the context of the user, as well as app parameters, down into the reports and dashboards that get rendered into your application.
The way they do this is simple conceptually: The reports can be rendered into a Web page through an embedded iframe. To do this easily, you use the Power BI client libraries that work for any browser application which also includes embedding a Web view into a desktop or native mobile app , and Power BI renders your reports and dashboards into the content of a div that you identify within your pages.
Let's dive right into building a sample. NET Core for my back-end, but you can do what I'm going to show in any Web front end, regardless of which front- or back-end frameworks you're using. I'll also cover doing the same thing with an ASP.
You can't have data visualizations without data, so let's start there. Power BI has a lot of different ways to connect to data. If you need your data to be a little more real time, you can also create DirectQuery connections to databases, which results in the report being rendered directly from the data in the database at the time the report is rendered.
For my sample application scenario, I'm going to use some simple financial data representing sales of some products. The data includes various numeric fields for sales amount, profit, cost of gross sales COGS , and a few other sales-related fields that you might want to report on if you were in a sales organization. DirectQuery enables your reports to be rendered in real time from your database, as well as enabling row-level security filtering so that users only see the data they're authorized for in your reports.
Your data doesn't have to be in the cloud for Power BI to connect to it, because Power BI supports data gateways that let you get to on-premise databases or APIs as well. But if the data is already accessible in the cloud, it makes things a lot easier.
DirectQuery enables your reports to be rendered in real-time from your database, as well as enabling row-level security filtering so that users only see the data they're authorized for in your reports. The sample application code includes a SQL script and instructions to set up an Azure SQL Database, as well as a Power BI desktop file that has the data all imported so you don't have to set up any back-end database if you just want to experiment with rendering a static report in your app.
Figure 2 shows the relational data model of the data I'll be working with, displayed in the Power BI Desktop relationships view. As mentioned earlier, to start working with Power BI, you need an account. These are different from a personal Microsoft Account set up with an email account that you own.
You can create one of these on your own, even if you don't have an account with an organization. The steps are a little involved, but I've included a step-by-step guide on doing so in the download sample code so you can get up and running on your own. Once you have an organizational account, you must create a Power BI Pro subscription for that account. That gives you 60 days to work with it and experiment without needing to pay anything.
Once you have a data source set up that you're going to pull data from and a Power BI account, you can download and fire up Power BI Desktop and start defining a report. Once you launch the app and sign in with your Power BI account, you can connect to a data source with the Get Data button in the ribbon at the top, as shown in Figure 3. In the Get Data dialog that comes up, you can select from the wide variety of data sources supported. I then enter the name of the database server I'm connecting to, as well as the name of the database, and select DirectQuery because I want the report to get the data from the database each time it's rendered, as shown in Figure 5.
The next step has you select which tables from that data source you want to work with and gives you a preview of the data in the Navigator view, as shown in Figure 6. That's not the focus of this article though, and I'm using a simple data source that's already in the shape I need to start hooking up to reports. If your database has foreign keys defined between the tables, the designer can pick those up and set them as relationships in the data model. If it doesn't, you can just switch to the Relationships view, as shown in Figure 7, and define those quickly yourself.
Once in the relationships view, you can drag the tables around and use drag-and-drop gestures to define relationships between the tables. To do so, you simply click and drag on a field in one of the tables and drop it onto the other table. The dialog shown in Figure 8 pops up and lets you select the columns that you're matching up and the direction of the relationship. Once your relationships are defined, you can switch back to the Report view using the top tab on the left side of the designer.
From there, I can pretty much drag-and-drop my way to a nicely defined report. For the sample report for this article, I created the first visual by doing the following:. In a similar fashion, you can add other visuals and hook up the appropriate fields from the tables to expand to a multi-visual report. These are basically filter inputs, typically connected to some of the lookup tables in the data model Product, Segment, and Country in the sample data , that allow the user to make selections in the report that will filter the data presented based on the selections.
The final report definition included and used for the rest of the article is the one shown back in Figure 1. Once the report is ready to go, you have to publish it to the Power BI service using the Publish button at the far right of the ribbon bar. To do that, you have to first create a Workspace in the Power BI service that you'll publish the report to. Creating a workspace basically just requires you to give it a name.
Once you've done that, you can publish from Power BI Desktop and it'll give you a list of your workspaces to choose from to contain the report. Once you select one, it publishes to that workspace. At the completion of publishing, Power BI Desktop shows a warning about not being able to connect to the data source.
This is because it doesn't want to blindly publish your report along with the database credentials embedded for security reasons. In the dialog with that warning, it has a link to go open the. When you click on that, it opens the report in the Power BI Service portal and has a link for you to provide the database credentials to get it hooked back up to your data source from there.
To do so, you select your workspace from the left navigation bar, and then it shows the view in Figure Select Datasets in the menu along the top, click the ellipses Enter your database username and password and click the Sign In button. While you are in the Dataset settings, take note of the Dataset ID in the address bar of the browser, as shown in Figure 13 ; you'll need this later to apply security filtering to the data set.
Now your report should be ready to go for embedding. So, instead of forcing users to rely on another mapping app to find your location, they can simply find you through your app.
It makes life easier for them — which means lower churn rates for you. And, most of us have used Google Maps or MapQuest to help us navigate unfamiliar streets. Although no one knows exactly how much Google invested to build its hyper-complex Google Maps software, we imagine the figures must have been astronomical.
Still, its efforts have paid off in huge dividends. Embeddable mapping tools are pieces of code you insert into an app to offer users mapping capabilities. The question should be: why not take advantage of the opportunity to embed a map on your app for free? Lego and Chrome teamed up for Build with Chrome , an experiment that gamified mapping by allowing users to build Lego objects on Google Maps.
Google Maps is the de facto map service on the planet. Daily, over a billion people tap into Google Maps to navigate their way around town. You can also use Google Maps Platform to add an API to your app or web app, a better option if you want to offer more complex mapping capabilities. For its part, Bing has a user-friendly API, high-resolution mapping images, and virtually all the same features as Google Maps.
All things considered, Bing does some things better than Google. We like its detailed travel instructions, traffic updates, and traffic camera images. Google Maps dominates mobile it virtually captures the entire market.
0コメント