Hello everyone
Have some peculiar scenario: MyEntity has N:N hierarchical relation (can explain motivation behind it, but take it as must have setup for now).
So there is a Business required Option Set which defining the type of MyEntities record. If it is type 1 (Document), then Grid 1 representing related records of type 2 (Package) is visible; if type 2, then Grid 2 representing records of type 1 is visible.
But there is an issue: once I add the record via Grid 1 - it is visible on Grid 1, but not visible on Grid 2 (on the related record). After a little research I figured out - it behaves that way only with hierarchical N:N relation. Non hierarchical relations work fine, so I assume that system entity (which created to allow N:N) doesn't distinct those 2 Grids. So let's assume that system entity consists of 3 fields only: "GUID; FK1; FK2". Once we create the record from Grid 1, the record created is "GUID1; FK of Document 1; FK of Package 1". Once we create the record from Grid 2, the record created is "GUID2; FK of Package 1; FK Document 2". So the actual table is like:
| GUID | FK1 | FK2 |
| 1 | Document 1 | Package 1 |
| 2 | Package 1 | Document 2 |
So if we editing/viewing the Document 1 record, in the Grid we can only see the records, having Document 1 as FK1 (GUID 1 in this case). Which is correct.
If we editing/viewing the Package 1 record, in the Grid we can only see the records, having Package 1 as FK1 (GUID 2 only). Which is incorrect (in my expectation).
So I have 2 questions actually:
1) Do I understand the way hierarchical N:N works correctly?
2) Is there a way to make record displayed on both Grids without creating "fake symmetrical records" by some custom plugin?