Assigned To Intune

[sntech]

Hi,

We want to add a validation on Intune Staging table, that if CI records already has "Assigned To" updated, Staging table value should not override it. 

If Assigned To on CI records is empty then only allow staging table to update "Assigned To" field on CI record.

[shubhamseth]

@sntech 

A better approach is to add the validation in the Transform Map (or a custom Robust Transform Map if you're using IntegrationHub ETL).

Before updating the CI, check whether the existing assigned_to field is already populated. If it is, simply skip updating that field. If it's empty, allow the value from the Intune staging record to be applied.

For example:

if (!target.assigned_to.nil()) {
    target.assigned_to = target.assigned_to; // Keep existing value
} else {
    target.assigned_to = source.assigned_to;
}

This ensures that user assignments made manually or by another authoritative source aren't overwritten by Intune, while still allowing Intune to populate the field when it's blank. It also keeps the customization isolated and upgrade-safe.

If you are using Integration Hub ETL, please handle the same using Reconcilation Rule based on data source and give high priority to manual entry for 'Assign To' field than other data source. 

[Kieran3]

Hi @sntech 

My recommendation is to handle this in the transform map for the Intune Staging import.
Add an onBefore transform script (or equivalent field-level transform condition) so that the Assigned to field is only populated on the target CI when that field is currently blank, and is left unchanged when a value already exists. This is the cleanest way to enforce the requirement without overwriting existing assignment data during the import process.

If this didn't help, let me know and we can discuss further.

If it helped, please mark it as correct so it can help others looking for a solution 🙂