Finance | Project Operations, Human Resources, ...

Deleted EDT used in Data entity in D365 FO

(0) Share

Report

Posted on by Boyapati Praveen Microsoft Employee

Hi Team,

We created one new custom entity for vendor packing slip transactions. In this entity one field has been used an deleted EDT and this may be due to latest version upgrade.

Now we are getting one error "An unknown error occurred in the mapper control. Please contact administrator for more details" while we open the mapping visualization form for the data entity. i am unable to get the references of this label with Label Id "@Mapper:MAPERR999" also.

Can we use deleted EDT's in Data entities ? Is anyone come across this issue ?

We are using D365 FO 10.0.5 version and SysDeletedObjects configuration keys are disabled in the license configuration.

Appreciate your help..!

Thanks,

Praveen

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

You can't use EDTs that don't exist. If MS removes EDTs they mark them as obsolete one year in advance. Using obsolete EDT will produce a compiler warning. So you always have one year to react to those warnings and rework your entity.

Was this reply helpful? Yes No
Boyapati Praveen Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Thanks Nikolaos for your reply.

We are getting this error only in Tiered environements not in the developer environement. Any insights on this ?

Was this reply helpful? Yes No
nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

Are the systems in the same version? Which EDT is it? In which package is it in the dev system?

Was this reply helpful? Yes No
Boyapati Praveen Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Thanks Nikolaos.

Both Systems are in same version and it is 10.0.5.

EDT is DEL_IntrastatItemCodeId and it is in Application Suite package.

The table we have used is VendPackingSlipTrans and field is ItemCodeId.

Thanks in advance..!

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

You should never use objects with DEL_ prefix. Why it still exists in your dev system I don't know, but it's not relevant for solving the issue.

Was this reply helpful? Yes No
Blue Wang Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Praveen,

DEL_ is a special prefix. It is an abbreviation for Deleted and is used for application objects that will be deleted. After an object is prefixed with DEL_, it will be supported for a release and then deleted in the next version of the product.

DEL_ tables and fields are necessary to allow data update. Such objects allow access to old data that must be migrated to a new location.

When an object with a DEL_ prefix is introduced, the update mechanisms handle changes in the standard application, for example by moving fields and X++ code to the table that replaces the one with the DEL_ prefix. But, if you have written X++ code that references an application object that has been given a DEL_ prefix, you have to update these references yourself.

docs.microsoft.com/.../naming-conventions-prefixes

community.dynamics.com/.../what-are-the-fields-beginning-with-del-words-in-some-tables-do-they-serve-some-specific-purpose

Was this reply helpful? Yes No
nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

So, these DEL_objects exist in dev system so that you can do code upgrade from AX2012 to D365. But before deploying your code to test/prod you have to remove all references to such objects.

Was this reply helpful? Yes No