This page collects MDriven documentation relevant to Power BI integrations. The supplied documentation does not describe a complete, supported Power BI setup; confirm the appropriate architecture, credentials, and refresh configuration for your deployment.
Relevant MDriven integration topics
Documentation:Integration lists REST API integration, exposing REST services, web API integration, and data import/export topics. Use those guides when designing an integration between Power BI and an MDriven application.
The MDriven Framework API documentation is available at Documentation:Api documentation.
Database deployment considerations
MDriven production deployment packages are available with PostgreSQL, MySQL, or MSSQL database options. In the provided Docker Compose configurations, the selected database and MDriven Server are placed on the same internal network, and the documentation states that this allows database communication without exposing the database to the public internet.
Before making database data available to a reporting system, review the deployment and network design in Documentation:Configuring Production Databases PostgreSQL MySQL MSSQL. In particular, do not assume that a database in the supplied Docker configuration is reachable from a reporting service outside that internal network.
For Microsoft SQL Server and Azure SQL connectivity, Documentation:Microsoft.data states that MDrivenServer changed from System.Data.SqlClient to Microsoft.Data.SqlClient, including support for the Azure SQL connection-string mode ActiveDirectoryIntegrated.
Refresh design
A MDriven cache-invalidation design can be used to react to production-data changes. The cache-invalidation walkthrough describes an example in which a cache-invalidation module calls a REST API to initiate a Power BI refresh. This is presented as an architectural possibility, not as documented product configuration.
Watch the cache-invalidation walkthrough.