Duplicate or conflicting column header for "" when importing power feeds

[bellwood]

I am attempting to import new power feeds on v4.3.2.

I exported my current data (to use as a guide/template), made the changes required to reflect a new zone with panels/feeds that have been added and attempted to import it back.

All the fields are in the order shown under the import tool; required fields are present.

Upon attempting to import from the input (and file upload) I receive:

Duplicate or conflicting column header for ""

I have a few columns that are all empty but they are all optional columns and only present for data ordering, for instance there is an empty column for location before rack and empty columns for tenant and description so that I can enter data for comments.

The error message is rather unhelpful in this regard.

Thank you.

[bellwood]

Alrighty, coming full circle here.

1. Column position in your dataset doesn't matter, it goes by the column headers which must be lower case and snake cased if needed, e.g: power_panel

2. The rack column is just its' name, however, you must also specify the related location.name in the location column.

3) Please note that you cannot just import NEW data (additions). The import tool will leave you ONLY with what you import. Make backups. Be careful.

Thoughts/suggestions:

1. Having the column headings in the textbox (import tool wide) at render would be helpful. I understand using Label values for them when you export, but, it can/did lead to confusion.

2. If there is an attempt to import a rack column and there is no location column in the dataset, the toast notification clarifying the constraint would be helpful e.g: "Attempting to import column rack without required column location"

3) When importing, if there is existing data, notify the user they are about to drop existing and re-populate with the imported objects versus append. It might be handy to offer users an "append to existing data" option when importing. Reason for this being, otherwise, to bulk import new objects, you need to export everything, massage the data, heavily and then re-import everything (including the id column for the existing objects as well)

I'm not sure if any of this would really be considered bugs but as a Netbox user since 2016, there certainly seems to be some room for improvements.

Thanks.

[bellwood]

Resolving this.

Point 3 was entirely invalid and caused by caching of the response showing what was imported versus all objects.

Documentation could be improved and/or be made consistent with the lack of pre-populated header fields in the import form.

I'm happy to make a PR if there is interest Stretch?

Thanks.