<\/p>\n\n\n\n
Power BI Licensing<\/h2>\n\n\n\n
No additional Power BI license<\/strong> is required to use the cBI Focus Planner within Power BI<\/strong> Desktop<\/strong>. In this scenario, an existing internet connection and the ability to download the custom visual from the Microsoft AppSource Marketplace and embed it locally into a report are sufficient. This setup is particularly suitable for development and testing purposes or for use in smaller, locally operated environments.<\/p>\n\n\n\n However, for productive use<\/strong>\u2014especially when deploying the application to end users\u2014it is recommended to use the Power BI Service<\/strong>. This requires at least<\/strong> a Power BI Pro license<\/strong>. Only with this license is it possible to centrally publish created reports and share them specifically with other users, such as planners. This becomes especially important when multiple users are working with the visual simultaneously or when centralized management and control of content is desired.<\/p>\n\n\n\n Regarding data connectivity, both Import mode<\/strong> and DirectQuery<\/strong> are supported in<\/strong> Power BI Desktop<\/strong> and are compatible with cBI Focus Planner. However, in<\/strong> the Power BI Service<\/strong> with a Power BI Pro license, DirectQuery is mandatory<\/strong> if automatic visual updates after data write-back are required. If Import mode is used instead, data changes can still be saved, but the visuals in the report will not update automatically\u2014significantly limiting the user experience.<\/p>\n\n\n\n If you still wish to use Import mode in the Power BI Service<\/strong> with automatic updates, a Power BI Premium<\/strong> license is required<\/strong>. This license enables access to an XMLA endpoint, which allows Import models to be refreshed via a technical interface.<\/p>\n\n\n\n See the following overview for details on Microsoft\u2019s available plans and licensing models: Power BI: Pricing | Microsoft Power Platform<\/a><\/p>\n\n\n\n <\/p>\n\n\n\n The current version<\/strong> of cBI Focus Planner exclusively supports Azure SQL Server<\/strong> instances. Other database technologies or on-premises SQL Servers are not supported at this time.<\/p>\n\n\n\n To ensure successful operation, both the network connection and the underlying data model must meet specific requirements, which are described in the following sections.<\/p>\n\n\n\n <\/p>\n\n\n\n To ensure reliable communication between the Azure Functions, Power BI, and the Azure SQL Server instance in the customer\u2019s tenant, appropriate firewall rules<\/strong> must be configured. Specifically, the IP addresses or IP ranges of the Azure Functions and the Power BI service must be allowed access to the database.<\/p>\n\n\n\n There are two main options for configuring IP access:<\/p>\n\n\n\n These permissions can be configured directly in the Azure Portal or via a Bash or PowerShell script.<\/p>\n\n\n\n Note: The IPv4 addresses of the Power BI service change periodically.<\/p>\n\n\n\n To integrate with cBI Focus Planner, a dimensional data model in the form of a star schema<\/strong> is required. The star schema is a widely used database structure, particularly in data warehousing and business intelligence. It supports multidimensional data modeling and is designed to optimize query performance and simplify data analysis. The key characteristics of the star schema are as follows:<\/p>\n\n\n\n 1. Fact and Dimension Tables<\/strong><\/p>\n\n\n\n Fact Table: This central table contains the quantitative data (transactional data) to be analyzed, such as sales figures, revenue, or other key performance indicators. Each row in the fact table represents an event or transaction.<\/p>\n\n\n\n Dimension Tables: These tables contain descriptive attributes (structural data) used to analyze the facts. Typical dimensions include time, product, customer, and location. Each dimension table has a unique key column that links to the fact table.<\/p>\n\n\n\n 2. Simple Structure<\/strong><\/p>\n\n\n\n The star schema features a clear and intuitive structure, with the fact table at the center and the dimension tables arranged around it like spokes. This layout simplifies data navigation and understanding.<\/p>\n\n\n\n 3. Clear Relationships<\/strong><\/p>\n\n\n\n Each dimension table is directly linked to the fact table, meaning there are no complex joins between dimensions. This direct relationship improves query performance and simplifies SQL queries.<\/p>\n\n\n\n 4. Denormalization<\/strong><\/p>\n\n\n\n Dimension tables are often denormalized, meaning they may contain redundant data to enhance query performance. While this increases the size of the dimension tables, it typically results in faster query execution.<\/p>\n\n\n\n 5. Simple Queries<\/strong><\/p>\n\n\n\n Thanks to its clear structure and direct relationships, queries in a star schema are generally easier to write and understand.<\/p>\n\n\n\n cBI Focus Planner requires a structured data model to perform targeted write-back operations. Only when the origin of a value can be clearly identified is precise data updating possible. The star schema ensures that:<\/p>\n\n\n\n The use of star schema relationships is therefore a mandatory requirement for the correct and reliable operation of cBI Focus Planner, as it enables the visual\u2019s write-back logic.<\/p>\n\n\n\n To ensure secure and controlled data exchange between Power BI, the cBI Focus Planner backend, and the SQL database, two separate user roles are defined: the READ<\/strong> user<\/strong> and the WRITE user<\/strong>.<\/p>\n\n\n\n READ User<\/strong><\/strong><\/p>\n\n\n\n The READ user is responsible for establishing the connection between Power BI and the Azure SQL Server. This user is granted read-only access to the database.<\/p>\n\n\n\n It is important to note that a dedicated database user is not strictly required for read access. Instead, Power BI supports native authentication methods, allowing for a flexible and user-friendly connection to data sources.<\/p>\n\n\n\n Available authentication methods are:<\/p>\n\n\n\n It must be ensured that at least one READ user exists who can authenticate with the Azure SQL Server using one of the methods listed above. WRITE User<\/strong><\/p>\n\n\n\n The WRITE user is primarily responsible for writing data back to the database, but is also used for queries required for validating the modelling of the cBI Focus Planner.<\/p>\n\n\n\n Due to technical limitations in Power BI, it is not possible to forward the logged-in Microsoft or domain user credentials for write operations. Therefore, additional configuration is required within the cBI Focus Planner settings (see here<\/a>). To enable this, at least one SQL database user must be created in Azure SQL Server and granted the necessary permissions.<\/p>\n\n\n\n It is recommended to restrict this user\u2019s access rights to only those data areas that are relevant for planning or control purposes. This ensures that no unauthorized write access to sensitive data can occur.<\/p>\n\n\n\n The minimum required permissions for the database user are:<\/p>\n\n\n\n <\/p>\n\n\n\n For initial testing, a publicly accessible sample report is available via Microsoft AppSource. This report includes a fully preconfigured demo application with the cBI Focus Planner embedded, and it can be used without a purchased license. The write-back functionality is also active within this sample report, allowing you to realistically test how the visual works.<\/p>\n\n\n\n Please note that the write-back functionality only works with the demo database included in the sample report. Connecting to your own SQL Server instance is not possible in this mode. A valid license is required to connect to your own databases.<\/p>\n\n\n\n![\"\"](\"https:\/\/cbi-focus.com\/wp-content\/uploads\/2025\/06\/OverviewOfSupportedImportMethods-1024x600.png\")
<\/figure>\n\n\n\nSQL Server Configuration<\/h2>\n\n\n\n
Network Requirements and Firewall Configuration<\/h3>\n\n\n\n
\n
T<\/strong>his setting allows all Azure services and resources to access the SQL Server\u2014at least at the network level. It is important to note, however, that valid SQL database user authentication is still required despite this access. This option provides a quick and easy way to establish connectivity but should be used with caution.<\/li>\n\n\n\n
A more secure and targeted approach is to allow only the specific IP addresses that are actually needed. These include:\n
Enabling the Option \u201cAllow Azure services and resources to access this server\u201d<\/strong><\/h4>\n\n\n\n
\n
![\"\"](\"https:\/\/cbi-focus.com\/wp-content\/uploads\/2025\/06\/EnablingTheOptionsAllowAzureServicesStep3-3-1024x431.png\")
<\/figure>\n\n\n\n\n
![\"\"](\"https:\/\/cbi-focus.com\/wp-content\/uploads\/2025\/06\/EnablingTheOptionsAllowAzureServicesStep6-2-1024x301.png\")
<\/figure>\n\n\n\nExplicit <\/strong>Whitelisting <\/strong>of individual IP addresses<\/strong><\/h4>\n\n\n\n
\n
![\"\"](\"https:\/\/cbi-focus.com\/wp-content\/uploads\/2025\/06\/ExplicitWhitelistingStep2-1-1024x522.png\")
<\/figure>\n\n\n\n\n
![\"\"](\"https:\/\/cbi-focus.com\/wp-content\/uploads\/2025\/06\/ExplicitWhitelistingStep3-1-1024x635.png\")
<\/figure>\n\n\n\n\n
![\"\"](\"https:\/\/cbi-focus.com\/wp-content\/uploads\/2025\/06\/ExplicitWhitelistingStep6-1-1024x398.png\")
<\/figure>\n\n\n\n\n
![\"\"](\"https:\/\/cbi-focus.com\/wp-content\/uploads\/2025\/06\/ExplicitWhitelistingStep9-1-1024x781.png\")
<\/figure>\n\n\n\nData Modeling: Star Schema as a Requirement<\/h3>\n\n\n\n
![\"\"](\"https:\/\/cbi-focus.com\/wp-content\/uploads\/2025\/06\/image-11.png\")
<\/figure>\n\n\n\nStructure of the Star Schema<\/strong><\/h4>\n\n\n\n
\n
<\/strong>The fact table is at the center of the model. It contains the numerical key figures to be analyzed as well as the primary key, which is a composite key referencing the various dimension tables. A surrogate key is used to uniquely identify each data row in the fact table.<\/li>\n\n\n\n
<\/strong>These tables contain descriptive attributes used to categorize and filter the facts, such as \u201cTime,\u201d \u201cProducts,\u201d or \u201cCustomers.\u201d<\/li>\n<\/ul>\n\n\n\nPurpose in the Context of cBI Focus Planner<\/strong><\/h4>\n\n\n\n
\n
User Configuration<\/h2>\n\n\n\n
\n
<\/del><\/strong><\/p>\n\n\n\n\n
cBI Focus Planner Licenses<\/h2>\n\n\n\n