Aaron Kuhn
1 posts
Registered:
04 Dec 2023
08 Jan
Link to this post
I have a Dynamics entity called ust_tank, with a primary id of ust_tankid. It has a self-referencing many-to-many relationship to itself for customer required functionality. When I embed a sub-grid on my portal form and configure it to use the N:N relationship it fails on load with the error "There was an internal error retrieving the data, please try again later." If I look at the details of the error is see the following: "'ust_USTTank' entity doesn't contain attribute with Name = 'ust_usttankidone' and NameMapping = 'Logical'."
It appears that TPC is attempting to handle this relationship just as it would for any other N:N relationship, however Dynamics does not handle it the same way. Typically if you have 2 entities (Table A and Table B), you would look at the referencing attributes of tableAid, and tableBid which are both stored as the primary fields on the 2 tables. However in the case of the self-referencing N:N, the referencing attributes are not stored on the primary tables, but instead on the N:N table.
Is there any work around or configuration that I can do to get this to work, or is this a bug that needs to be fixed with a future update?