Millington Offices (10).png

Power BI Report Development 101 - Part 2

Updated: 2 days ago

Last month I wrote the first part of this blog post, which is intended for users that are in the beginning of their Power BI journey.

After a long wait, I finally had some time to finish the second part of the post!

If you don't remember what we discussed in the first post, have a look in the link below:

Power BI Report Development 101 - Part 1 (

Review of the Part 1 finished? Amazing!!

So, let's go back to our diagram:

Colours legend:

Blue Squares - These steps are usually mandatory in most reporting projects

Orange Squares - These are optional steps for advanced visualisation features

Pink Squares - These are optional steps for Q&A Setup

Green Squares - These are optional steps for Row Level Security

Purple Squares - This is a mandatory step for On-Premises data sources

In my diagram, I divided the report development process into four main steps:

1) Analyse data and build your data model

2) Report Design

3) Prepare to share your report

4) Share your report

In the Part 1 of this post, we went through the steps 1) and 2). In this post, we are going to focus on the remaining steps: Prepare to share your report and Share your report

You probably noticed I have a small section on the right called Power BI Integrations.

I decided to add this section because I think it's important to also know what integrations with other tools are there, and how this can be useful in your use case.

I won't be talking about the Power BI Integrations in this post though.

3) Prepare to share your report

🞂 Row Level Security (Optional):

This step comes after you've finished all your work with your report development in Power BI Desktop (data model and report design).

Row-level security (RLS) can be used to restrict data access for given users. Filters restrict data access at the row level, and you can define filters within roles. This means that, if you are using RLS in your report, when a user opens it he/she will be able to see only the data for the role he was assigned to (e.g. you define a RLS role for UK users. You defined a rule that will filter the dataset/report for this group users, meaning they will be able to see only sales data for the UK region).