Background
Contoso, Ltd. is a sales company in the manufacturing industry. It has subsidiaries in multiple countries/ regions, each with its own localization. The subsidiaries must be data-independent from each other. Contoso. Ltd. uses an external business partner to manage the subcontracting of some manufacturing items. Contoso, Ltd. has different sectors with data security between sectors required.
Current environment
Contoso, Ltd. uses Business Central online as the main ERP for financials, sales, purchase, warehouse, and manufacturing processes. It has employees that use the Business Central web application and external applications. The company has a custom external mobile app under development.
The IT department and its partners installed custom extensions to satisfy the company's requirements where the functionality is not available natively.
Contoso, Ltd. interacts with external services provided by customers and partners. Different applications interact with SOAP and OData endpoints exposed from Business Central.
An external business partner of Contoso, Ltd. exposed a REST API for receiving details about new subcontracting orders and for sending the planned release date of each subcontracting order received.
Contoso, Ltd. has not activated the monitoring of the tenant and has no internal telemetry for its apps.
Custom reporting must be created to meet the requirements of the different departments.
Tenant management
Contoso, Ltd. has the following tenant management considerations:
IT department
1. The IT department requires the ability to monitor the tenant to prevent performance problems and detect possible anomalies.
2. The IT department plans to use Azure Application Insights and Log Analytics to inspect the ingested telemetry signals.
3. All tenant upgrades are automatically handled by Microsoft. The IT department does not check for update availability or for tenant-related notifications.
4. The IT department has not configured the receipt of tenant-related notifications from the Business
Central admin center.
External business partner
1. The external business partner must add custom telemetry to an application created for Contoso, Ltd. to monitor a business process.
2. Custom telemetry signals for the application must be visible only on the partner's telemetry.
SOAP
1. Contoso, Ltd. plans to dismiss using the SOAP protocol for integrations.
2. Contoso, Ltd. must be able to detect if external applications are using its Business Central SOAP endpoints.
Issue
The Business Central tenant is upgraded by Microsoft to a new major version during the night.
Users report that one of the Contoso, Ltd. extensions disappeared from the tenant. The IT department confirms that the extension is still published.
Custom mobile application requirements
Contoso, Ltd. plans to create a custom mobile application that has the following requirements:
1. The app must be used by employees to check item details from the ERP in real time and to report issues that occur during the manufacturing process.
2. An AL extension must be created for handling archived issues.
3. Business Central development guidelines must be followed when implementing modules.
4. A module must be implemented for the reporting and tracking of issues information. You plan to call this module Issue Management. The module must expose a method named PostIssue.
5. Code modifications will be required over time.
6. The Issue Management process must be split into two extensions:
ISSUE BASE: main extension
ISSUE EXT: second extension with dependency from ISSUE BASE
7. In the version 1.0.0.0 of the ISSUE BASE extension, you plan to create an Issue table that contains a global Decimal variable named IssueTotal.
8. In the version 1.0.0.0 of the ISSUE BASE extension, you plan to define a table named Issue Category with a Description field defined as follows:
field(2; Description; Text[50])
{
DataClassification = CustomerContent;
}
9. The Issue table defined in ISSUE BASE extension contains a Clone procedure defined as follows:
procedure Clone()
begin
end;
10. In the ISSUE EXT extension, you create a tableextension object of the Issue table.
11. The tableextension object of the Issue table must access the IssueTotal: Decimal variable.
After weeks of usage, you discover that you must remove the Description field and the Clone procedure because they are no longer required.
In a new version of the ISSUE BASE extension, you create a new Issue Type table. You must move data row by row from a previously obsolete Issue Category table to the new Issue Type table. Because a large amount of data must be moved, you must write an Upgrade codeunit by using the DataTransfer object.
The IT department creates a custom API for exposing the custom Issue table. The API provides an action for copying an issue to a new table. The action is defined as follows:
[ServiceEnabled]
procedure Copy(var actionContext: WebServiceActionContext)
begin
end;
Contoso, Ltd. must create an API in Business Central to expose item details to the mobile application.
1. The API must have the lowest possible impact on the production environment when used during working hours.
2. The API must only support Get operations.
Debugging problems
A user of the ISSUE BASE extension in Business Central reports a problem.
To debug the problem, snapshot debugging with the following configuration was activated:
You discover that the debugging is not triggering.
Integration with business partner for subcontracting
Contoso, Ltd. must connect Business Central to the external API provided by the business partner. This will be used for the partner to send the details of new subcontracting orders to fulfill the sales demand, and for receiving the planned release date of each order sent. The integration requirements are as follows:
1. The business partner will provide a REST API secured with basic authentication. Credentials to access the API will be shared with Contoso, Ltd.
2. The API for sending subcontracting orders must be called by sending an authenticated POST request to the given endpoint.
3. The API for retrieving the order no. and planned release date of each subcontracting order responds with the following JSON:
Each order no. must be retrieved.