Why isn’t the reverse association created from Geography?


In TRIRIGA 3.4.2.3, 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?

Continue reading →

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s