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

CSV Import Problem with custom fields #14675

Open
2 tasks done
Bradley369 opened this issue May 3, 2024 · 2 comments
Open
2 tasks done

CSV Import Problem with custom fields #14675

Bradley369 opened this issue May 3, 2024 · 2 comments

Comments

@Bradley369
Copy link

Bradley369 commented May 3, 2024

Debug mode

Describe the bug

When importing AND updating assets by using the CSV import feature. I am unable to populate custom fields with the type "list".

All asset models are linked with this set of custom fields and the list item exists in the custom field list. I am able to manually update these custom fields but not when importing.

Reproduction steps

  1. Create custom fields called "server fileds"
  2. Make this custom field optional, with the type "list" and populate an option of "RACK Fix depreciation math #1"
  3. Link the asset model to this custom field
  4. Import csv with both the asset model and custom field as a column
  5. Verify that the custom field has been populated

Expected behavior

I would expect that the custom field is populated and not left blank.

Screenshots

Unable to provide screenshots of work environment.

Snipe-IT Version

v6.2.3

Operating System

Ubuntu

Web Server

Docker/Kubernetes

PHP Version

N/A

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

Copy link

welcome bot commented May 3, 2024

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@snipe
Copy link
Owner

snipe commented May 22, 2024

v6.2.3 i from quite some time ago. Please upgrade and let us know if you're still having the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants