Solved: Change lifecycle state for obsolete products I want to use the menu "Change lifecycle state for obsolete products" in the "Product Information management" module, but I want to make this for many items by using the corresponding filter :
Issue in AL Validation for version Business Central v27 mark those procedures as obsolete using the [Obsolete] attribute along with a version tag, and then use conditional compilation with a preprocessor symbol to exclude them in version 27 This lets the procedures remain in the code for backward compatibility but safely omitted during compilation for v27, avoiding validation failures
Referenced field is marked as obsolete - Dynamics 365 Community Hi every one, I created extension for project entity Project entity has a field telephone I am getting Bp warning telephone referenced field PSAPhone is marked obsolete In PSAPhone field properties is obsolete is yes Can any one suggest how to resolve this Bp warning Thanks in advance
Sales Order Header is showing as Obsolete since upgrade to . 37 We recently upgraded to 10 0 37 but have not noticed in Sales Order Open in Excel the Sales orders export (Entity name: SalesOrderHeader) is showing as obsolete in the list of options under 'Open In Excel:
Business Central : Deprecated and Obsolete Fields With the new version of business central wave 2 ,number of fields have been deprecated or obsolete1) Fields moved to an extension by Microsoft2) Field
Solved: open in Excel option not showing data [Obsolete] sales order header and lines i know its obsolete but a few days before he is using this, and data was showing when he uses this option
Appsource validation fails for BC25 because a page extension targets a . . . The correct way is to mark your page extension as obsolete using the property ObsoleteState = Pending; while keeping the extension code intact for now This tells the system and appsource that this extension is planned for removal and will allow validation to pass on BC25