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

Feature Request: Enhanced Bulk CSV Import Error Handling #427

Closed
2 tasks
Anonymenet77 opened this issue Oct 9, 2024 · 1 comment
Closed
2 tasks

Feature Request: Enhanced Bulk CSV Import Error Handling #427

Anonymenet77 opened this issue Oct 9, 2024 · 1 comment

Comments

@Anonymenet77
Copy link

Anonymenet77 commented Oct 9, 2024

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues

GLPI Version

10.0.16

Plugin version

2.13.5

Bug description

Unless I’m mistaken, I haven’t noticed this feature.

USE CASE 1:
I would like that during a bulk .csv import, if there is a data entry error in a column corresponding to a multiple field in GLPI, the affected row should not be added. At the end of the import process, I would like to be informed of the rows that encountered errors and were not imported into GLPI. Additionally, the valid rows should be successfully imported, as no anomalies were found.

USE CASE 2:
In the event that USE CASE 1 is not feasible, I propose that if an error occurs during the import, the entire file should be rejected and no data should be added to GLPI. A message should then indicate that an error has been detected in the file.

Best Regards,

Relevant log output

No response

Page URL

No response

Steps To reproduce

No response

Your GLPI setup information

No response

Anything else?

No response

Copy link

This issue has been closed as we only track bugs here.

You can open a topic to discuss with community about this enhancement on suggestion website.
You can also contact GLPI editor team directly if you are willing to sponsor this feature.

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

No branches or pull requests

2 participants