web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / ELandAX blog / Why could relation on a tab...

Why could relation on a table not result in an automatic lookup?

Evaldas Profile Picture Evaldas 1,800
Hello AX World,

Developing with the latest and greatest Dynamics 365 for Finance and Operations is fun, but sometimes we also have to deal with temporary solutions made in previous versions. Recently I have to deal with a one.

I needed a CurrencyCode field on my table. The easiest way is to copy it from another table. It's such a great feature to be able to copy application elements here and there. So, I have copied CustTable field Currency to my new table. I did not bother much to copy the relation to the Currency table as well. A relation is required to get an automatic lookup on the form. 


A good advice of mine, be aware of what you are copying as you may overlook important things. As I did this time. The problem was that I could not get an automatic lookup shown up on my form. 
I have started to examine the relation carefully by going through all the properties and I found the cause of the problem. It turns out that the problem was EDTRelation property, it was set to Yes as so was in CustTableNot sure why it's not the problem in Customers form, the lookup is showing up there. Let me know in the comments bellow if you know the answer.


This property came in AX 2012 when relations were being migrated from the older versions (AX 2009 and earlier) EDTs. Not sure why they are still in this version. Perhaps, due to enabling an upgrade path from AX 2009.

Once the EDTRelation property was set to No the automatic lookup showed up as expected.



Be aware and take care!


This was originally posted here.

Comments

*This post is locked for comments