v.1.0.3.0
- Limiting the UCL value for a P-chart and Laney-P-chart to 1
v.1.0.0.0
- Initial version
v.1.0.3.0
v.1.0.0.0
The following video demonstrates the main features of the Attribute Control Chart for Power BI and how to apply them.
The Attribute Control Chart in Power BI offers a comprehensive view of process quality by allowing users to monitor defects/defectives and their corresponding metrics.
The schema will help you to select the most appropriate Attribute Control Chart.
This visual supports six types of Attribute Control Charts:
Key features of the Attribute Control Chart are:
Some of the benefits of using Attribute Control Charts are: improve process visibility, early detection of anomalies and enhanced collaboration.
To use the Attribute Control Chart, you need to have a dataset with at least a Lot, Sample and Defect / Defectives. The available fields are:
The Attribute Control Chart comes with many of the standard Power BI formatting options. Titles, axis labels, line and markers appearance, etc. It’s all there.
The General settings contain options that affect the visual container and are consistent across all visual types. Here you can also customize the general Title and Tooltips.
Here you will find the options that affect your analysis the most. You can change the number of points considered for the average and each rule.
Available options:
Rules
By default a p-Chart will show up when adding a category to the Lot, Sample and Defect / Defectives wells, go to Format visual > Calculation > Attribute chart type, click to get a drop down menu and select another chart type.
If the calculation of the LCL results in a negative number, it will be replaced with 0. If you add your own LCL category with negative value, the negative value will show up in the labels and tooltips.
The u-Chart (Unit Chart) and c-Chart (Count Chart) are quality control charts used to monitor count-type data, both are used to track defects.
The u-Chart controls the average number of defects per unit while the c-Chart controls the total number of defects per unit. A c-Chart can only be used if the sample size remains constant. If the sample sizes aren’t constant, use the u-Chart instead.
Use a u-Chart to monitor: defects in manufactured products, customer returns, damaged goods, medication errors, defects in software, failed test cases, inventory discrepancies, defects in building materials.
Use a c-Chart to monitor: number of defective units per batch, number of customer complaints per day, number of damaged items per shipment, number of medication errors per week, number of software defects per release, number of billing errors per billing cycle.
The p-Chart (Proportion Chart) and np-Chart (Nr of Defectives per Unit Chart) are control charts used to monitor proportions both are used to track defectives.
The p-Chart controls the proportion of items and is used for ‘pass/fail’ inspection, while the np-Chart controls the number items.
Use a p-Chart to monitor: proportion of defective items, proportion of customer complaints, proportion of damaged packages, proportion of medication errors, proportion of software modules with defects in a release, proportion of building materials failing quality.
Use a np-Chart to monitor: number of scratches per unit inspected, number of customer complaints per day, number of damaged packages per delivery, number of medication errors per day, number of bugs found per software module.
The Laney u’-Chart and Laney p’-Chart are attribute control charts used to monitor large sample sizes (>5000) and the data shows overdispersion or underdispersion. This can lead to false indications of out-of-control points on a traditional u- or p-Charts.
Use a Laney u’-Chart to monitor: tracking the number of medication errors per patient, the number of falls per patient, or the number of post-surgical complications per procedure; tracking the number of complaints or escalations per customer interaction, the number of errors per customer order, or the number of service failures per service call.
Use a Laney p’-Chart to monitor: the proportion of hospital-acquired infections over time, with each data point representing a weekly or monthly period; the proportion of defective units produced in a manufacturing process over time, with each data point representing a batch.
For any questions or remarks about this Visual, please contact us by email at Nova Silva Support or visit the community forum.
Each of the charts supported by the Attribute Chart has their own specific calculations. This article shows and illustrates the applied formulas.
Users can export data from the Attribute Control Chart into a file for further analysis or sharing purposes. Exporting and downloading data is an easy process and offers flexibility in choosing the format and destination for the exported data. In this brief guide, we’ll walk you through the essential steps.
Here’s what you need to export and download calculated data from the Attribute Control Chart:
– Enable the setting Allow downloads from custom visuals in the Admin Portal
– a Power BI report with your Dataset
– Build and Format the Attribute Control Chart
– Save and Share
This setting is disabled by default and applies to all visuals including those managed by your organizational store, Desktop, and web. When this setting is enabled, users can download data from a custom visual into a file on their storage device.
To manage Power BI visuals you must be a Global administrator or have been assigned the Fabric administrator role. Go to the Admin portal > Tenant settings, scroll down to Power BI visuals and enable Allow downloads from custom visuals. When this setting is enabled, users can download data from the Attribute Control Chart into a file. It can export to files of the following types: .csv, .txt, .json, .tmplt, .xml, .pdf and .xlxs
The UI tenant settings only affect the Power BI service. If you want these settings to take effect in Power BI Desktop, use AD Group Policy.
Key | Value name | Value |
---|---|---|
Software\Policies\Microsoft\Power BI Desktop\ | AllowCVToExportDataToFile | 0 – Disable 1 – Enable (Default) |
When AllowCVToExportDataToFile
is set to 1, the custom visual can export data to a file only if:
Overdispersion and underdispersion are concepts used in statistical analysis to describe the variability of data compared to what would be expected under a particular probability distribution.
Overdispersion occurs when the observed variability in the data is greater than what would be expected based on a theoretical probability distribution. In other words, the data exhibit more variation than predicted by the assumed distribution. This could happen, for example, if there are additional sources of variation or if the data are more spread out than the distribution assumes. In the context of count data, overdispersion might occur when the variance of the data exceeds the mean, which is not consistent with a Poisson or binomial distribution.
Conversely, underdispersion occurs when the observed variability in the data is less than what would be expected based on the assumed distribution. In this case, the data exhibit less variation than predicted by the theoretical distribution. Underdispersion might occur if there are factors that constrain variability or if the data are more clustered or concentrated than expected.
Additionally, in the context of attribute control charts, Laney charts provide a means to account for overdispersion or underdispersion. For instance, a Laney P’ Chart or a Laney U’ Chart can better distinguish between common-cause and special-cause variations compared to traditional attributes charts like a P Chart or a U Chart when overdispersion or underdispersion is present. These Laney charts incorporate adjustments, such as Sigma Z, to accommodate for overdispersion or underdispersion, ensuring more accurate control limits for process monitoring.
Users can export data from the Control Chart XmR for Power BI into a file for further analysis or sharing. In this brief guide, we’ll walk you through the essential steps.
Here’s what you need to export and download calculated data from the Control Chart XmR:
– Enable the setting Allow downloads from custom visuals in the Admin Portal
– a Power BI report with your Dataset
– Build and Format the Control Chart XmR
– Save and Share
To manage Power BI visuals you must be a Global administrator or have been assigned the Fabric administrator role. Go to the Admin portal > Tenant settings, scroll down to Power BI visuals and enable Allow downloads from custom visuals. When this setting is enabled, users can download data from the Control Chart XmR into a file. It can export to files of the following types: .csv, .txt, .json, .tmplt, .xml, .pdf and .xlxs
The UI tenant settings only affect the Power BI service. If you want these settings to take effect in Power BI Desktop, use AD Group Policy.
Key | Value name | Value |
---|---|---|
Software\Policies\Microsoft\Power BI Desktop\ | AllowCVToExportDataToFile | 0 – Disable 1 – Enable (Default) |
When AllowCVToExportDataToFile
is set to 1, the custom visual can export data to a file only if:
Now every user of the PowerGantt Chart can also define and include their own custom scale date. Adding a custom scale date to your PowerGantt Chart allows you to visualize project timelines and tasks more effectively. A custom scale date provides greater flexibility and precision in representing project schedules because there are unlimited number of custom date/time scales, like: fiscal years, special weeknumbers, AM/PM split of the day, etc..
In this article, you will find step-by-step instructions on how to achieve this.
Here’s what you need to define and set up a Custom scale date:
– a Power BI report with your Dataset (including task names, start dates, end dates, etc. )
– a Dataset with a date or time table
– Link tables
– Build and Format the PowerGantt Chart
– Save and Share
A custom date table is essential for implementing a custom date scale. This table will include all the dates you want to display on the Power Gantt Chart. You can generate a date table with DAX or Power Query.
Your date table should have: a date column, unique values, no BLANKs and no missing dates.
To work with DAX, you must have at least one date table in your model. A date table is a table that meets the following requirements:
You have generated a date table with DAX, now you need to build a relationship between your dataset and the date table. Go to section 2. Link Tables
If you add only a calendar table, convert it To Table in the Convert menu on the ribbon. Click OK in the next menu (no selection needed). After converting the list to a table, rename the column to “Date” and right-click and select Change Type > Date.
If your organization has already a global date table in the source data, you can use Power Query to connect to the date table.
You have generated a date table with Power Query, now you need to build a relationship between your dataset and the date table.
Connect the newly created date table with your existing dataset based on the date fields. You need to establish a relationship between the date table and the date fields in your dataset.
Your date table is now linked to your dataset.
Add a PowerGantt Chart to your report and use the Custom scale date.
Take advantage of the additional formatting features available for the Date scale in the formatting pane and customize it according to your preferences.
Go to Format visual pane and expand the Date scale card to:
Additionally, change the Color and Background color of the Date scale under the Column headers card.
Save your Power BI report and publish it to the Power BI service.
For good design practices to create date tables in your data models when using Power BI Desktop, see Create date tables in Power BI Desktop in the Microsoft Learn platform.
There are several reference materials and guides available for DAX and M Query, that can help you to define your custom date.
Data Analysis Expressions (DAX) Reference: https://learn.microsoft.com/en-us/dax/
DAX Guide: https://dax.guide/
CALENDAR DAX Function
Date = CALENDAR (DATE (2024, 1, 1), DATE (2024, 12, 31))
DAX Sample used in screenshots
DateTable =
VAR StartDate = DATE(2024, 1, 1)
VAR EndDate = DATE(YEAR(TODAY()), 12, 31)
RETURN
ADDCOLUMNS (
CALENDAR (StartDate, EndDate),
"Year", YEAR([Date]),
"QtrYr","Q" & FORMAT([Date], "Q YY"),
"Quarternumber", QUARTER([Date]),
"Month", FORMAT([Date], "MMMM"),
"Monthnumber", MONTH([Date]),
"MonthShortName", FORMAT([Date], "MMM"),
"Weekday", FORMAT([Date], "dddd"),
"Weeknumber", WEEKNUM([Date],1),
"WeekdayShortName", FORMAT([Date], "ddd"),
"DayOfWeek", WEEKDAY([Date]),
"WeekdayStartMonday", WEEKDAY([Date],2)
)
Power Query M formula language: https://learn.microsoft.com/en-us/powerquery-m/
Power Query M formula language: https://learn.microsoft.com/en-us/powerquery-m/power-query-m-function-reference
M Query Samples
= List.Dates(#date(2024,1,1),365,#duration(1,0,0,0))
let
Source = List.Dates(#date(2024,1,1),365,#duration(1,0,0,0)),
#"Converted to Table" = Table.FromList(Source, Splitter.SplitByNothing(), null, null, ExtraValues.Error),
#"Renamed Columns" = Table.RenameColumns(#"Converted to Table",{{"Column1", "Date"}}),
#"Changed Type" = Table.TransformColumnTypes(#"Renamed Columns",{{"Date", type date}}),
#"Inserted Year" = Table.AddColumn(#"Changed Type", "Year", each Date.Year([Date]), Int64.Type),
#"Inserted Month" = Table.AddColumn(#"Inserted Year", "Month", each Date.Month([Date]), Int64.Type),
#"Inserted Quarter" = Table.AddColumn(#"Inserted Month", "Quarter", each Date.QuarterOfYear([Date]), Int64.Type),
#"Inserted Week of Year" = Table.AddColumn(#"Inserted Quarter", "Week of Year", each Date.WeekOfYear([Date]), Int64.Type),
#"Inserted Day Name" = Table.AddColumn(#"Inserted Week of Year", "Day Name", each Date.DayOfWeekName([Date]), type text)
in
#"Inserted Day Name"
In this article we will explore how using Power BI Certified visuals help organizations to protect data integrity and ensure the security and privacy of sensitive information.
Certified Power BI visuals are visuals in AppSource that meet certain specified code requirements that the Microsoft Power BI team has tested and approved. The tests are designed to check that the visual doesn’t access external services or resources, and that it follows secure coding patterns and guidelines. All certified visuals must pass all the certification requirements.
All our Power BI visuals (including the Shielded HTML Viewer) are certified by Microsoft. At Nova Silva we develop visuals based on the Microsoft Certification requirements, so our visuals are tested to verify that they don’t access external services or resources, and that they follow secure coding patterns and guidelines. An important requirement to pass the Microsoft certification tests is that the visuals cannot connect with any external server or service. In other words: our visuals do not share any of your data with anyone, not even with us. This is the main reason why we certify all our visuals: we want to make sure you are the only party that can access your data.
When you use our visuals, you do not make use of any Nova Silva infrastructure or platform. Our visuals do not share data with any external service or resource, we have no access to any of your data, nor do we play a role in any production services. We publish our visuals (and any updates) to Microsoft. Microsoft will check our code to determine if it complies with their quality and security standards. After passing these certification tests, Microsoft will publish the visual to the Microsoft AppSource. This is where you will download and use it from. The next image gives an overview of how we work with Microsoft on our Power BI visuals.
The code of our visuals (at run time) are on a Microsoft managed environment. The only way we can change this code is through the Microsoft Certification process. Our visuals interact with Power BI through a Visuals API. This API provides the visual with the right data and context. The visual only renders the result on the screen within Power BI.
This is the process to certify our visuals:
Each time we develop or update a visual we perform our own internal testing to make sure we comply with all Microsoft certification requirements. Then we publish the source code to Microsoft, and they perform their Certification Test. After passing all tests Microsoft will publish the visual to the Microsoft AppSource. This is the environment where our customers can access the visual and use it within their Power BI Environment.
Each time we publish a (new) version of our visual it first needs to pass the Microsoft Certification tests. This includes a thorough review of our source code by Microsoft engineers. A certified visual cannot lose its certification with a new update. Instead, the update is rejected. If the update is rejected because of a violation, an email is sent to Nova Silva explaining what needs to be fixed.
These are some of the requirements to get a Power BI visual certified.
List of requirements:
Before submitting a Power BI visual for certification:
To learn more about the certification process, go to Microsoft.
The certification process tests include, but aren’t limited to:
innerHTML
, or D3.html(user data or user input)
.eval()
, unsafe use of settimeout()
, requestAnimationFrame()
, setinterval(user input function)
, and user input or user data.Certified visuals will be clearly identified by:
Non-certified visuals: some Power BI visuals aren’t certified because they don’t comply with one or more of the certification requirements. For example, a map Power BI visual connecting to an external service, or a Power BI visual using commercial libraries can’t be certified.
When that is the case the visual has no badge and will show this information:
Microsoft certified our first Power BI visual, the Shielded HTML Viewer, back in 2020! It was a long process and took several code reviews by Microsoft before we got our first visual certified.
Sometimes, users report the Shielded HTML Viewer does not work with LinkedIn or YouTube, our visuals do not render anything from any external server or service as this is one of the main requirements to be certified. This can only be achieved with a non-certified visual.
Currently all Nova Silva visuals are Power BI Certified, this guarantees our visuals are safe and secure and ensures they meet the highest data security standards.
We are committed to maintain those standards, all our visuals are either certified or in the process of getting certified.
Power BI certified visuals offer more features than non-certified visuals, like:
– Export to PowerPoint
– Export to PDF
– or display the visual in received emails when a user subscribes to report pages.
The PER USER license is sold directly through the Microsoft AppSource. These licenses can be purchased monthly/yearly. It supports the payment options you have with Microsoft for any Azure related purchases. For most organizations this is limited to credit card payments.
Every user, that is both Creator and Viewer need a valid license to use the visual. For example, if you have 2 users creating reports with the visual and 10 users who only consume the reports, you need: 2+10=12 user licenses. After you purchase these licenses from the Microsoft AppSource you need to assign the licenses to each user or user group. This is done at the Microsoft Admin Center.
Before purchasing a PER USER license through the Microsoft AppSource please read the Considerations below!
The PER USER licenses can only be purchased directly by the organization that will use the visual and not via distributor/reseller.
There are currently no options to re-assign these licenses between organizations.
The best is that the tenant admin does the purchase (through the Microsoft AppSource).
If the tenant admin owns the licenses (Org licenses), then any of the license admins (Global Admin, License Admin or User Admin) can manage and assign the licenses.
Currently, the following Power BI environments don’t support PER USER license management or license enforcement:
• Embedded – Publish To Web (public URL) , PaaS embed
• National clouds (Depends on general support for transactability in national clouds)
• RS Server (No planned support)
• Exporting (PDF\PPT) using REST API
For unsupported environments you need a PREMIUM license.
The Nova Silva visuals you can download from the AppSource are Certified Power BI visuals that meet certain specified code requirements that the Microsoft Power BI team has tested and approved. The tests are designed to check that the visual doesn’t access external services or resources. Our visuals are updated automatically when a new version is available.
To purchase a Nova Silva visual through the Microsoft AppSource, click Buy now and complete the Checkout path. See below:
You can add a purchase number to the billing profile of your order. At the final stage of your checkout, select Add new under the billing profile and add the Purchase order number in the field.
After you complete your purchase, you can find your receipt in the Microsoft 365 admin center by clicking Download invoice under Bills & payments > Invoices.
Billing and Global admins can also pay by invoice if that’s set up for your company. Read more about setting payment methods. Follow these steps to see your billing profile.
After the purchase through Microsoft AppSource is complete and successful, the  buyer (owner) will need to assign the licenses to the users.
If the tenant admin owns the licenses (Org licenses), then any of the license admins (Global Admin, License Admin or User Admin) can manage the licenses.
However, if the subscription owner is non-admin, he will have access to the portal and only he can manage the subscription and licenses. The tenant admin can see all subscriptions purchased under the tenant account, including the subscriptions purchased by non-admins. You can assign licenses to users in the same tenant that you purchased subscription under regardless of the location.
Buyers get a license assigned to them automatically. It can take up to five minutes from the time of purchase for the license to take effect. If you want to add more users or update your subscription, go to the admin center. You can assign the license to the users directly by providing name or email, or through Microsoft Groups either Mail-enabled or Security Group.
If the owner of the subscription leaves the company, tenant admin purchases (typically known as organizational purchases) continue to work as-is. If the owner was an admin, any license admin (Global Admin, License Admin, User Admin) can continue to manage the licenses. The subscriptions can be managed by any Billing Admin or Global Admin with access to the billing account used for purchase.
If the owner wasn’t an admin, the license will continue to work as long as the subscription is active. However, the subscription can’t be managed by anyone else.
After you assign a license in the Microsoft 365 Admin Center, the license should be available within a few minutes.
If you were just assigned a license, refresh the report to activate it by doing one of the following:
If, after you refresh, the license is still not available, wait a while and try again. It could take up to five minutes.
Access the information about the licenses you purchased and manage it in Your Products under the Billing node in the Microsoft 365 admin center.
Check the visual to activate the options or click the icons (Buy licenses or More actions). Here you can Buy licenses, Remove licenses, View billing profile, Edit recurring billing (to turn on/ off recurring bill) and Cancel subscription.
As a billing or global admin, you can see all subscriptions in the Microsoft 365 admin center, and you can cancel them.
In the admin center, go to Billing > Your products
Find and check the visual you want to manage
Click Cancel subscription
You’re eligible for a full refund if you cancel your subscription within seven days of purchase. Refunds aren’t available for subscriptions canceled after that time period. PER USER license purchases and refunds are handled by Microsoft and not by Nova Silva.
For help managing licenses, contact support or click the Help & Support option on the bottom right section of your screen. If you raise a support ticket provide the Subscription ID.
Currently, the following Power BI environments don’t support PER USER license management or license enforcement:
For unsupported environments you need a PREMIUM license, this can be purchased from our webshop.