> 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.md).

# Power BI

The JobManager installation includes ready to use examples.

Power BI, the perfect tool for analysing all registrations made in JobManager.

Power BI makes it easy to access your data through reports and dashboards. All important information is stored, and you can easily visualise significant trends and developments in your business. Power BI can be set to be updated regularly (available on a daily basis).

The registrations are available for update after they have been calculated, approved and for payroll records, generated earnings.

* The front page shows graphs for the past six months.
* Separated by means of statistic groups that deal with both time records, the original registrations and salary records. Salary records are time records that have been processed by using the rules set out in the wage agreement.
* It is possible to export to PDF, PowerPoint or print.
* Get a quick overview by subscribing and receiving an email in your inbox as often as you wish. The email shows the page you interested in, as well as a link for quick access.
* If there is something that needs further investigation, it is possible to create a comment that can be sent to a specific employee for further investigation. The mail that is sent, contains a link with the same information that you want to be examined, with the same filter. A fast and effective tool that leaves nothing to chance.
* Drill-down by right-clicking and select Drill-down. A detailed report opens with the desired time or salary records.

Detect trends on both time and salary items per employee or per month. Trends in weekly profile and work type distribution. In the company as a whole or specific departments or groups. There are many filter options available.

All useful tools for many levels of management.

You can edit the statistics groups setup in Business Central at any time. After a change in the setup has been made, wait until the next scheduled refresh has been completed or trigger a manuel refresh of the semantic model. After the update, the report will automatically inherit the changes.

Changes will also reflect historical data (but will not affect them).

**SETUP GUIDE FOR&#x20;*****STATISTICS GROUP*****&#x20;IN NAV/BC:**

The statistic groups are defind in [Jobmanager Bi Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-bi-group-6182367.md)

Here you select which groups you want to collect data on:

* JobManager BI Mapping (Journal Entries / Journal Stamps.)
* [Time Counters](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-counters-6182411.md) (Time Entries)
* [Paytype](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-6182551.md) (Pay Events)

[Column No.](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-bi-group-6182367.md#field-2) defines the order off the columns in the BI Report.

[Caption](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-bi-group-6182367.md#field-3) Is the Caption of the Column in the i BI report.

**JobManager BI Mapping**

Journal Entries is a Comsumption of the registrated time - The raw time from the modules (IPC, Job/project, production. etc.).

Useful tool when you want insight in procceses.

*JobManager BI Mapping* is a subtable (In JobManager Bi group) Where you can combine *Journal Stamps*.

Examples:

| Ref.Type      | Level 1        | Level 2                                | Worktype |
| ------------- | -------------- | -------------------------------------- | -------- |
| IPC           | IPC Categori   | IPC Activity                           |          |
| Job           | Resource group | Resource                               | Worktype |
| Production    | Work Centre    | Prod.resource (NAV)/ Machincentre (BC) |          |
| Serviceordre  | Resource group | Resource                               |          |
| Assemblyordre | Resource group | Resource                               |          |

The scenarios are defined from the top down, that it is sufficient to specify an overall combination, that consump the underlying hours. E.g.:

* Ref.type = Everthing under that ref.type
* Ref.type + Level 1 = Everthing under that ref.type and level 1
* Ref.type + Level 1 + Level 2 = Everthing under that ref.type and level 1 and level 2

On Job/Projekts you can combine the combinations above and add a worktype.

Every combination must have a short description, that is usefull if you make a *drilldown* on the Column header in the BI Report.

You can make several combinations that covers over the same data, without counting doubble in the BI report.

**Time Counters**

Shows the calculated time in relation to the *Time Schedule*, which can be split up on std. hours, overtime, absence etc.

When the column no. and caption are filled out, the specific Time Counters must be *mapped* with a [BI Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-counters-6182411.md#field-8000) on the [Time Counter](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-counters-6182411.md).

To get the best results on the Power BI report, it is important that *Column no.* 99 gets filled out with std. hours/profiletime Time Counter. Then you can make the right percentage calculation e.g.. how many % absence compared to the profiletime.

**Pay Type**

Shows the calculated *Pay Events* in relation to the Agreement rules. Time and Rates (If you have them in JobManager) will be calculate per *Pay Type*. i.e. It can be calculated ind time and amount - e.g. The cost if an Employee has been sick in X number of days.

When the column no. and caption are filled out, the specific Pay Type must be *mapped* with a [BI Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-6182551.md#field-8000) on the [Pay Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-6182551.md).

When NAV/BC BI Groups and mapping is set up, the information must be updated in the Power BI, before it shows any data.

## See also

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

## Reference

[JobManager BI Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-bi-group-6182367.md)\
[Time Counters](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-counters-6182411.md)\
[Pay Type](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/pay-type-6182551.md)

\
\\


---

# 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.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.
