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 / Forums / Finance | Project Operations, Human Resources, ... / Electronic reporting -...
Finance | Project Operations, Human Resources, ...
Answered

Electronic reporting - Table relation is not shown in the model mapping designer

(1) ShareShare
ReportReport
Posted on by Nastaran 290
Hello,
I have an ISV table named CustSalesInvoice that has a relation to CustTrans, but CustTrans does not have any relation to CustSalesInvoice. I want to add a field from the CustSalesInvoice table to my report, but I cannot find this table listed in the #1 Relations, as shown in the screenshot below.
Just to ensure I understand these two types of relations correctly:
#1 <Relations:Record refers to tables that have a relation to CustTrans.
#2 >Relation:Record means tables that CustTrans has a relation to.
CustSalesInvoice has a relation to CustTrans and the relation type is 'composition.' Do you know why I cannot see this relation under #1?
Thank you,
 
 
 
  • Verified answer
    Alireza Eshaghzadeh Profile Picture
    Alireza Eshaghzadeh 15,271 Super User 2026 Season 2 on at
    Hi Nastaran,
    <Relations indicates a "parent-to-child" or "one-to-many" relationship. It means that the data element or entity on the left side of the < symbol is the parent or source, and it can have multiple child or related elements or entities on the right side. In ER, this is often used to represent a situation where one record in a source data entity corresponds to multiple records in a target data entity. For example, in an invoice, one invoice header can have multiple line items.

    >Relations indicates a "child-to-parent" or "many-to-one" relationship. It means that the data element or entity on the left side of the > symbol is the child or related data, and it is associated with a single parent or source element or entity on the right side. In ER, this is often used to represent a situation where multiple records in a source data entity are related to a single record in a target data entity. For example, multiple sales order line items may be associated with a single sales order header.
     
    Regarding you custom table CustSalesInvoice, do you have parent-to-child relation to CustInvoiceJour? If yes, you can retrieve CustTrans. If not you can check if can find child that has relation to CustTrans. I hope it helps :) 

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

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

#1
Martin Dráb Profile Picture

Martin Dráb 544 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 347 Super User 2026 Season 2

#3
CU-1234529-002 Profile Picture

CU-1234529-002 197

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans