In TRIRIGA 220.127.116.11, I noticed that the reverse association “Geography > Geography Contains > triProperty” hasn’t been created automatically after updating the triGeographyLookupTX field of triProperty. As delivered, the following forward/reverse associations are between the Geography and triProperty BOs:
- In Geography: “Geography > Geography Contains > triProperty”, Reverse association: Belongs To Geography
- In triProperty: “triProperty > Belongs To Geography > Geography”, Reverse association: Geography Contains
The triBuilding has the same configuration of associations, but the reverse association was created correctly (by a workflow?). My question is: If we want the reverse association to be created automatically when the forward association is created, we have to create forward/reverse associations based on the real BO (triCity, triCountry, triState, etc.), right?