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 :
Finance | Project Operations, Human Resources, ...
Answered

[BPUpgradeMetadataEDTRelation]:EDT relation found in field ItemId of table EntityStaging. It should be migrated to a regular table relation

(0) ShareShare
ReportReport
Posted on by 1,552

Hi,

Does that mean, i need to do a new relation for each field in staging table? and what is this migration tool? is there sth than can do the relations automatically?

and if my itemId comes from tableX in the entity and in tableX there is a relation on inventTable (inventTable is not used in  my entity). So in my staging table, should i put the relation with the data entity data source tabeX or with inventTable?

I have the same question (0)
  • Verified answer
    Gunjan Bhattachayya Profile Picture
    35,429 on at

    Hi junior AX,

    You need to create a relation with InventTable.

    For an example, for ProjectItemJournalTransStaging, ItemId relation is created with InventTable.

  • Blue Wang Profile Picture
    Microsoft Employee on at

    Hi Junior,

    Yes, you need to define a relation  to InventTable.

    In  relation, you should add field ItemId. And on the relation field, change  Source EDT property to ItemId.

  • Verified answer
    Sergei Minozhenko Profile Picture
    23,097 on at

    Hi JuniorAX,

    Migration tool was designed for AX 2012, to migrate all this kind of EDT relations to relation on table level docs.microsoft.com/.../edt-relation-migration-tool

    As it was mentioned by others you need to perform the next steps:

    1. Set "Ignore EDT relation" property on the field to Yes

    2. Create a relation on the table level.

  • junior AX Profile Picture
    1,552 on at

    Hi All,

    1. Thank you so i have put the property Ignore EDT on the staging field to yes and created the relation

    But how i'm going to know what to fill Cardinality,Related Table Cardinality and relationship type with? how should i fill these values when using a staging table how should i think of the answer??

    2. Also if i have two fields related to CountryRegionId and i got the same BP warning.

    is it ok to create one relation with LogisticsAddressCountryRegion and add two nodes inside it related to the two fields? or should i create two seperate relations? is creating one for both might affecet the resulted value?

    3. Also what should  Cardinality,Related Table Cardinality and relationship type for country region with staging be?

  • Verified answer
    Sergei Minozhenko Profile Picture
    23,097 on at

    Hi JuniorAX,

    1. Usually for ItemId and similar fields parameters are (if the field is not mandatory)

    Cardinality = ZeroMore

    Related table cardinality = ZeroOne

    Relationship type = Association

    2. You need to create one relation per field

    3. Can be the same as for itemId

  • junior AX Profile Picture
    1,552 on at

    Hi Sergie,

    1. May i ask why related would be zeroOne? and what's the difference if it's mandatory?

    2. what would happen if both are in the same relation

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 722

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 605 Super User 2026 Season 1

#3
Subra Profile Picture

Subra 547

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans