https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-dataaccessintent-property

In Business Central, when you need to handle the removal of fields and procedures to ensure that other extensions are not affected by these changes, you typically follow a two-step deprecation process. This allows other developers and users to adapt to the changes before they are fully enforced. Here are the steps to handle the removal:

Mark as Obsolete : In the first version where the decision to remove the field or procedure is made, you set the ObsoleteState to Pending and provide an ObsoleteReason . This doesn ' t remove the feature but indicates to users and developers that it will be removed in the future. This step is crucial for backward compatibility.

Removal : In a subsequent version, after users have had time to adapt to the deprecation warning, you can then remove the field or procedure or set the ObsoleteState to Removed .

Based on these guidelines, here are the three actions you should perform in sequence:

Set the Description field as ObsoleteState = Pending and ObsoleteReason = ' Not in use ' in version 2.0.0.0.

Set the Clone procedure as ObsoleteState = Pending and ObsoleteReason = ' Not in use ' in version 2.0.0.0.

Remove the Description field from the Issue table in version 2.0.0.1.

These steps will ensure that anyone using the Description field or Clone procedure will receive a warning about the pending deprecation before it is actually removed, thereby minimizing the impact on other extensions and providing a clear path for migration.

When handling the removal of fields and procedures in Microsoft Dynamics 365 Business Central, the process should be carried out in a way that allows other extensions or dependent features to adapt to the changes without causing immediate failures.

Set Obsolete State and Reason for Description Field (Version 2.0.0.0): The first step involves marking the Description field as obsolete by setting the ObsoleteState to ' Pending ' . This is a non-breaking change, signaling to other developers and users that the field is planned for removal in a future version. An ObsoleteReason should also be provided to explain why the field is being deprecated.

Set Obsolete State and Reason for Clone Procedure (Version 2.0.0.0): Similarly, the Clone procedure should be marked as obsolete with the ObsoleteState set to ' Pending ' . This indicates that the procedure is no longer in use and will be removed in the future. Providing an ObsoleteReason is best practice as it explains the rationale behind the decision.

Remove the Description Field (Version 2.0.0.1): In the subsequent version, after the developers and users have been given time to adapt to the deprecation notice, the Description field can be safely removed from the Issue table. This is considered a breaking change, hence it is done after the field has been marked as obsolete in a previous version.

The reason for not removing the Description field and Clone procedure immediately in version 2.0.0.0 is to avoid causing runtime errors for any extensions or integrations that may depend on these components. By following this sequence, you provide a clear deprecation path that helps maintain the stability of the overall system while evolving the schema.

Explanation

1. Create a custom Home Page field for the Company information table.

Selection: No

Reasoning: Creating a custom field (e.g., 50000 " My Home Page " ) creates a disconnected data silo. The standard application uses the standard " Home Page " field. If you create a custom one, it will be empty unless you write additional code to sync it, and it won ' t be populated by standard pages. The correct approach is to either use the replacement standard field (if one exists) or suppress the warning until you can refactor.

2. Enclose Line 1 within #pragma warning disable AL0432 .. #pragma warning restore AL0432.

Selection: Yes

Reasoning: This is the standard, correct " Code update " to manage specific deprecation warnings (AL0432). It allows you to continue using the field temporarily (e.g., during a transition period while the field is Obsolete: Pending) without breaking the build, and it limits the suppression strictly to the lines of code that require it, rather than blinding the entire project to deprecations.

3. Disable the AL0432 rule in the ruleset.

Selection: No

Reasoning: While this technically stops the warning from appearing, it is considered bad practice. Disabling the rule in ruleset.json suppresses AL0432 for the entire project , meaning you might miss other critical deprecation warnings that you actually need to address. It is a configuration change, not a focused " code update " to manage a specific warning.

4. Remove or comment the column and then put it back after the field length is increased.

Selection: No

Reasoning: Removing or commenting out the column breaks the report functionality immediately (the data will disappear from the report). Furthermore, relying on " putting it back later " is not a valid strategy for continuous development; you need the code to work now . If the field is marked for removal, it may not exist " later " in its current form, so simply uncommenting it in the future might fail entirely.

Read Scale-Out:

Read scale-out is a feature in Business Central that allows you to improve performance by distributing read-only queries (such as the ones from the ticketAPI) across multiple read replicas in the cloud database. This reduces the load on the primary database and helps improve the response time for read-intensive operations, like analyzing POS data through the ticketAPI.

Data Access Intent - ReadOnly:

When enabling read scale-out, you can configure the DataAccessIntent property of APIs to be ReadOnly. This directs the system to use read replicas to handle read-only queries, which enhances performance by offloading such queries from the primary database.

Why Not Other Options?

Option A (ODataReadonlyGetEnabled) : This parameter is unrelated to read scale-out and primarily affects OData services behavior, not API performance tuning.

Option B (AccessByPermission) : Setting the permission to Read does not directly affect the performance. It only controls access based on user permissions.

Option D (DataAccessIntent ReadOnly) : While setting this property to ReadOnly helps in read-only operations, enabling read scale-out (option C) ensures the underlying infrastructure is optimized to handle such read operations, which is the fundamental action required.

Reference Documentation:

Read Scale-Out in Business Central

Data Access Intent in AL

Table Structure in Business Central: When creating entities such as " non-conformity " entities in Business Central, you use document tables to represent entities that have a header and line structure. In this case, the non-conformity entity has:

A header with common information (Non-conformity Number, Date, Vendor No., etc.).

One or more lines representing the detailed information for each non-conforming item.

Document Table Usage:

Document Table: A document table is the correct table type for scenarios where you have a header (with general information like vendor details) and lines (with detailed, item-specific information).

Document tables are typically used for entities such as Sales Orders, Purchase Orders, or any other transactional data where you have both header and line information.

Supplemental Table (Option C):

Supplemental tables are usually used to add supplementary information to existing data in Business Central. In this case, we need to store detailed line information, which is a core part of the entity rather than supplementary data, so a supplemental table would not be appropriate here.

Document History Table (Option A):

Document history tables are used to track changes and historical data for entities but are not suitable for the main introduction of the entity and its lines. This option is also not appropriate.

Reference Documentation:

Introduction to Business Central Tables

Document Tables in Business Central

var

TempBlob: Codeunit " Temp Blob " ;

IncidentOutStream: OutStream;

IncidentInStream: InStream;

ImageFilter, FileName: Text;

begin

// Initialize the TempBlob and streams

TempBlob.CreateOutStream(IncidentOutStream);

Rec.Image.ExportStream(IncidentOutStream); // ' Rec ' refers to the current Room Incident record

TempBlob.CreateInStream(IncidentInStream);

// Set the filters and filename for the image

ImageFilter := ' Image Files (*.bmp,*.jpg,*.jpeg,*.gif)|*.bmp;*.jpg;*.jpeg;*.gif ' ;

FileName := ' Customer Picture ' ;

// Prompt the user to download the image

if not DownloadFromStream(IncidentInStream, ' ' , ' Download Incident Picture ' , ' ' , ImageFilter, FileName) then

Error( ' Unable to download the image. ' );

end;