I think it is important to highlight the difference between working in SQL and AwareIM, because maybe it causes some confusion when trying to figure out how shortcuts behave. In SQL you have to keep track on the relations yourself by using unique identifier columns so you can do JOINs etc to connect the correct rows to eachother.
AwareIM on the other hand keeps track on this automatically after you have created a relation between two BOs. AwareIM adds all the relationship logic in the SQL, and is not dependent on self-made ID attributes visible in the Config Tool. After that, you can use a grid, combo-box, etc to establish the relationship during the creation/editing of an object. Then you can add shortcuts to display the attributes of the other BO row.
The only reason I can think of why you would want the IndID attribute is if you are importing data from another source, and want to establish AwareIM relationships based on these values. However, if the users are adding the data themselves, you will not need this attribute. I think IndID is something you might have created because you are thinking in the terms of a SQL database guru rather than an AwareIM Config Tool user 🙂
lueu wrote
Follow up question:
Does shortcuts only work for objects created/edited after relationship and shortcuts are made? Not for existing objects in the table(BO)?
Since I can create a new object using a reference attribute to select/set a value, and this will show, but the already existing objects shows nothing in the shortcut column?
Because if this is the case, it's working now, just not the way I wanted it to 🙂
Not sure if I understand, but as long as you can edit an object and add a reference to a row in BO2 (or use a rule), the shortcut should work fine.
