The goal is to create a codeunit to manage POS terminal APIs efficiently within an extension.

1. Access Property: Setting Access = Internal is the best practice for codeunits that provide logic meant to be used only within the current extension. It prevents other extensions from calling these procedures, maintaining encapsulation. Public would expose it globally, which is often unnecessary for internal API management.
2. Procedure Declaration: The OnRun trigger calls readAPI(); without passing any arguments. Therefore, the procedure must be defined as procedure readAPI() to match the signature of the call. The var prefix is used for parameter definitions, not the procedure name itself, and providing an integer parameter would cause a compilation error due to a signature mismatch.

Microsoft Learn: Codeunit Object - Documentation on properties and triggers. Access Property in AL

Microsoft Learn: AL Simple Statements - Explaining procedure calls and parameter matching. Procedures in AL

Microsoft Dynamics 365 Business Central Development: Best Practices for Extension Development - Guidance on encapsulation and access modifiers.

OnInitReport: This trigger runs when the report is first loaded but before the Request Page is shown. It is the ideal place to check user permissions or locations to determine if the user is even authorized to run the report.

OnPreReport: This runs after the Request Page is closed but before data is fetched. It is the standard location for validating user-defined filters or options entered on the request page before the system commits to processing records.

OnPreDataItem: This runs before a specific DataItem is iterated. It is used to apply dynamic filters (like SetRange or SetFilter) based on table data (User Setup) to the specific dataset being processed.

Microsoft Learn (Dynamics 365 Business Central): Report Triggers Overview. "The OnInitReport trigger is used to perform actions before the request page is run."

Microsoft Learn (AL Development): OnPreReport Trigger. "Runs before a report is run... typically used to verify that the user has made selections that are required for the report." Link to Documentation

Microsoft Learn (AL Development): OnPreDataItem Trigger. "Runs before the first record in a data item is retrieved... use this trigger to set filters on the data item." Link to Documentation

Microsoft Dynamics 365 Business Central Documentation: Report Object Triggers. Section: "Execution flow of report triggers."

The code fails because the Open() method is missing. In AL, a query must be explicitly opened to generate a dataset before the Read() method can iterate through records. For optimal performance and correctness, filters (via SetFilter) must be applied before calling Open() so the filter criteria are included in the SQL statement sent to the server. Enclosing line 08 in a BEGIN..END block is unnecessary because it is a single statement. SetFilter is correctly used here to handle the "greater than" (>) operator, which SetRange does not support in the same syntax.

Microsoft Learn. Query.Open() Method. [Official Vendor Documentation]. Specifies that Open must be called before Read.

Microsoft Learn. Query.Read() Method. [Official Vendor Documentation]. Explains that Read returns records from an opened dataset.

Microsoft Learn. Filtering Queries in AL. [Official Vendor Documentation]. Section: "Applying Filters". Confirms filters should be set before the query is opened.

Microsoft Dynamics 365 Business Central Documentation. AL Language Reference: SetFilter vs SetRange. Details the use of filter expressions in SetFilter.

In Business Central report development, the request page automatically generates a tab for every data item. By configuring the DataItemLinkReference property on a child data item to point to its parent, the system treats it as a nested dependency. This suppresses the child data item from appearing as an individual tab on the request page, fulfilling the requirement to hide child items. To optimize user efficiency when filtering, the RequestFilterFields property is used. This property pre-populates the request page with specific fields, allowing users to enter filter criteria immediately without having to manually search for and add fields from the dropdown menu, thereby decreasing the time required for report preparation.

Microsoft Learn (Official Documentation): RequestFilterFields Property. Section: "Applies to Report Data Items." This documentation confirms that this property defines the fields that are displayed by default for filtering.

Microsoft Learn (Official Documentation): DataItemLinkReference Property. Section: "Remarks." It specifies that linking a child data item to a parent via this property affects the hierarchy and request page visibility.

Microsoft Dynamics 365 Business Central AL Developer Guide: Design Report Request Pages. This guide outlines how data item properties influence the layout and behavior of the user interface.

MB-820 Exam Official Curriculum: Module 4: Develop Reports in Business Central. Topic: "Enhancing the Request Page User Experience."

To enable telemetry for a Business Central SaaS tenant, you must first provision an Application Insights resource in the Azure portal. Microsoft best practices recommend using the customer's subscription for data sovereignty. Once created, you copy the Connection String (formerly the Instrumentation Key) and paste it into the specific environment settings within the Business Central Admin Center. This establishes the link. Finally, to verify that signals are being ingested, you navigate to the Logs section of the Application Insights resource and query the traces table, where Business Central telemetry data is stored.

Microsoft Learn: Monitoring and Analyzing Telemetry - Enable Application Insights. [Section: "To enable Application Insights on an environment"]. It specifies using the Admin Center to add the Connection String.

Microsoft Learn: Business Central Telemetry Overview. [Section: "Azure Application Insights"]. Explains that telemetry data is sent to the traces table in Application Insights.

Microsoft Learn: Telemetry FAQ. [Section: "Which Azure subscription should I use?"]. Confirms the recommendation to use the customer's subscription for SaaS environments.

Microsoft Dynamics 365 Business Central Documentation: Environment Management - Telemetry. Detailed steps on configuring the connection string via the Business Central Administration Center.

To optimize performance and meet the requirements for an API page in Business Central:

1. DataAccessIntent: Setting this to ReadOnly allows the platform to use a read-only database replica (if available). This reduces the load on the primary database for GET requests, which is a standard best practice for OData/API performance.
2. Editable: To ensure the API is strictly read-only and prevents any data modification through the endpoint, the Editable property must be set to false. While InsertAllowed = false and ModifyAllowed = false restrict specific operations, Editable = false is the broader property that ensures the entire page context remains non-modifiable.

Microsoft Learn: API Page Type Reference. Section: "Performance and DataAccessIntent". Link to Microsoft Docs

Microsoft Learn: Properties for API Pages. Documentation on Editable and DataAccessIntent properties for Business Central AL.

AL Language Reference: Page Property - DataAccessIntent. Specifying intent for database access.

In the data architecture of Dynamics 365 Supply Chain Management, transactional entities such as non-conformances are defined using a standard pattern. The primary table, which holds the main header information for each unique non-conformance record (e.g., non-conformance ID, date, problem type, status), is referred to as a document table. This table serves as the foundation for the non-conformity entity. While other tables may store related details like corrections or logged history, the document table is the essential component used to introduce and define the core entity.

A: A document history table is designed to store posted, finalized transactions for archival and auditing purposes, not to define active, in-process entities like a new non-conformity.

C: While a non-conformity can have related details, the term "supplemental table for lines" is not the standard architectural component for defining the main entity itself; it would hold subordinate detail records.

1. Microsoft Learn. "Create and process a nonconformance." Dynamics 365 Supply Chain Management Documentation. This document outlines the process of creating a new non-conformance, which involves creating a new record in the main header table (InventQualityOrderTable), demonstrating the role of a central document table in defining the entity.

2. Microsoft Learn. "Tables in finance and operations apps." Finance and Operations apps development Documentation. This article discusses table properties, including the TableGroup property. The primary table for non-conformances (InventQualityOrderTable) belongs to the Transaction group, which is characteristic of document tables that hold the main records for business events.

The app.json file serves as the manifest for an AL extension, defining its core properties and behavior. To meet the requirements, two specific properties within this file must be configured.

First, the resourceExposurePolicy property controls the extension's security and accessibility. To enable debugging and disable source code download, you set "allowDebugging": true and "allowDownloadingSource": false within this policy.

Second, the startupObjectId property in app.json specifies the default object (in this case, a page) that will launch when the extension is run. This sets the desired startup page for testing and general use. Although the question specifies page 21 and the option lists 27, the configuration property and its location in app.json are correct for the stated purpose.

A. While startupObjectId can be set in launch.json, this file is for developer-specific launch configurations and overrides the app.json manifest setting only during a debugging session from VS Code.

B. The resourceExposurePolicy property is not valid for the launch.json file; it belongs exclusively in the app.json manifest. Also, "at low Debugging" is not a valid property name.

D. This option incorrectly sets allowDownloadingSource to true, which contradicts the requirement to disable the capability to download the source code.

1. Microsoft Learn: App.json file. This document details the properties of the extension manifest file.

Section: resourceExposurePolicy Property: "Specifies the exposure policy for the resources of the extension." It lists allowDebugging and allowDownloadingSource as valid keys.

Section: startupObjectId Property: "The ID of the object to run on startup."

2. Microsoft Learn: Launch.json file. This document explains the launch configuration file for debugging.

Section: startupObjectId Property: "Specifies the ID of the object to run for the startup company. This setting will override the startupObjectId property in the app.json file." This confirms that launch.json is an override, while app.json is the primary manifest setting.

On-premises is the only choice for running on company hardware, as "Online" (SaaS) is hosted in Microsoft's Azure environment.

Sandbox environments are a core feature of Business Central Online for testing and development before production deployment.

The standard Shopify connector is natively supported and managed in Business Central Online; while on-premises supports some integrations, the turnkey connector is built for the SaaS ecosystem.

Microsoft Power Automate and Business Events are cloud-native services. While on-premises can connect via data gateways, the seamless, standard "workflow calling a business event" architecture is the defining characteristic of the Online deployment.

Microsoft Learn: Choosing the Right Deployment Option for Dynamics 365 Business Central. Covers the distinction between SaaS (Online) and On-premises regarding hardware ownership.

Microsoft Docs (Development): Production and Sandbox Environments in the Online Version. Specifically details the use of sandboxes for extension development in SaaS.

Microsoft Dynamics 365 Documentation: Shopify Connector for Business Central. Identifies the connector as a standard feature of the online environment.

Microsoft Learn (Power Platform): Using Business Central as a Power Automate Source. Details the requirement for the Business Central Online connector to trigger cloud-based business events and workflows.

Line 10 & 11: In AL, HttpContent.WriteFrom(Text) is the standard method to initialize the content body. HttpContent.GetHeaders(HttpHeaders) is then required to access the content-specific headers (like Content-Type) before they can be modified.

Line 16: This is incorrect because ReadAs is a method of the HttpContent object, not the HttpResponseMessage object directly. To fix this, you must first access the content of the response: ResponseMessage.Content.ReadAs(ResponseText). Line 16 as written will cause a compilation error because ResponseMessage does not have a ReadAs member.

Microsoft Learn (Business Central): HttpContent.WriteFrom(Text) Method. Online Documentation

Microsoft Learn (Business Central): HttpContent.GetHeaders(HttpHeaders) Method. Online Documentation

Microsoft Learn (Business Central): HttpResponseMessage Data Type. (Note: Content property must be accessed to call ReadAs). Online Documentation

Microsoft Learn (Business Central): HttpContent.ReadAs(var Text) Method. Online Documentation