CSV Import Fails for Object-Type Custom Fields (Object not found) in NetBox 4.3.4 #21516
Replies: 2 comments 1 reply
-
|
Hey Mandeep! NetBox 4.3 has seen some changes in how custom fields and imports are handled. For object-type custom fields, the import logic usually expects either the primary key or a unique 'slug/name' depending on the specific field configuration. Have you checked if the objects you're trying to reference in the CSV are already present in the database and that you're using the correct lookup value? If you can share a snippet of your CSV header and the problematic row (with dummy data), that would help in troubleshooting! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Pratik, Thanks for your response. I am using the attached CSV header format to upload the data. The devices and interfaces are already present in NetBox. When I select the values manually in the UI, it works without any issue. |
Beta Was this translation helpful? Give feedback.




Uh oh!
There was an error while loading. Please reload this page.
-
NetBox version
v4.3.4
Python version
(Paste from: python3 --version)
Steps to Reproduce
CSV Used
name,slug,status,identifier,type,description,cf_End_A_Interface_Origin
VSI-16,vsi-16,active,16,vpls,Test Description,18754
OR
name,slug,status,identifier,type,description,cf_End_A_Interface_Origin__device__name,cf_End_A_Interface_Origin__name
VSI-16,vsi-16,active,16,vpls,Test Description,DLE_OWAASHK_HWA673_R1_01,XGE/0/1
Expected Behavior
CSV import should resolve the object and assign the custom field value (same as manual selection via UI).
Observed Behavior
Import fails with:
"Record 1 cf_End_A_Interface_Origin: Object not found"
Even though:
Additional Information
Is this expected behavior for custom object fields in CSV import?
Is nested lookup officially supported for custom fields?
Beta Was this translation helpful? Give feedback.
All reactions