This setup page will let you define the behavior of how and when tests are created, as well as default settings for templates and test generation rules, and details such as batches to use for automated processes.

For an initial overview of the setup steps refer to How to Setup and Configure Quality Inspector

Defaults Section

Visibility Settings

Visibility	Only available in the full version. Specifies whether or not to show the Quality Inspector in Business Central. Show Quality Inspector: All of the Quality Inspector pages and functions will be available. Hide Quality Inspector: All Quality Inspector pages will not be available except for this setup page. Use “Show Quality Inspector” to use the Quality Inspector. Use “Hide Quality Inspector” when Quality Inspector is only being used as a library or a dependency and no quality inspection feature is being leveraged in the containing application.
Grade Visibility	Only available in the full version. Specifies if the grade is more visible or not. If your test grades are just in-progress, pass, and fail you typically do not need to show grade details. If you have multiple passing and multiple failing states you might want to see the grade details. Only set this to “Show All Details” when there are many multiple pass/fail grades with complex passing or failing characteristics. “Only Show Promoted” is the correct setting for most scenarios, where “Pass” is the default promoted scenario. Do not change this setting to “Show All Details” unless you need multiple passing or failing grades or are using other complex grading features.
Chart Visibility	Specifies whether the chart part should be shown or hidden on pages such as Quality Inspection Fields, Quality Inspection Templates. Set this to “Visible” to show embedded charting pages. Set this to “Hidden” to hide embedded charting pages.

Numbering

Quality Inspection Nos.

Specifies the default number series used for quality inspection documents when there is not a no. series defined on a Quality Inspection Template. When a no. series is defined on a template, then that is used instead.

Most of the time numbering is only setup on this setup page.  It is possible to have custom numbering that is defined on templates to allow different templates to have different no. series.

Behaviors

Create Test Behavior

Specifies the behavior of when to create a new Quality Inspection Test when existing tests occur.

This setting is influenced by the “Find Existing  Behavior” setting when looking at the state of existing tests.

Choices:

“Always Create a New Test” will always create a new test.

“Create a Retest if a matching test is finished” will create a new re-test if there is already an existing matching test, but that matching test is finished.  Otherwise it will not create a new test.

“Always Create a Retest” will always create a new re-test regardless of the state of the existing tests.

“Use Existing Open Test If Available” will behave such that if there is an existing open test that matches the supplied criteria, this will be used instead and a new test will not be made.  If any existing test for the source details match, but it’s not open, then a new test will be made

“Use Any Existing Test If Available” will behave such that if there is any existing test, regardless if it’s finished or open, that match the source details, then this will be used instead of creating a new test.

Find Existing Behavior

Specifies what criteria the system looks for when searching for existing tests.

This is the behavior that defines how the system looks for existing tests.  This influences the existing tests that are found when used with the “Create Test Behavior”.

Choices:

Standard Source Fields = This will look for matches for the Template Code, Source Table, Source Type, Source Sub-Type, Source Document No., Source Document Line No., Source Item No., Source Variant Code, Source Serial No., Source Lot No., Source Task No., Source Package No.

This is the most common setting for most scenarios.

Source Record= This will look specifically for the Source Record Table No. and the Source Record ID.  This ignores the item, document, and any tracking details.  This setting is most often used for custom entities where there is no related item tracking information and nothing matches an item number nor document number.

By Item Tracking = This will only search by the item and item tracking details along with the template code. Source Item No., Source Variant Code, Source Serial No., Source Lot No., Template Code, and Source Package No.

This is most often used when there are many different document types that can produce the same kind of test, for example items that can be either purchased, or moved, or produced.

By Document And Item Only = This ignore item tracking details and only search the document number, document line number, item number, and variant code.  All lot tracking details are ignored.

This is most often used in scenarios of make-to-order where the document number and/or the item number is the key identifying characteristic for the test and there might be multiple lots or serials.

Conditional Lot Find Behavior

Specifies which test(s) are considered when evaluating if a document-specific transaction is blocked.

This is used with grade specific document lot blocking.

If you are not using grade specific document lot blocking then set this to “Any test that matches”.

Choices:

“Any test that matches” = When multiple tests for the same lot exist then any test that matches the criteria for the lot will be used. If there are multiple tests for the same lot then there is no specific behavior other than the first the system finds.

“Only the most recently modified test” = When multiple tests for the same lot exist, then only the most recently modified test will be considered, which might not be the most recently created.

Use this when you want the most recent test that was updated to be the test that influences the behavior of grade specific lot blocking.

“Only the newest test/re-test”= When multiple tests for the same lot exist, then only the most recently created test will be considered, which might not be the most recently modified.

“Any finished test that matches” = When multiple tests for the same lot exist, then the first finished test for that lot that the system finds will be used.

“Only the most recently modified finished test” = When multiple tests for the same lot exist, then the most recently modified test for that lot that the system finds will be used.

“Only the newest finished test/re-test” = When multiple tests for the same lot exist, then only the most recently created test that is finished will be considered, which might not be the most recently modified.

Miscellaneous Settings

CoA Contact No.

Specifies the contact details that will appear on the Certificate of Analysis report when supplied.

This is used with the example/sample reports that show COA details.

Maximum Rows To Fetch on Field Lookups

Specifies the maximum number of rows to fetch on data lookups. Keeping the number as low as possible will increase usability and performance. A larger number will reduce performance and reduce usability.

This setting is used to help keep performance and usability in mind especially for users on phones, tablets, or in other kinds of shop floor scenarios.

When using fields that are lookup codes this will help constrain the choices to a reasonable amount.

As a best practice when designing choices on fields for a template try and keep the choices as limited and small as possible to help make it quick to enter the data. Instead of increasing this value to larger numbers find ways to make the options faster for data entry.

Show Test

Specifies whether to show the Quality Inspection Test page after a test has been made.

For demonstrations and training it can be useful to show automatically created tests immediately to the user, however for production scenarios in most circumstances automatically created tests will end up in a queue or dispatch for quality inspectors. [Only Manually Created Tests] will let you see tests created manually with a button, and will just let automatically created tests be created without showing it.

Consider that in most scenarios the person that triggers the creation of a quality inspection test from an automatic action is likely not the same person collecting values.

“Automatic and Manually Created Tests” = This is the default option, useful for demonstrations, training, or smaller companies where the person that triggers the test is also the same person that fills in the values.

“Only Manually Created Tests” = When tests are created with automation (such as automatically creating tests on purchase receipt, production output, etc…) these tests will not automatically show (even though they will still be created).

Ad-hoc/manually triggered tests (tests created by someone clicking a button) will still continue to show.

This is the most common setting used in production scenarios.  It allows unobtrusive test generation for automatically created tests, and assumes that someone manually creating tests probably wants to see the test.

“Do Not Show Created Tests” = This does not show the test after it’s made, whether it’s made from an automatic trigger or manually generated.

This setting is mostly used in very locked down environments where someone needs to trigger a test to be generated, but is not allowed (or does not need to see) the test itself.

Picture Upload Behavior

Specifies what to do with a picture after it has been taken.

“Do Nothing” = Disables picture upload by doing nothing when a picture is taken.

“Attach Document” = Adds the picture as an attachment.

“Attach and Upload to OneDrive” Adds the picture as an attachment and also uploads it to OneDrive using the OneDrive configuration within Business Central.

“Attach and Upload with DocXtender” Only available on the full version. This leverages DocXtender to attach the file and then upload to SharePoint using DocXtender’s configuration.

Default Caption Expression

Specifies the default data caption expression for a Quality Inspection Test to use. When blank the system will choose for you.

Leave blank to let the system automatically create one.

You can use the square bracket nomenclature [fieldName] to reference fields that are in tests.

Workflow and Approval Request Integration Section

Workflow Integration

Specifies whether to enable events and responses for workflows.

This setting defines whether to enable or disable workflow integration.

If you are using Business Central workflows to automate dispositions, such as automatically moving inventory, or automatically negating inventory, then this should be enabled.

If you are not using automated dispositions, or are using custom code (that itself does not use workflows) for automated dispositions then this can be disabled.

Acceptable Quality Limits

This group is not available on the foundation version.

These are the default AQL settings for the company, you can override them at the template level for specific templates, and also optionally override them on a specific test.

Only adjust these settings if you are using AQL configuration.

Default AQL Grouping Code	Specifies a grouping code allows you to maintain separate AQL configurations. If you only use one, leave this blank.
Default Inspection Level	Specifies the default inspection level that will be applied when a test is created, if you are using AQL. This is optional.
Default AQL	Specifies the default AQL level. Typical values are 0.065, 0.1, 0.15, 0.25, 0.4, 0.65, 1.0, 1.5, 2.5, 4, 6.5.  You can create your own values.

Rounding

This group is not available on the foundation version.

This is used to help configure rounding for sampling.

For example, if a sample summarized value would result in a mathematical value of 0.001111111111 and you want the value instead to be rounding to 0.01 then you can configure that on this setup page.

Round Direction	Specifies which direction to round the values.
Round Precision	Specifies the precision to use. For example use 1.0 to round to a whole number. Use 0.01 to round to two decimal places. For more details refer to https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/system/system-round-method
Summary Decimal to Text Format	Specifies the display format when converting from decimal to text for display purposes. For example “” would cause summary values to be displayed as 1,234.56

Receiving Section

This section defines the default automation that is used on receiving related triggers, which become the default on the related “Quality Inspection Test Generation Rule”.

Automation

Warehouse Receipts

Specifies a default warehouse receipt trigger value for Test Generation Rules to create a test.

Choices:

“When Whse. Receipt is Created”.  This sets the default for receiving rules to be triggered when a Warehouse Receipt is Created.

“When Whse Receipt is Posted”. This sets the default receiving rule to be triggered when a Warehouse Receipt is posted. This is functionally equivalent for purchase related receiving to “When a Purchase Order is Received”.  These settings are separate to allow granular flows with other extensions that integrate with Business Central in other locations.

“Never”. This does not trigger a test for a Warehouse Receipt (unless configured with Purchase, Sales, or Transfer related triggers).

Purchase Orders

Specifies a default purchase trigger value for Test Generation Rules to create a test.

“When Purchase Order is Received”. This is the most common setting even when Warehouse Receipts are used, because often purchase receiving related rules are configured based on details from the purchase line, not the warehouse receipt line.

“When Purchase Order is Released”. This could be used in scenarios where a test needs to be made prior to the product being received. Note that in many cases the lot numbers aren’t always well known in advance.

“Never”.  This does not create a test for purchase receipts (unless using Warehouse Receipts and a Warehouse Receipt trigger is used).

Sales Returns

Specifies a default sales return trigger value for Test Generation Rules to create a test.

“When Sales Return is Received”.  Used when tests should be triggered when a sales return receipt has been posted.

“Never”.  This does not create a test for purchase receipts (unless using Warehouse Receipts and a Warehouse Receipt trigger is used).

Transfer Orders

Specifies a default transfer trigger value for Test Generation Rules to create a test.

“When Transfer is Received”.  Used when tests should be triggered when a transfer receipt has been posted.

“Never”.  This does not create a test for transfer receipts (unless using Warehouse Receipts and a Warehouse Receipt trigger is used).

Production Section

Automation

Production – Create Test

Specifies a default production-related trigger value for Test Generation Rules to try and create a test.

Choices:

“When Output is Posted” = This is the correct choice for most scenarios where tests need to be automatically created during a production process.  This will create a test automatically for the matching test generation rules when output is actually posted and there is something available to test.

“When Order is Released” = This setting is used in some edge cases where a test needs to be made as soon as the production order itself is released to the shop floor from an earlier state such as simulated, planned, or firm planned.

“When a Released Order is Refreshed” = This setting could be used similar to “When Order is Released”, but when orders are not planned ahead of time and instead are just made ‘ad-hoc’.  Caution must be taken with the “Create Test Behavior” setting to avoid creating excessive tests if the order is repeatedly refreshed.

“Never” = The default will be not to automatically create tests. Use this if you are not automatically creating tests with production.

Auto Output Configuration

Specifies granular options for when a test should be created automatically during the production process.

This setting only has an influence when the “When Output is Posted” setting is used for “Production – Create Test”.

If any setting other than “When Output is Posted” is used then this setting has no effect.

Choices:

“Any Output Entry (time or quantity)” = This will trigger the production output trigger when any output is recorded, whether it’s just time or also intermediate or finished goods output.

“Any Quantity Output” = This will trigger the production output trigger when any intermediate or finished goods output is recorded, but not time-only entries.  This setting should be used in conjunction with shop floor systems that allow posting of time separately and outside of finished goods or intermediate work in progress.  This will work with scrap or output quantity posting.

“Only with Quantity” = This will trigger production output for any entry that has output quantity recorded, but not scrap-only entries.   Use this for processes where only finished goods that are not immediately scrapped trigger tests.  If an entry has both quantity and scrap quantity entered then this will be triggered.

“Only with Scrap” = This will trigger production output for any entry that has scrap recorded.  Use this for processes where tests only occur on scrapped goods.

If an entry has both quantity and scrap quantity entered then this will be triggered.

Assembly – Create Test

Specifies a default assembly-related trigger value for Test Generation Rules to try and create a test.

Choices:

“Never” = Never. Use this if you are not triggering tests for assembly output.

“When Output is Posted” = When assembly output is posted.

Inventory and Warehousing Section

Automation

Create Test

Specifies a default warehousing related trigger value for Test Generation Rules to try and create a test.

“Never” = Never creates a test automatically.

“Movement into Bin” = This can be used to trigger tests to be made automatically when product is moved into certain bins.  This can be used for most warehouse transactions but is most commonly used with processes where tests need to be made when put-aways for receipts or production are posted.

This can also be used to trigger automatic test generation when product is moved into a ‘quarantine’ bin.

“Bin Movements and Reclassifications”

This group defines the batch (or batches)  to use when moving inventory to a different bin; this will be used for the manual Move to Bin action as well as PowerAutomate actions. This will also be used for reclassification journals when changing item tracking information.

These are the batches used when dispositions or automated reactions occur, these do not define limits on which triggers cause the transactions.

Batch Name

Specifies the batch to use for bin movements and reclassifications for non-directed pick and put-away locations.

The item reclassification batch name to use when creating item reclassification journal entries as an automated or manual disposition.

Whse. Batch Name

Specifies the batch to use for bin movements and reclassifications for directed pick and put-away locations.

The warehouse reclassification batch name to use when creating warehouse reclassification journal entries as an automated or manual disposition.  Requires the use of warehouse locations.

Whse. Worksheet Name

Specifies the worksheet used for warehouse movements for directed pick and put-away locations.

The warehouse movement worksheet batch name to use when creating a warehouse movement journal entry.  Requires the use of warehouse locations.

Item Tracking Section

Tracking Before Finishing

Specifies whether to require item tracking before finishing a test.

“Allow Missing Item Tracking” = Use this if you do not use lot or serial numbers, or if you use them but have processes that will have tests that will not have known lot or serial numbers. For example if you have tests created in production that prevents the product from being produced then there may not be a lot/serial. Tests with no lot/serial will be permitted.

“Posted Item Tracking Only” = Use this if all lot/serial numbers must be posted in the system before a test can be finished. For example if you are doing tests on finished goods then the lot/serial should exist, or if you are doing tests when lots are moved to a bin then the lot/serial must exist.

“Reservation or Posted” = Use this if lot/serial numbers need to be in the system, but might not yet be posted. An example could be lots that are being received or being produced, have not yet been received or produced yet, but do exist on your item tracking lines.

“Any Non Empty Value” = Use this if you want to track lot/serial numbers that do not enter the system but need tests to document why they did not enter the system. For example if you reject a lot during the receiving process and a failed lot is never put-away. Alternatively if you are producing and know the intended lot/serial but the in-progress item is discarded before it is posted to inventory. Tests with lot/serials that are not in your inventory will be permitted.

Personal Device Interface Section

These are settings that allow adjusting the brick fields, which affect how the test information is shown and displayed on the phone and tablet apps.

To use the phone interface, use the phone app for Business Central and use the Role Center “Quality Inspection – Phone Optimized”. Use this section to configure the available fields when looking at tests on a mobile interface. Additional information about layout can be found here: https://learn.microsoft.com/en-us/dynamics-nav/how-to–display-data-as-bricks

Actions

Test Templates

View a list of Quality Inspection Templates. A Quality Inspection Template is a test plan containing a set of questions and data points that you want to collect.

Test Generation Rules

Specifies a Quality Inspection Test generation rule defines when you want to ask a set of questions defined in a template. You connect it to a source table, and set the criteria to use that template with the table filter. When these filter criteria is met, then it will choose that template. When there are multiple matches, it will use the first template it finds, based on the sort order.

Grades

View the Quality Inspection Grades. Grades are effectively the incomplete/pass/fail state of a test. It is typical to have three grades (incomplete, fail, pass), however you can configure as many grades as you want, and in what circumstances. The grades with a lower number for the priority field are evaluated first. If you are not sure what to configure here then use the three defaults.

Source Configuration List

Use this page to define what tables tests can be created on, and how to connect one table to another for extended source information. Chained connections can be made to allow filtering based on criteria other than the triggering record, such as chaining to a customer record to allow customer specific tests, or to item properties to have more specific item related tests

Quality Inspectors and Quality Inspection Permissions

Fine tune what users are allowed to do in the Quality Inspector module. Note: you still need to grant access to permission sets that provide Business Central access to quality inspections.

Configure Available Tools	This page lets you configure available tools to use when recording Quality Inspection Tests. You can then assign these tools on a specific field on a Quality Inspection Template.
Sample Size Configurations	Configure AQL Sample Size Configurations and their ranges.
AQL Sample Plan Configurations	Configure Sampling Plans. For a given sample code and inspection level configure the sample size, acceptance points, and rejection points.