You’re offline. This is a read only version of the page.
2,432
When We have sufficient table relations in ax 2012, then still relation exist on EDT level. Is It just specifically used for populating lookup field from parent table into referenced table or some else use is there?
*This post is locked for comments
Thanks Ivan, for your valuable Information.......
You are safe using the EDTs on dialogs. If an update comes out, where a new pattern is required, I am sure Microsoft would release a tool to bulk-update those, as that would need to also be used internally if such large-scale repeatative refactoring was required.
As for Martin's question: If you look at some of the CTPs for AX7, you'll see that the EDT relation nodes are still there. That's what I meant in my post above.
As for my personal opinion - I don't really see that big of a difference between an EDT relation and an EDT table reference :) What I was saying above is that there most probably (in new AX versions) will still be a way to add fields to a dialog based on EDTs without needing to specify how to lookup and validate values entered.
I agree with your updated info which i was unaware of it.
One things is clear, no table relation using EDT Relations.
What if we use EDT Relations specifically to populate data on unbound controls in Forms or Dialog Form.
Is it better to proceed with EDT relations or handle it with table references as said? which is best?
please let me know which is good way....
I thought that table references would be removed in the next version. MSDN says that "relations that are defined under EDT nodes are still effective, but in a future release they will be obsolete and deleted", people are expected to migrate relations already during upgrade to AX 2012 and Microsoft don't certify any ISV solution with EDT relations.
Lookups etc. are handled by table references (a new concept added in AX 2012).
Do you have a different opinion, or information from inside Microsoft?
These were mostly left for "backward compatibility". All of them were copied over to the Table level based on the fields in the table.
You cannot create EDT relations on new EDT types you add yourself.
But you are right that these relations are still used when, for example, adding a field to a dialog and specifying the EDT.
In future versions I would assume the table relation on the EDT will stay, solely for the above purpose, but that is to be seen.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (