Easy feature request about custom field

I can not hide custom property by subnet/supernet/group. There are some custom fields that I do not want to see on other groups/subnet/supernets etc. Therefore custom property field is pretty useless since it show extra/unnecessary information for the subnet/supernet/group.

I should create a custom property field then I want to choose that custom property to show on specific subnets/supernets/groups etc. I think it is very easy to do(fix) it! Please include this request for your next release.

Thanks.

Find more posts tagged with

custom_field

Accepted answers

All comments

mavturner

I've noted this as a feature request per the other thread you posted this in. We can look at this as part of our user delegation work. Does anyone else have this requirement? This is the first time I've heard this request.

You can hide the columns in the subnet management page (this applies to all subnets). To hide or show columns, simply mouse over any column, a down arrow should appear, left click on this and go over the Columns field, un-check any column you don't want to show up and check any column you want to be displayed.

Mav

ctopaloglu

Mav,

I am sorry but I don't understand your point.

Let me give you an example. I created three custom fields for my DMZ Server Farm subnets.

I am looking my LAN Server Farms subnets. Guess what? I am seeing completely unrelated custom fields with my LAN Server Farms subnets. Now imagine you have different kind of groups/subnets and you have to hide or unhide every one of them for every other subnet or group! It is not simple as you see. It is very disturbing.

I am waiting a fix for this. Thanks for listening.

mavturner

I provided the steps to "hide" columns that you do not want displayed. Unfortunatley, this affects all subnets, not just the specific you you set it on.

The short of it is, you can't do this today and I've logged the feature request. When you create a custom property, it is available for all subnets (or IPs depending on the type).

Filter.PNG

ctopaloglu

The short of it is, you can't do this today and I've logged the feature request.

Mav,

It is not good enough for us. We are migrating our mySQL IP tables to IPAM. I get lots of trouble because of of this. It should be high on the list! This is a basic one. Orion's power comes from customization and there is no way to customize IPAM fields. Manual method is too painful for us.