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?
Electronic reporting - Table relation is not shown in the model mapping designer
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 :)
Was this reply helpful?YesNo
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.