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

Custom field's default value not respected when using bulk import CSV #16073

Open
diondohmen opened this issue May 10, 2024 · 0 comments
Open
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@diondohmen
Copy link

diondohmen commented May 10, 2024

Deployment Type

Self-hosted

NetBox Version

v4.0.1

Python Version

3.12

Steps to Reproduce

P.S.
Tested this also with the current public demo instance of Netbox giving the same result.

  1. Add a new custom field with the following specs:
  • Object-type: DCIM > Device
  • Name: 'test_default'
  • Type: Boolean
  • Required: False
  • Default: true

afbeelding

afbeelding

  1. Use 'Device Bulk Import' feature together with the following CSV file.
    The CSV doesn't mention the cf_test_default column/value so you would expect Netbox to enter the default value

public_dev_netbox_devices_import_ttt.csv

afbeelding

  1. After submitting you can see the device has been added but the custom field 'test_default' is empty.
    afbeelding

Expected Behavior

The custom field's value should be 'True' like in the following screen:
afbeelding

Observed Behavior

The custom field's value is empty/null using the Device Bulk Import.
When adding a device manually, the dropdown box is pre-filled with the correct default value of True

@diondohmen diondohmen added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels May 10, 2024
@abhi1693 abhi1693 added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available 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