> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/power-bi/installation.md).

# Power BI (install)

## Power BI installation of JobManager BI <a href="#power-bi-installation-of-jobmanager-bi" id="power-bi-installation-of-jobmanager-bi"></a>

There are two versions for **SaaS** and **OnPrem**. Below is help for both versions. General knowledge of setting up Power BI is a prerequisite.

## SaaS BC <a href="#saas-bc" id="saas-bc"></a>

It is recommended to make initial [setup of BI statistics groups](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/power-bi.md).

### Setup the report <a href="#setup-the-report" id="setup-the-report"></a>

1. Open the included Power BI template `JobManager_BI_SaaS.pbit`\
   *The file is located in the "BI" folder of the JobManager nstallationsfilen (ZIP).*
2. Specify connection parameters.\
   Hover over the (i) icons next to the individual parameters for instructions/examples.
3. Click “Load”
4. Power BI prompts you to sign in to your Business Central account
5. Click “Connect”\
   \
   The report will load data from Business Central\
   Check out the built-in RLS roles. Users must be assigned to a role to use the report in the Power BI Service. The roles are as follows:
   * *All*: All data available
   * *All except pay*: All data available except pay entries.
   * *Calc. responsible*: All data for the employees, that the logged in user is calculation responsible for.
   * *Calc. responsible except pay*: All data for the employees, that the logged in user is calculation responsible for except pay entries.\
     \\
6. Set the default date range by changing the “Filter on all pages: CurYearOffset”\
   E.g. `Greater than -5` (Default value) corresponds to *previous 4 yeas + current year*.
7. Save the report as a `.PBIX` file
8. Publish the report to the Power BI Service
9. Assign AAD groups or individual users to the RLS roles on the semantic model
10. Configure scheduled refresh in the Power BI Service
11. *Optional:* Publish the report as a app to give your audience the best reporting experience

## OnPrem NAV/BC (SQL version) <a href="#onprem-navbc-sql-version" id="onprem-navbc-sql-version"></a>

1. Open the file `JobManager_BI_OnPrem.pbit`.\
   *The file is located in the "BI" folder of the JobManager nstallationsfilen (ZIP).*
2. Enter parameters:
   * `SqlServer`: Server name or IP
   * `SqlDataBase`: BC/NAV database name
   * `RangeStart`: Enter default value as in *info bubble* on then field.
   * `RangeEnd`: Enter default value as in *info bubble* on then field.
   * `BaseAppID`: Enter as given in the *info bubble* on the field.
   * `JmgAppDI`: Enter as given in the *info bubble* on the field.
3. Choose `Load`.
4. Publish the raport to PBI Service.
5. Setup RLS on dataset in the Power BI service (On the dataset select menu item `Security`)\
   Users/AD-groups is added to the individual RLS groups:
   * `All`: Can see all
   * `All except pay`: Can see all - except payroll information
   * `Calc. responsible`: Can see all on the employees for which the user has the Time Calculation responsibility.
   * `Calc. responsible except pay`: Can see all on the employees for which the user has the Time Calculation responsibility - except payroll
6. [Setup the report in BC/NAV](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/power-bi.md).
7. Update the dataset in PBI.

## See also

[Power BI](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/power-bi.md)

## Reference

\
\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/power-bi/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
