|
- Solved: How to enable an obsolete entity - Dynamics 365 Community
But first version of Customer entity is marked as Obsolete and hence cannot be selected It doesn't seem create extension of that entity can let you override "IsObsolete" property I am wondering is there any way to re-enable entities that is current marked as "Obsolete"?
- 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 :
- 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:
- D365FO - Get list of obsolete data entities - Dynamics 365 Community
Find which data entity is obsolete after every new update Here are the steps For example; Customers V2 data entity is obsolete with version 8 0For d
- 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
- How to use the Doc. Attachment List Factbox on a custom page
Thank you, but that is the obsolete page This is the new one: Page "Doc Attachment List Factbox" | Microsoft Learn I assume the code I require uses the OnBeforeDocumentAttachmentDetailsRunModal Event, but I am struggling to get it to work, so if anyone has achieved this, it would be much appreciated
- Dynamics 365 Business Central: again about obsoleting fields
Obsolete fields are actually never physically removed also during a next major release upgrade The right way of work when you need to declare fields as obsolete is to always maintain those field definition on your AL code, like in the following code: In this way, you don’t have breaking schema changes and your extension will be correctly
- Issue with removing a field marked for removal in Business Central . . .
Hello, I'm encountering an issue need some advice Here's the situation: In an older version of our extension published on AppSource, we added a new field to a table In the subsequent version, we marked this field as ObsoleteState = Pending since it was no longer needed, and that version was published to AppSource In the following version, we changed the field's ObsoleteState from Pending to
|
|
|