Resource Manager's Resource Associations does not show all associations
Last Updated September 12, 2013
When looking at an asset's Resource Manager page, on the left column in Resource Associations, all expected associations do not appear.
There is no issue, the display is working as designed.
The Resource Manager's Resource Associations section may be confusing in how it displays is associations. In general, there are no known issues that would cause it to not show all expected associations. The following describes how this section works.
Any resource association, child or parent (which refers to a resource association and reverse association, respectively), will appear in Resource Associations for an asset. However, the number of what is listed is limited by design. Custom associations/reverse associations are also shown.
Resource Associations displays a max number of five association types. There is no method to extend how many can appear on this list. The user is recommended by the UI to use the Resource Association Grid if they wish to see all remaining associations, which is denoted when the user mouses over the three vertical dots at the bottom of the associations.
The following screenshot shows five associations types, Asset User Owners (Asset Owner), Associated Assets (one-to-many), Test Assoc. (a custom association), Computer Type and Location. All are child associations. Also denoted is the hint box that appears when the mouse is hovered over the three vertical dots, recommending that the user use the Resource Association Grid to see all remaining associations.
Note that the Asset's Status association is not displayed. This is found when the user goes to the Resource Association Grid. When used, this then shows the full number of associations, which in this case, is six.
For a one-to-many association, such as a computer's Associated Assets, Resource Associations displays a max number of three associations per each listed one-to-many association. This may the make the list appear to have more than five types, which is incorrect. For example, if five types are already shown, and one of them is a one-to-many association with three or more associations, the total list of associations shown will be eight: five are the different types, the fifth being the one-to-many, with three associations listed. The user is recommended to click on the More link to see the entire list of associations if there are more than three, for each listed one-to-many association.
There is no discernable way in how Resource Associations chooses which associations to show if there are more than five. Therefore, the user may see one asset showing certain associations, but another showing different, if they both have more than five total.
Some data is considered associations, even if the user believes they are not. For example, a computer's Status is actually an association, not a straight data class, which is why it appears in Resource Associations.
Both child and parent associations are shown. Child to parent are denoted by a blue arrow pointing to the right. Parent to child are denoted by a blue arrow pointing to the left. When editing the asset, parent associations may not be shown, possibly adding to confusion of why this appears on the Resource Associations as a "mystery" association but which is added there by design.
Because this shows two different association relationships, counting how many appear on Resource Associations and comparing it to what is in the asset may result in different numbers. The correct number will be only shown, generally, when the asset is reviewed in the Resource Association Grid.