1,846
In AX2012 we use to drag our EDT and drop on the table which then asks to create a foreign key relationship. This would make a field with same name as an EDT (which is dropped) in the child table and set relationship itself.
In Dynamics 365 for Operations, we would have to make a new field in child table for setting up the relationship with Related table field ?
*This post is locked for comments
Can you please describe how exactly did you add DimensionAttributeRecId to your table?
I added that EDT field into my child table but it didn't ask me to create FK relation, nothing pops up on window and When i go to add foreign key relation it gives a BP error that no constraint has been specified.
Please explain how the behavior differs in your case if you follow instructions explained in the verified answer. We can't comment on your problem before you actually describe it.
Hi, this doesn't work the same way we used to do it in AX-2012 R3. Please update what needs to be done to create foreign key relation in dynamics 365 for relations. Thanks!
Not sure exactly what you are mean to ask here but as far as user experience is concerned while development its seems same as in ax 2012.
take an example of any EDT which has got table relationship on it. e.g. take EDT named DimensionAttributeRecId
drag it under fields nodes of your table and it will prompt you for foreign key relationship. if you hit YES, it is going to work and create relationship automatically. This far, the experience is same in D3FO as it was in AX2012
Hi M N,
Yes, in D365 you need to create the field first, then you can add the foreign key relation.
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,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (