Skip to content

Dyflexis Power BI dashboard

We bring together hours, absences and busy periods from Dyflexis by department in a single Power BI model. We developed a data platform for the Concertgebouworkest.

For Koninklijk Concertgebouworkest, we developed a future-proof data platform that connects data from multiple systems

The wealth of information gathered over the orchestra’s history was scattered across different systems, archives and data sources. By connecting, structuring and standardising that data, we make information easier to find and avoid duplicated work.

Read the case study

Did we have enough staff on the floor on the busiest night of the season, and how much did it cost?

Dyflexis brings schedules, hours worked, revenue and staffing costs together in its own dashboards, broken down by location and department. If you want to compare busy periods, absences and payroll periods across seasons with ticket sales or accounting records, you can pull the data into your own model via the API.

Book a conversation

Staffing, activity levels, sickness absence and closed payroll periods from Dyflexis come together in one model for each department

Discuss your staffing

Scheduled versus recorded

Scheduled shifts alongside hours recorded after clocking in and out, by location and department, across all seasons.

Staffing alongside demand

Workload from your information sources, such as visitor numbers, transactions or revenue, alongside scheduled staffing by hour or by day.

Sickness absence by department

Sickness reports and returns to work by department and period. Dyflexis can send a webhook for each sickness report, allowing the data ingestion step to update immediately.

Alongside your other sources

Dyflexis data alongside ticket sales, payroll and accounting, as we did when we connected and standardised data from multiple systems for Concertgebouworkest.

We agree how to handle the department hierarchy and pay periods before the first report is ready

  1. Department hierarchy and definitions

    Which locations and departments from the department hierarchy to include, which hours count as recorded, and how absence is counted for each department.

  2. A token with the right scopes

    A Dyflexis administrator requests a token through support, with only the scopes the report needs.

  3. Refreshing at the right time

    A scheduled refresh during working hours, with the hours for each pay period loaded only when Dyflexis confirms that the period has closed.

Why build your own Power BI model when Dyflexis already has dashboards?

Discuss it with us

A good fit if

You have multiple locations or pronounced seasonal peaks, want to view staffing alongside ticket sales, budgets or accounting data, or have a BI team that wants Dyflexis in the same model as the rest of the organisation.

Not a good fit if

The dashboards and reports in Dyflexis already answer your questions about schedules, hours, revenue and staffing costs by location, and you don’t need to add other data sources. In that case, your own model adds little value.

What determines the scope

How many locations and departments are involved, which data flows you already track, whether sickness absence and pay periods need to be included, which other sources you want to use alongside Dyflexis, and who will manage the model afterwards.

Is the API included in our plan?

According to Dyflexis, that depends on your plan; its pricing page shows which integrations are included. An administrator requests the token from support. We’ll work that out together before we build anything.

Dyflexis dashboards, the API to Power BI, or staff, ticketing and finance in one data warehouse?

Dashboards in Dyflexis

Choose this if Dyflexis is your only data source. It compares locations by schedules, hours worked, revenue and staffing costs, and also offers connections to BI tools.

The API to Power BI

Choose this if you manage hours, absence and demand across locations and seasons. Our advice: store historical data in your own loading process and retrieve pay periods only after they have closed.

Everything in one data warehouse

Choose this if staff data is only part of the picture and you also need to bring together ticketing, payroll and finance. See how to build a data warehouse.

Bringing data from disparate systems together into one usable whole is something we do often

Since 2016, Data Science Lab has built solutions with data and AI as a Microsoft Partner for Fabric. We developed a data platform for the Concertgebouworkest and assessed data maturity for the Albert Schweitzer Ziekenhuis.

Book an introductory meeting

Your locations, your Dyflexis package and the peak periods you want to understand are at the heart of our first conversation

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your first point of contact. In our first conversation, we’ll discuss your locations, your Dyflexis environment and the questions your dashboards currently leave unanswered.

Which departments and peak periods do you want to see in Power BI using data from Dyflexis?

Tell us how many locations you have and which point-of-sale, ticketing or payroll system you use alongside Dyflexis. We’ll then email you back or schedule an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

The Dyflexis API is designed for this. Its developer documentation lists business intelligence as a use case, with Power BI as an example: retrieving scheduled hours, recorded hours and payroll periods. A Dyflexis administrator requests the token from support. We load the data in a separate step and build the model on top of it.

We explain why a dashboard starts with the question someone needs it to answer on our Power BI dashboards page.

For reporting, Dyflexis lists scheduled shifts, hours recorded through clocking in and out, employees, the hierarchy of locations and departments, and sickness absence. It also provides payroll periods with hours per day, contract types and information streams containing workload data.

The API is documented according to OpenAPI 3.1, with the required scope specified for each endpoint. Leave other than sickness absence has no dedicated endpoint: it appears as an hour type in the hours for a closed payroll period, by department.

Dyflexis uses information streams: a till or another system sends the actual workload, such as visitor numbers, transactions or revenue per hour. These data points can also be retrieved through the API.

In the model, we place them alongside scheduled and recorded hours by department. This shows you whether staffing matched demand for each performance, event or peak day.

You retrieve sickness reports through the absence section of the API. Dyflexis also sends a webhook when a sickness report is created or an employee returns to work. You register the webhook receiver through Dyflexis itself, not through the API.

For the broader absence figures that HR tracks, see the HR dashboard in Power BI.

Once the payroll period is closed. Dyflexis signals this with the Payroll period ready webhook, or you can read the queue of completed periods. Only then are the hours per day finalised.

For a view of today, Dyflexis says that refreshing hourly during working hours is more than enough for most dashboards.

Yes. According to the documentation, requests are limited per token; if you make too many, you receive a 429 response. Lists are paginated, with a maximum of 100 employees per page for payroll administration.

That is why we load data incrementally, wait progressively longer after an error and avoid frequent polling.

In two places. The token has only the scopes the report needs and is kept outside the report. In the Power BI model, row-level security ensures that a department head sees only their own branch of the department hierarchy.

We configure workspaces, permissions and refreshes as described on our Power BI consultant page.

Each scheduling system has its own API and terminology. Dyflexis uses a department hierarchy, scopes per token and information streams for demand. The questions are often the same; the model is not.

Read about the L1NDA Power BI dashboard and the Shiftbase Power BI dashboard too.