In the recent history some tables were marked as Obsolete to notifiy the developer that the tableType will be changed to temporary.

Or the Obsolete property is used to increase the field length on field Home Page

#if not CLEAN24

        field(35; "Home Page"; Text[80])

        {

            Caption = 'Home Page';

            ExtendedDatatype = URL;

            ObsoleteReason = 'Field length will be increased to 255.';

            ObsoleteState = Pending;

            ObsoleteTag = '24.0';

        }

#else

#pragma warning disable AS0086

        field(35; "Home Page"; Text[255])

        {

            Caption = 'Home Page';

            ExtendedDatatype = URL;

        }

#pragma warning restore AS0086

#endif

I think it's wrong to use the Obsolete property for this purpose.

Instead of this we should have some additional property to warn for breaking changes.

Additionally we need a way to change or at least increase field lengths for AppSource Apps.

Related Idea on Breaking Changes: https://experience.dynamics.com/ideas/idea/?ideaid=ad09d46e-f779-ec11-b820-0003ff45920b