starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #2915] [Feature Request]: Hudu - Ability to choose fields for matching #1443

New issue

Closed

opened 2026-03-02 13:44:14 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:44:14 +03:00

Owner

Originally created by @HappyEarthDay on GitHub (Oct 3, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2915

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

We absolutely love the CIPP-Hudu integration. Our RMM also has an integration with Hudu. We wanted all our Computer assets in the same asset type in Hudu, with the goal of incorporating all of the data from both integrations. Turns out each integration is matching on different values for Serial Number:

Hudu's default Computers asset uses the "Service Tag" field
CIPP matches on the "Primary Serial" field
RMM matches on the "Serial Number" field

This results in duplicate assets for each device: we have one asset created by CIPP, and one asset created by the RMM.

To fix this, and allow us to have a single asset for each device with information from many integrations (not just Level) CIPP could:

GET the fields in already selected the Asset Layout in the Hudu settings for 'Asset Layout for M365 Devices'
Optionally, display the all of the "Text" type fields to the user, and allow the user to select which text field should be used for the serial number matching.
Match serial number on that field going forward.

PowerShell commands you would normally use to achieve above request

No response

Originally created by @HappyEarthDay on GitHub (Oct 3, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2915 ### Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole. We absolutely love the CIPP-Hudu integration. Our RMM also has an integration with Hudu. We wanted all our Computer assets in the same asset type in Hudu, with the goal of incorporating all of the data from both integrations. Turns out each integration is matching on different values for Serial Number: - Hudu's default Computers asset uses the "_Service Tag_" field - CIPP matches on the "_Primary Serial_" field - RMM matches on the "_Serial Number_" field This results in duplicate assets for each device: we have one asset created by CIPP, and one asset created by the RMM. To fix this, and allow us to have a single asset for each device with information from **many** integrations (not just Level) CIPP could: - GET the fields in already selected the Asset Layout in the Hudu settings for 'Asset Layout for M365 Devices' - Optionally, display the all of the "_Text_" type fields to the user, and allow the user to select which text field should be used for the serial number matching. - Match serial number on that field going forward. ### PowerShell commands you would normally use to achieve above request _No response_

kerem

2026-03-02 13:44:14 +03:00

closed this issue
added the
enhancement

no-priority

no-activity
labels

kerem commented

2026-03-02 13:44:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 13, 2024):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

@github-actions[bot] commented on GitHub (Oct 13, 2024): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

kerem commented

2026-03-02 13:44:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 27, 2024):

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions[bot] commented on GitHub (Oct 27, 2024): This issue was closed because it has been stalled for 14 days with no activity.

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#1443

No description provided.

Rows
Columns