Site-Based Filtering for Bulk Import

[mkarel]

NetBox version

v4.3.5

Feature type

New functionality

Proposed functionality

Similar to Feature Request 19840 , it would be highly beneficial to extend site-based filtering capabilities to the bulk import process for the following object types:

• Modules
• Interfaces
• Front Ports
• Rear Ports
• Console Ports
• Console Server Ports
• Power Ports
• Power Outlets
• Module Bays
• Device Bays
• Wireless Links

Use case

This enhancement would streamline bulk data management and improve operational efficiency by allowing users to target specific devices within a site. It would also eliminate the need to manually look up device IDs for device's when you have an environment where devices share the same name across multiple sites.

Database changes

None

External dependencies

None

[gadler01]

I agree with mkarel. We move datacenters and often have multiple sites containing the same device that is being moved.

[jeremystretch]

While I appreciate the use case, we cannot keep adding columns arbitrarily to the myriad import forms. (Consider hypothetical similar requests for location, region, etc.) If we want to support this functionality, a more robust mechanism of dynamically extending the import forms needs to be identified (e.g. by specifying device.site rather than treating site as its own field).

[mkarel]

@jeremystretch I agree that arbitrarily adding columns to a wide range of import forms wouldn’t be ideal. I also support enhancing import functionality to allow the use of objecttype.property (e.g., device.site) in import files, enabling additional fields to be populated and used to target devices if that is seen a better solution then adding site to each import function.

This feature request stemmed from a situation I encountered that closely mirrored the referenced issue. I was importing front and rear ports for patch panels at a site where we reused the same names due to our naming conventions. As a result, I had to rely on device.id to complete the import, which required extra effort. If I had been able to include the site name in the import to target only devices within that site, it would have saved a significant amount of time.

I believe @gadler01 ran into a similar challenge when importing interfaces, as device names are reused between the source and destination data centers.

Interestingly, your proposed solution is something I initially tried as a workaround.

[gadler01]

I agree wholeheartedly with @mkarel . We move datacenters and as such have duplicate devices in the source and the destination. In v3 this was possible because the device was unique per site. It's difficult with the dependence on to device.site being the requirement.