Third article from a series on [ #Office365 ] Power BI 2.0 :
As described in the previous post, there are basically three types of sources in Power BI: files databases and services.
Here is a detailed view of the sources supported in the Designer and on the Web authoring tool:
Content packs are a cool way to prebuilt a data model for a specific data source. Accessing to it your end-user will be able to quickly define great reports.
The preview gives access to 17 content packs and much more were announced at MS Ignite;
I am especially awaiting the Office 365 content pack which will allow us to query the utilization data of our Office 365 tenant.
Here are two samples:
It was also announced that for GA they will introduce Organizational Content Packs which will allow users, BI professionals and system integrators to build their own Content Packs to share purpose built dashboards, reports and datasets within an organization for others to consume and gain business insights.
That’s cool but technically what is a Content pack?
A content pack can include the following components:
- Data model
- Optimization for natural language query
- Connectivity, if needed
It provides instant insights for a role, domain, or workflow of your service
- Adds monitoring, analytics, exploration, and sharing of insights
- You don’t need to invest heavily in reporting infrastructure
- Visible to any user of Power BI
- Enable mashup of data from your service with data from other services
- Enforces authentication/authorization to your service’s data
One last but not least thing to know is that a dataset in Power BI can store up to 200,000 rows. When this limit is reached, new data push oldest data out in a FIFO logic: