On demand · Product video
Collect multiple samples with the sampling worksheet in Quality Inspector
For quality teams that measure several samples per field and want sample sizes and rejection points to come from their sampling plans.

Summary
Quality Inspector can collect several samples for one field on a quality inspection test. The video sets a sample summary, such as average, on template fields so they collect multiple samples, then shows the sample size, acceptance point, and rejection point that come from the inspection level, lot quantity, and Acceptable Quality Limit (AQL) tables in Quality Inspector setup. It enters samples one field at a time in the sample editor, then enters several fields at once in the sampling worksheet. Finally, it adds a reject grade to the sampling plan configuration so the test fails as soon as enough samples are rejected, without collecting the rest.
Key topics
- Set a sample summary so a field collects multiple samples
- Get sample sizes from inspection level and AQL tables
- Enter samples in the sample editor or the sampling worksheet
- Fail a test automatically at the rejection point
Read the transcript
We’re going to review how to create a quality inspection template that has a field that collects multiple samples, and how to use that with the new sampling worksheet feature. To get started, we’re going to create a new template, and in this template we’re going to add some fields. This step is the same as if you were adding existing fields from your other systems. For example, let’s look for a temperature. Here’s a temperature, and let’s also look for a weight and a width. And let’s see if we have a pressure and a pH. Perfect.
Now, in these existing fields, we’re going to configure just some of them to collect multiple samples. We’re going to have temperature, pressure, and pH each collect multiple samples. We’re going to keep weight and width as single value samples, and we’re going to show how you can still collect all these values in a mixed fashion. To tell temperature to collect multiple samples for this template, all you need to do is specify the sample summary. If it’s blank, it’s not going to collect multiple samples. If it’s anything other than blank, it’s going to collect multiple samples.
For simplicity, we’re just going to choose last for temperature. Actually, let’s choose average instead. For pressure, we’ll choose average as well, and the same for pH. Okay, so now we’re going to connect this to something simple. In our case, we’ll just choose the item ledger entry, with no conditions, and we’ll create a test. We choose our item ledger entry, and we’ll choose something that has multiple quantities, such as this item here.
All right, so when you’re collecting multiple samples, you’re going to notice a new area on the quality inspection test. It shows you the inspection level and the quantity that comes in from the document, which you can configure in your source document configuration. It also shows you the sampling plan code and sample size, as well as the AQL. You can configure the inspection level and the AQL on the template or in the Quality Inspector setup. You also don’t have to configure these at all. You would configure them if you want the sample size to come in automatically, based on the tables defined in the Quality Inspector setup.
It’s basically that simple. We have the inspection level, the quantity, and the sampling plan code, and that tells us the sample size, based on our inspection level and AQL configuration, is 50. To look at some of the values, we just click the editor, and now we’re in a single field editor for that one field. We’re collecting samples right now just for temperature. You can see details on the right-hand side for the sample statistics, which give you an idea of everything you have.
The sample area tells you how many samples you have remaining to test, as well as the acceptance point and rejection point. Here we know to stop testing as soon as we’ve hit six failures. All right, so let’s put in some values. We’re going to put in five. Yes, we do want to assign this to ourselves. Ten, 15, one, and let’s see, five, six, seven, eight, nine. Now we can see that we’ve got several samples, we can see the rejection point hasn’t been reached, and we can see the average value. So we should expect to see that average value of seven when we close this.
Editing a single field at a time is a good way of entering values if you’re using a specific tool that collects multiple measurements. If you’re collecting multiple samples for multiple fields at the same time, for example temperature, pressure, and pH, which would typically be measured together, you would use the sampling worksheet. You can open it by clicking the Sampling Worksheet action on the quality inspection test. This action becomes enabled as soon as the test detects that multiple samples need to exist.
The sampling worksheet is very similar, except you don’t see the individual statistics. It does, however, let you enter multiple values at the same time, with simple color coding showing whether those values passed or failed. Now, we’re going to notice that only the fields that are configured for multiple samples are shown in the sampling worksheet. You can also drill down into the statistics for any given field just by clicking the three dots on any of the rows.
By clicking the three dots, we drill down into the temperature for this quality inspection test. Then we can see the individual values and get a better understanding of the statistics, the acceptance and rejection points, and other details that might be important for that field.
All right, so when you collect multiple samples, if you’re not using an AQL configuration code, the grade on the line will automatically use whatever summary statistic you’ve chosen. For example, if you’re using average, it will apply the grade to that average value. If you’d like to use AQL failures instead, to take advantage of something like the rejection limit, all you need to do is specify the failure grade on the AQL tables. Let’s do that now so we can compare and contrast. We see here that we’re on general level two, sampling plan code H, and AQL 4.
So we’re going to navigate to Quality Inspector setup, and there we see two different tables. The first is the sample size configuration. This tells the system what sampling plan code to use for a given minimum and maximum lot size. In our example, we had a quantity in the three hundreds. That was used as the lot size, and the system looked it up here and found sampling plan code H.
Then there’s a secondary table, the sampling plan configuration. This is where we define the AQL for any given code, with the acceptance and rejection points. If we look at sampling plan code H for general inspection level two, we can see the sample size is 50. That’s where that 50 came from. We’ve configured the AQL in this scenario to 4, so the acceptance point is five and the rejection point is six.
Now, there’s another field here called Reject Grade. If you leave this blank, the system uses the summary field on the test line to determine whether that test line passes or fails. However, you can specify a failure grade here. In this case, I’m going to choose one called AQL Fail. You don’t need a special grade for this; it can just be your typical fail or error grade. I’m choosing a special one so we can see how it uses that failure grade.
So now, when you have that reject grade specified, the system uses it as soon as you have enough failed samples to meet the rejection criteria. And beyond that, it doesn’t use it just for the line; it also uses it for the test. The idea is that as soon as you hit the rejection point, you don’t need to collect additional samples, so we inform you right away that there’s nothing else to do. If we see this in action, we can see that it already knows this has an AQL failure.
So let’s tweak these values a little. Let’s change some of these to a pass, put this as minus 20, and also have one that’s 100. In this case, the average is 12.1, and our pass description is minus 25. Overall, our rejection point hasn’t been reached, because we only have four rejected samples, which does not hit the rejection point of six. Because we have that 12.1, if we didn’t have the reject grade, the line would show a failure from the average, which it does. However, as soon as you put in enough rejected samples, it’s going to choose that AQL failure, regardless of the summary statistic you’re using.
To demonstrate, we need two additional rejected samples, so we’ll put in six and seven. We see that these individually failed based on those grades, and we now see the AQL Fail grade come in. It comes in because we’ve defined on the sampling plan configuration table that, for that inspection level and AQL number for our sample size, the line should fail with that specific grade when the rejection point is reached. We can still see the individual samples with their passing and failing grades, and then the AQL failure that affects the line itself.
If we go back to the test, we can now see two things. The line failed with an AQL failure, and beyond that, the test itself failed immediately. The value here is that once you hit the rejection point, you no longer need to collect samples. If you’re not using a reject grade on the sampling plan configuration, the grade on the line acts as it did before, so you would still need to finish collecting the samples. Here, the system knows there’s no point in even collecting the weight or the width, because this inspection test has already failed.
All right, editing other values is the same as before, so you can still edit values that aren’t multi-sample. For example, weight and width are not multi-sample, so they act as they did before. Only fields that are configured for multiple samples give you the drill-down to the sample editor for that field, or appear in the sampling worksheet, where you can enter all of those fields at once. So that is a review of the sampling worksheet and the ability to collect multiple samples in Quality Inspector.
Questions about this webcast?
Send your question and the Insight Works team will reply by email. Ready to plan a project? Contact your Microsoft Partner.
Ask a question
More recordings
Webinar recording · 38 minBusiness Central quality is a starting point: Here’s how partners take it furtherQuality InspectorRecorded May 2026
Webinar recording · 60 minTransform your quality assurance process with Dynamics 365 Business CentralQuality InspectorRecorded February 2026
Product video · 6 minCollect quality test values in Microsoft Teams with adaptive cards in Quality InspectorQuality InspectorRecorded December 2025