I'm interested in creating some dashboards for clients. They will contain some sensitive data, so I plan on putting them behind an authentication wall (ASP.net, most likely). The dashboard will allow for filtering and sorting, but no data entry or deletion. Each dashboard will be fed by an Excel file.
My company suggested using Microsoft Power BI, but BI for web doesn't allow for private/confidential data, and any other method of sharing would require the client to have a Power BI license.
I also considered Tableau but ran into similar issues.
So broadly speaking, what's the best platform for creating web-based visualizations that can be embedded into a page?
Thanks
Power BI gives you - Azure AD authentication ,
- row level security to data
So Power BI will be better option
Related
I'm searching if I can use tool like tableau or power bi to create dashboards fast and display it to the clients in my system
The data cannot be shared publicly
I searched and found the Power BI and Tableau embedded
Didn't use it, and want to know more cause I'm comparing between creating the dashboards manually or using this solution
But need to know if someone used it before, what's the limitations, value, and the pricing,
Thanks in advance
I have this requirement in my company in which we want user to be only able to access BigQuery from either from GCP console (using any network, it doesn't have to be from our company network) and Looker BI tools that we use in our company.
We want to prevent access so that the BigQuery isn't accessible using any other tools such as BI tools such as Power BI, MS Excel, etc. The reason is because we'd like to prevent users from downloading and exporting data using this unauthorized BI /3rd party Tools.
The issue is that based on our test as long as user has viewer access to BigQuery, then they can use any compatible BI tools to connect to BigQuery, create tabular visualization and then export the data from there.
Is there any way to prevent this from happening ?
Thank You
i write an web application for wrapping power bi report server web portal(on-premises),my users have access to folders or category items(all of kind such data source) without seen the web portal and they see my user interface.
i want to integrated dashboard in my ui. the simple way is embed by adding "?rs:embed=true" to end of url of that report url.
our database are so huge and full of data(average 5 million rows for each table) and when i embedded it this may take a time for rendering.
i wanna better way to integrated my dashboard or report or kpi with best time to rendering.
we have few solution for this like urlaccess or wmi provider or report view control or rest api.which one is better? and have more less time of loading reports?
can i simulate a backend system(or client side) like report viewer control for viewing reports directly?
can you show me link for .net core example(code) of this work or like this work?
thanks alot
mohammadreza daneshvar
You can write an intermediate program and the customer can communicate with the Power BI server By your own API. so you can define your access level and customization your dashboard. this way is fast and easy
Visualization tools like tableau, looker, apache superset are not supposed to be used for multi tenant products.
For example. A product with 1000's of users would like analytics on their data. This needs to be secure so company A cannot see other company B visualizations. For this to work these tools need to understand if a user has privileges to view the data. This is usually achieved through cookies after the user has logged in
To ensure data is only accessed by authorized users these third party tools should not be used. Instead sticking to Ruby on Rails with d3js, highcharts etc is the best options. The data can be managed a lot easier through the same authentication methods as you login and so the data is secure.
Actually, Looker handles multi-tenant data situation just fine. It is quite a common use case for Looker.
You can bind attributes to users that will force the right SQL to be written to guarantee that the user only sees appropriate data.
https://docs.looker.com/reference/explore-params/access_filter
We've got lots of customers building extranets for their businesses this way.
Disclosure: I work at looker.
The complexity of multi-tenant deployments goes far beyond the setup of some filter:
Data privacy - you are one typo away from a data privacy breach with the filters. You should use the database security and privacy capabilities to isolate your tenants.
Performance - you need to scale the underlying database to handle the load of concurrent users.
Customization - your tenants might need to load and analyze their own custom data. They need custom reports, etc.
Take a look at gooddata.com and their workspaces.
Disclosure: I work at GoodData
I'm starting on some architecture work for a .Net based social networking application to be hosted on Azure cloud. we are going to be using ASP.NET MVC on the front end.
i would like to consider the options for storage. considering scalability needs and due to the inter-connected nature of the application, SQL azure has been ruled out.
what would be the main considerations in choosing a graph DB such as Sones GraphDB or neo4j which have features specific for a social networking application against using windows azure table storage to achieve the needs.
i'm mostly concerned about development time, cost, ability to leverage existing skills like .NET and reliability of the graph DB platforms and ease of setup and administration.
Graph databases are designed for applications such as social networks. For ease of development, it may be best to start with something like GraphDB. A key advantage over a key-value database is powerful query and traversal capabilities. It would be easy to, for instance, find all occurrences of friends of friends using the GraphDB query syntax.
The benefit of a key-value database service like Azure Table is low cost, minimal administrative overhead and scalability. You can store 500TB of data per Azure storage account and setup accounts in multiple regions. There is no server setup or database administration overhead and the Visual Studio SDK is easy to use. The down side is that graph like query support is not built in and you must index off the Primary Key / Row Key pair. For additional Azure Table design pattern please see https://azure.microsoft.com/en-us/documentation/articles/storage-table-design-guide/