starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Prefix export replacing subnets with • #6502

New Issue
Closed
opened 2025-12-29 19:41:38 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:41:38 +01:00
Owner
Copy Link

Originally created by @bakergt1 on GitHub (May 23, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

V3.2.2

Python version

3.9

Steps to Reproduce

  1. Select selecting prefixes from site
  2. export current view
  3. Output is showing as

Prefix
10.51.16.0/20
"•

10.51.16.0/24"
"•

10.51.17.0/24"
"•

10.51.18.0/24"
"•

10.51.20.0/22"

Expected Behavior

there should be no • and blank lines in the export

Observed Behavior

nil

Originally created by @bakergt1 on GitHub (May 23, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version V3.2.2 ### Python version 3.9 ### Steps to Reproduce 1. Select selecting prefixes from site 2. export current view 3. Output is showing as Prefix 10.51.16.0/20 "• 10.51.16.0/24" "• 10.51.17.0/24" "• 10.51.18.0/24" "• 10.51.20.0/22" ### Expected Behavior there should be no • and blank lines in the export ### Observed Behavior nil
adam added the type: bugstatus: accepted labels 2025-12-29 19:41:38 +01:00
adam closed this issue 2025-12-29 19:41:39 +01:00
adam commented 2025-12-29 19:41:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 23, 2022):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (May 23, 2022): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 19:41:40 +01:00
Author
Owner
Copy Link

@inigoleaga commented on GitHub (May 23, 2022):

I have the same issue. Let me introduce some more info:

Netbox version:

v3.2.2

Python version:

v3.8.10

Steps to Reproduce:

  1. Go to IPAM -> Prefixes
  2. Filter the prefixes you want to export
  3. Select Export -> Current view
  4. A .csv will be downloaded.
  5. Open the .csv

Expected behavior:

When you open the CSV file you can see all the prefixes you had in your filter.

Observed behavior:

When you open the CSV file you can only see the parent networks. Any other prefix that is a child of another, will appear as "•". Please, check the attached image:

image

Hope this clarifies the issue.

@inigoleaga commented on GitHub (May 23, 2022): I have the same issue. Let me introduce some more info: ### Netbox version: v3.2.2 ### Python version: v3.8.10 ### Steps to Reproduce: 1. Go to IPAM -> Prefixes 2. Filter the prefixes you want to export 3. Select Export -> Current view 4. A .csv will be downloaded. 5. Open the .csv ### Expected behavior: When you open the CSV file you can see all the prefixes you had in your filter. ### Observed behavior: When you open the CSV file you can only see the parent networks. Any other prefix that is a child of another, will appear as "•". Please, check the attached image: ![image](https://user-images.githubusercontent.com/43034818/169822680-913bfcf2-41db-460a-a0ba-b2b2942ed3ad.png) Hope this clarifies the issue.
adam commented 2025-12-29 19:41:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 24, 2022):

The garbage characters result from improperly decoded Unicode, representing the hierarchical indentation of each prefix. You'll need to investigate your NetBox deployment and/or browser to determine why the fields are not being decoded properly. (You can confirm that this works as expected on the public demo instance.)

As for the content itself, it should be possible to implement a custom table column that omits the prepended characters from the output when rendering CSV data. Alternatively, you can work around this by swapping out the "Prefix" table column with the "Prefix (flat)" column before performing the export.

@jeremystretch commented on GitHub (May 24, 2022): The garbage characters result from improperly decoded Unicode, representing the hierarchical indentation of each prefix. You'll need to investigate your NetBox deployment and/or browser to determine why the fields are not being decoded properly. (You can confirm that this works as expected on the public demo instance.) As for the content itself, it should be possible to implement a custom table column that omits the prepended characters from the output when rendering CSV data. Alternatively, you can work around this by swapping out the "Prefix" table column with the "Prefix (flat)" column before performing the export.
adam commented 2025-12-29 19:41:41 +01:00
Author
Owner
Copy Link

@bakergt1 commented on GitHub (May 24, 2022):

Thanks Jeremy, this is only a new problem we have come across, its something that I have been using often. But we will investigate locally and see if we can work out what is happening.

@bakergt1 commented on GitHub (May 24, 2022): Thanks Jeremy, this is only a new problem we have come across, its something that I have been using often. But we will investigate locally and see if we can work out what is happening.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6502
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?