3
Hi,
As Partners, we need to receive clear information about functionality marked as obsolete. Currently, there is this page with a list of fields
https://docs.microsoft.com/en-us/dynamics-nav/deprecated-fields
We need not only in which version the field has been marked as obsolete but also what is changing and when will be possible to apply the changes:
Example of today's received messages:
warning AL0432:
- Field 'Use for Invoicing' is marked for removal. Reason: Microsoft Invoicing is not supported on Business Central. Tag: 15.0.
- Table 'Item Template' is marked for removal. Reason: This functionality will be replaced by other templates.. Tag: 16.0.
From the current messages, I cannot do any action yet.
As Partners, we need to receive clear information about functionality marked as obsolete. Currently, there is this page with a list of fields
https://docs.microsoft.com/en-us/dynamics-nav/deprecated-fields
We need not only in which version the field has been marked as obsolete but also what is changing and when will be possible to apply the changes:
Example of today's received messages:
warning AL0432:
- Field 'Use for Invoicing' is marked for removal. Reason: Microsoft Invoicing is not supported on Business Central. Tag: 15.0.
- Table 'Item Template' is marked for removal. Reason: This functionality will be replaced by other templates.. Tag: 16.0.
From the current messages, I cannot do any action yet.
STATUS DETAILS
Under Review
Comments
Hi,
In my opinion you could start tracking features with a unique identifier and then add the identifier in the comment of the changes (obsolete reason) so that a developer can easily search for that reference and track back to the feature.
For example, the code analyzers use unique references, like AL0432 that has a dedicated page https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/diagnostics/diagnostic-al432
Hope this helpes
Category: Documentation
Business Central Team (administrator)
Business Central Team