Book Image

Extending Power BI with Python and R

By : Luca Zavarella
Book Image

Extending Power BI with Python and R

By: Luca Zavarella

Overview of this book

Python and R allow you to extend Power BI capabilities to simplify ingestion and transformation activities, enhance dashboards, and highlight insights. With this book, you'll be able to make your artifacts far more interesting and rich in insights using analytical languages. You'll start by learning how to configure your Power BI environment to use your Python and R scripts. The book then explores data ingestion and data transformation extensions, and advances to focus on data augmentation and data visualization. You'll understand how to import data from external sources and transform them using complex algorithms. The book helps you implement personal data de-identification methods such as pseudonymization, anonymization, and masking in Power BI. You'll be able to call external APIs to enrich your data much more quickly using Python programming and R programming. Later, you'll learn advanced Python and R techniques to perform in-depth analysis and extract valuable information using statistics and machine learning. You'll also understand the main statistical features of datasets by plotting multiple visual graphs in the process of creating a machine learning model. By the end of this book, you’ll be able to enrich your Power BI data models and visualizations using complex algorithms in Python and R.
Table of Contents (22 chapters)
1
Section 1: Best Practices for Using R and Python in Power BI
5
Section 2: Data Ingestion and Transformation with R and Python in Power BI
11
Section 3: Data Enrichment with R and Python in Power BI
17
Section 3: Data Visualization with R in Power BI

Chapter 6: Anonymizing and Pseudonymizing Your Data in Power BI

It happens very often to those who develop a specific software product for a client to want to repackage it and sell it to another client who is interested in similar features. However, if you want to show a few screenshots of the software in a demo to the new client, you should avoid showing any data that might be sensitive. Getting in there and trying to mask the data from a copy of the original software database by hand was definitely one of the tasks the poor hapless developer found themselves having to do in the past, maybe even a few days before the demo.

The scenario described does not require data to be shared with a third-party recipient but aims to successfully demo a product to the customer by displaying simulated data. Therefore, there is no concern about a possible brute force attack by professional analysts with the goal of deriving the original data prior to the de-identification operation.

Things...