Skip to main content

Repeating Fields in Assets

Core Web App

I'd like to see the ability to add a group of fields which can be repeated within an asset.
For instance if you have an asset type for a switch, you could have a group of fields for each port with for example - Port Name\Number, IP, VLANs, Connected To (Asset list) and you can add as many of these as you like to capture important ports - without having to have a template for different switch port counts

4 comments

Log in to comment and vote

Comments4

  • Black Moss

    •

    Aug 2, 2022

    Also in complete agreeance! Having a repeatable, embeddable fieldset for each network interface on a device would be amazing. Another use case would be storage arrays, especially in an instance where there are multiple RAIDs, JBODs or even multiple physical disks in play. Included fields would be # of disks, RAID Type, Total Capacity, Hosted Volumes, etc. as appropriate.

  • Apricot Astronaut

    •

    Feb 15, 2022

    Was about to submit this below, your post showed up as a suggestion. Totally agree with you.
    Would be cool and useful to be able to mark a field within an asset "duplicable" as well as have a group of fields duplicable.
    For example, say you have an IP text field in an asset. And then a particular instance of that asset type has two IPs. When editing the asset, you just click a plus button to add a second IP field.
    Expand on that and say you have a group of fields called interfaces, comprised of fields for type, MAC address, and IP address. Then you have an asset instance with two interfaces. You click a plus button for the field group, and document the second interface.
    Currently you can sort of accomplish this by just having a rich text field and using tables or whatnot. However, there are many benefits to breaking down the individual pieces of information into separate fields. It makes it more clear what's expected to be documented. It keeps the formatting consistent. Etc.
    Without being able to have a dynamic number of fields for specific types of information, I find myself making almost everything a rich text field in case there's more than one - more than one interface, IP address, license key, serial number (it can happen), whatever the case may be.

  • Indigo Magnetosphere

    •

    Oct 1, 2020

    I was thinking hard about this whilst populating my own documentation… I certainly in theory think your idea is great for certain assets, however, I'm also thinking that combined with what I wrote here ( https://hudu.canny.io/feature-requests/p/ability-to-inline-include-fields-from-linked-assets ), they can supercharge each other!
    A switch has x "ports" - ports belong to a switch and are repeatable fields as some will have 24, 48 or other.
    VLAN is a separate asset type - you should be able to inline join one to a port.
    This opens more questions such as should IPs belong to the repeatable element on the switch or the VLAN asset…
    I'm just thinking it would be great to fully document your entire client networks with ease and integration to the IPAM idea (if it happens)
    Imagine being able to associate the same VLAN asset with every device asset on the VLAN… Being then able to click the VLAN on the switch, see every device that's linked… being able to draw topology and more.
    … A huge area of my business is managing IoT devices and I'm currently linking Sim cards to routers to other assets - the possibilities of combining repeating fields alongside easier linking/relating to other devices opens up so many possibilities for the future.
    I just hope I haven't completely overcomplicated this! :)

  • Yellow Nucleon

    •

    Oct 1, 2020

    This would be very useful. It would also help with software licenses, where we need to keep track of purchase dates, counts, etc.