安裝中文字典英文字典辭典工具!
安裝中文字典英文字典辭典工具!
|
- Dynamics Community Forum Thread Details - Dynamics 365 Community
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:
- Dynamics Community Forum Thread Details - Dynamics 365 Community
You can add obsolete entities to the data project: 1 You can just type the name of the entity (Customers) in lookup under "Add entity" button (don't select it manually from lookup) 2 You can add it through "Add multiple" (here it's visible for lookup)
- cmty_blog_detail - Dynamics 365 Community
After making above table obsolete created new table with the new primary key Next point is how to transfer data in the new table To transfer data from obsolete table to new table used Installed code unit Additionally you can use temporary table to update data from old table to new table
- Dynamics Community Forum Thread Details - Dynamics 365 Community
Hi Fahad, Positions entity is marked as obsolete and that why you don't see it in the add entity dialog You can paste the entity name in the add entity dialog, press "Add" and the entity still be added to the data project or use Positions V2 entity (recommended approach)
- Dynamics Community Forum Thread Details - Dynamics 365 Community
<Message>Referenced object 'WMSPickingQtyTime' is marked as obsolete < Message> <Justification>Extension of EcoResReleasedProductV2Entity, not able to remove reference to WHSProductFilterGroupEntity from underlying entity < Justification> < Diagnostic> < Items> < IgnoreDiagnostics>
- Dynamics Community Forum Thread Details - Dynamics 365 Community
Might also be a missing call to Set Data It happens when one copies a textbox with a call to SetData Original textbox expression:
- Dynamics Community Forum Thread Details - Dynamics 365 Community
The solution is to stop using obsolete elements Unfortunately I don't know how this field used to be used in older versions before it got obsolete, therefore I can't tell you what has replaced it I guess they changed the solution to use the global address book instead of a field on ProjTable
- cmty_blog_detail - Dynamics 365 Community
Microsoft actually has not enforced a policy for physically removing obsolete fields from the database, this is at the moment only like a “mark” that prevent you (and your partners) to use the field (or the object) Obsolete fields are actually never physically removed also during a next major release upgrade
|
|
|