LogsiticsAddressCity doesn't exist

(0) Share

Report

Posted on by Rahul Tanna

We are currently working on code upgrade from AX 2012 to D365 F&O. As we are working on code conflict in F&O env, we came across few roadblocks. We are not able to find the several EDTs in D365 F&O, although they were present in AX 2012.

For example, LogsiticsAddressCity.

In AX 2012, there may be some custom table, which is using this EDT, "LogsiticsAddressCity".
So, while doing code upgrade to D365 F&O, LogsiticsAddressCity is doesn't exist in F&O.
Now, how to deal with this situation? As we have several such EDTs.

All responses (3)

Answers (1)

Verified answer

Martin Dráb 230,836 Most Valuable Professional on at

Like (1)

Report

RE: LogsiticsAddressCity doesn't exist

The question of LogisticsAddressCity EDT was already answered before: see LogisticsAddressCity ExtendedDataType In Ax7. In short, you should use LogisticsAddressCityName instead.

If you have such a problem (and searching the internet doesn't give you an answer), a good idea is looking how the same thing is done in F&O. For example, look at the field that used to use the old EDT and see what EDT is using in F&O.
Rahul Tanna 5 on at

Like (0)

Report

RE: LogsiticsAddressCity doesn't exist

A sincere apology from my side, it was a typo. Also, Thank you for the response.

I meant to say "LogisticsAddressCity" EDT does not exist in D365 F&O. However, it exists in AX 2012.

For example, we have "DMFDefinationGroupName" EDT in AX 2012, but we couldn't find it in D365 F&O.

I am attaching the snapshot for better understanding.

So, returning to my question, In AX 2012, there may be some custom tables that use such EDTs.

So, while doing a code upgrade to D365 F&O, How to handle such situations?
Suggested answer

Martin Dráb 230,836 Most Valuable Professional on at

Like (1)

Report

RE: Upgrade AX 2012 to D365 F&O

LogsiticsAddressCity indeed doesn't exist, but the problem is that you misspelled the name. LogisticsAddressCity does exist.