JSM Assets: linking an object multiple times

[Derrick Sutanto]

I have an object type in the assets manager with an attribute that refers to another object type. I would like the other object to appear in this attribute multiple times. In other words, I would like a one-to-one relationship to repeat within the attribute. Changing the cardinality allows me only to link more than one different object within the attribute.

[Dirk Ronsmans]

Hey @Derrick Sutanto ,

In a single attribute you can only have a single link to another attribute. Having multiple links to the from the same attribute to a single attribute is not possible.

Can you maybe elaborate on the use case why you want to do that?

[Derrick Sutanto]

We are using the asset manager to keep track of all our company's PCs and their components. Some components are too numerous/insignificant on their own to be recorded as individual objects, so we simply list the component type and model. As some PCs can take more than one of the same type of component, I would like to link that model more than once as an attribute of the PC in question.

For example, a server can have four graphics cards of an identical type. The specific server is one object, and the four graphics cards are abstracted to one model of card:

GRAPHICS CARDS

Attributes:

Id  | Name   | Type     | Type value
----+--------+----------+-------------
10  | Model  | Default  | Text
----+--------+----------+-------------
11  | OEM    | Default  | Select


Objects:

Key   | Model         | OEM
------+---------------+---------
PC-1  | Quadro A4000  | NVIDIA

___________________________________________________________________

SERVERS

Attributes:

Id  | Name      | Type                    | Type value
----+-----------+-------------------------+-------------
12  | Hostname  | Default                 | Text
----+-----------+-------------------------+-------------
13  | GPUs      | Object: GRAPHICS CARDS  | Reference


Objects:

Key   | Hostname   | GPUs
------+------------+---------------
PC-2  | Server-01  | Quadro A4000
      |            | Quadro A4000
      |            | Quadro A4000
      |            | Quadro A4000

[Darius]

Very interested in finding a viable approach this problem as well

[Peter Strömberg]

Likewise here. 

We'd like to demonstrate in "functions", the number of times a given product is needed. Thus we would like to have the possibility to link the same object several times. 

[Rachel Bond]

@Dirk Ronsmans - reposting bc I meant to add this as a reply and not an answer.

Voting as this would be useful my use-case as well. Basically, we have one system which could have up to 4 components in it, since these components all have very different capabilities they are all tracked as separate object types. Right now, we have to map each individual component back to the system with their own attribute of aux 1, aux 2, aux 3, and aux 4. 

Optimally, we'd be able to make 4 aux attributes linked to n number of object types where we can just track the aux location and mapping in one spot. 

It's cumbersome, albeit doable, to update multiple object types (aux components) and their attributes separate from the mapping of the system back to the components.

[Rachel Bond]

Voting as this would be useful my use-case as well. Basically, we have one system which could have up to 4 components in it, since these components all have very different capabilities they are all tracked as separate object types. Right now, we have to map each individual component back to the system with their own attribute of aux 1, aux 2, aux 3, and aux 4. 

Optimally, we'd be able to make 4 aux attributes linked to n number of object types where we can just track the aux location and mapping in one spot. 

It's cumbersome, albeit doable, to update multiple object types (aux components) and their attributes separate from the mapping of the system back to the components.