Report Data Definition: Issue with multiple aliasing or relationships on the same table with different joins

The report data definition does not allow adding a table twice as a data source.
Also, the report data definition prohibits multiple child relationships with the same data source.
What is the best alternative to overcome this in Cloud Kinetic Epicor?

1 Like

Manage relationships in the RDL Report dataset directly.

1 Like

Hello @fakhruddin,

No, I can’t do that because it clouds Kinetic Epicor so no database access.
And, if I just do a join with a company only, won’t the whole table be brought over and that be bad for performance.

1 Like

I second @fakhruddin on his solution.

As you said, you can’t add the same table twice in the data source and you can’t access the Db directly since you’re on cloud. Your hands are pretty much tied here.

If performance is an issue, you can try to add some criteria or filters in the RDD and see if that makes any difference.

@Dnyanraj_Patil in these situations it is best to see if the table that you need to access twice is hung off of one of the other tables through the Linked Table functionality. If it is, you can get the data one way through the linked table and the data the other way by adding the table and creating the joins.

Thank you for the suggestion but the required table is not available in the “Linked Table” functionality.

1 Like