42

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



Category: Development
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team

Comments

K

We need this new feature, as the current situation leads to unnecessary extra work and causes confusion in development.Additionally, obsolete tags should include information on the release in which the change will take effect. I cannot inform our customers when, for example, the "Package Tracking No." field will be expanded to Text[50]. Even though an obsolete tag states "24.0," we are currently in version 25.5. The preview versions of 26 and 27 still show a field length of 30, which creates significant issues for planning and communication.

Category: Development