Obsolete Codeunits

(1) Share

Report

Posted on by Hein Kruger

501

Hi I have an entire codeunit that I need to obsolete for a SAAS app. (ID changed for simplicity)
Could anyone confirm if the Obsolete format is correct. We need to put the Obsolete state inside the codeunit and not above it?
After the first release we use the CLEAN25 in the app Json and release again. Only after this will the ID be removed?

codeunit 50000 "Eventsubscribers"
{
#if not CLEAN25
ObsoleteReason = 'Duplicate ID in another app';
ObsoleteState = Pending;
ObsoleteTag = 'TEST-381';
#else
ObsoleteState = Removed;
ObsoleteTag = 'TEST-381';
#endif

[EventSubscriber(ObjectType::Table, Database::"Sales Header", 'OnAfterCheckSellToCust', '', false, false)]
local procedure OnAfterCheckSellToCust(var SalesHeader: Record "Sales Header"; xSalesHeader: Record "Sales Header"; Customer: Record Customer; CurrentFieldNo: Integer)
begin
SalesHeader.Validate("Customer Type", Customer."Customer Type");
end;
}

Thanks in advance.

Categories:

Business Central

All responses (2)

Answers (0)

Suggested answer

YUN ZHU 73,813 Super User 2024 Season 2 on at

Like (0)

Report

Obsolete Codeunits

There are many standard functions that you can refer to.

In addition, this is a customized function. If there is no extension that depends on it, I think there is no problem in deleting it directly.

Thanks.

ZHU
Suggested answer

Mohamed Amine Mahmoudi 9,610 Super User 2024 Season 2 on at

Like (0)

Report

Obsolete Codeunits

Hi,

Please refer to this :

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/attributes/devenv-obsolete-attribute

Best regards,

Mohamed Amine MAHMOUDI