Automatic 2 way linked assets
Loving the new way related assets automatically create a link.
One further enhancement I would like to request is the ability to define a two way asset link.
Whilst there are some times when the current way is better, there are times when I want to have a bidirectional record:
e.g. a sim card is in a router and a router has a simcard in it
I have created asset links on each, but, to me, it would make more sense that if asset type a contains an asset link field to asset type b, and asset type b contains an asset link field to asset type a, hudu could be smart enough and ask "Do you want to link these fields?" or similar.
Log in to comment and vote
Comments4
Coffee Moss
Apr 6, 2025
Sounds like this is what I would like to see as well. - I have a Person and a PC. I want to LINK the Person to the PC. When I follow the LINK to the PC, I would like to see that PC LINKED back to the person. At this time, I have to create a second LINK from PC to Person and when things change, we need to remember to remove both links. If they were LINKED as a two-way relationship, which everything really is, we would only need to create the LINK or relationship once.
Silver Hubble
Oct 6, 2021
Same here. I made the workaround too but graphically is awful
Sapphire Pinwheel
Feb 23, 2021
I think I understand what you're saying here, but to clarify, are you saying you want a custom field in one asset type to link to a custom field in another asset type? That would be very helpful for us.
Indigo Magnetosphere
Feb 24, 2021
Michael H.: Yes! :)
Whilst many things can be a 1:Many link where you have a person who can have many different items linked (through relations), there are a few things that have assets that need to be tracked, but, will only ever be 1:1
For example, a mobile phone or router and a sim card… Both are independent assets we need to track for a variety of reasons, but, a sim card will only ever be in one phone and one phone will only ever have one sim card (exception being a dual sim phone… but, they will have a new field called sim2!). This also feeds in to another suggest I had which is optionally restrict asset field to a finite amount of assets.
If I add the phone to the sim, I want the sim field in the phone to be updated rather than just a relation, or, vice versa.
Going to the extreme, I know Jacob mentioned IPAM abilities - imagine being able to have an asset with repeatable fields (That was a suggestion somewhere) so you have a switch with 48 ports… You can then have a device, and basically a relation/field can be a "cable" linking 1:1 - Not saying it will be easy, but, we could have automatic network mapping/topology and more in documentation based off relation fields…