[GH-ISSUE #1388] Add Autopilot Device - Case Sensitive CSV #769

Closed
opened 2026-03-02 12:45:04 +03:00 by kerem · 3 comments
Owner

Originally created by @Ben-ITLogic on GitHub (Feb 22, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1388

Description

When using the Add Device function the CSV columns are case sensitive on import which causes issues with vendor provided CSV files who use different heading casing.

Our vendors (and HP direct) provide us with the CSV file with the case as:

  • Device Serial Number
  • Windows Product ID
  • Hardware Hash

The CSV file needs these in the below case:

  • Device serial number
  • Windows product ID
  • Hardware hash

Environment data

Self Hosted in Azure.
Originally created by @Ben-ITLogic on GitHub (Feb 22, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1388 ### Description When using the Add Device function the CSV columns are case sensitive on import which causes issues with vendor provided CSV files who use different heading casing. Our vendors (and HP direct) provide us with the CSV file with the case as: - Device Serial Number - Windows Product ID - Hardware Hash The CSV file needs these in the below case: - Device serial number - Windows product ID - Hardware hash ### Environment data ```PowerShell Self Hosted in Azure. ```
kerem 2026-03-02 12:45:04 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 22, 2023):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:1440990125 --> @github-actions[bot] commented on GitHub (Feb 22, 2023): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@Ben-ITLogic commented on GitHub (Feb 22, 2023):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

<!-- gh-comment-id:1440998192 --> @Ben-ITLogic commented on GitHub (Feb 22, 2023): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
Author
Owner

@BNWEIN commented on GitHub (Feb 23, 2023):

This has been fixed in PR #1390, should be added in the next update.

<!-- gh-comment-id:1442150729 --> @BNWEIN commented on GitHub (Feb 23, 2023): This has been fixed in PR #1390, should be added in the next update.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#769
No description provided.