Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two ID columns in VLAN table #7802

Closed
rhyser9 opened this issue Nov 11, 2021 · 0 comments
Closed

Two ID columns in VLAN table #7802

rhyser9 opened this issue Nov 11, 2021 · 0 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@rhyser9
Copy link
Contributor

rhyser9 commented Nov 11, 2021

NetBox version

v3.0.9

Python version

3.9

Steps to Reproduce

  1. Create a new vlan
  2. Open the vlans table (.../ipam/vlans/)
  3. Click "Configure Table" and add the "ID" column from under "Available Columns"
  4. Export the VLAN table as a CSV file

Expected Behavior

image

The vid column should be distinguished from the netbox object ID column. For example, call it "VLAN ID".

Observed Behavior

image
image

Both the VLAN ID and the Netbox object ID have the same "ID" header, both in the table and in the CSV export. This causes an issue with anything consuming the exported CSV file, as the ID header is now ambiguous.

This bug was introduced in v3.0.9 via FR #6930 / PR #7673.

class VLANTable(BaseTable):
pk = ToggleColumn()
vid = tables.TemplateColumn(
template_code=VLAN_LINK,
verbose_name='ID'
)

@rhyser9 rhyser9 added the type: bug A confirmed report of unexpected behavior in the application label Nov 11, 2021
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Nov 11, 2021
@jeremystretch jeremystretch self-assigned this Nov 11, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants