Hello all,
We are working on an MS Intune integration and are facing the issue below:
We have scheduled jobs that run every 11 hours to fetch the latest data from Intune. While the data is being inserted from the source table (i.e., staging table) into the target table (i.e., CMDB hardware asset table), we observed the following behavior:
When a record has a user assigned to the "assign to" field and Intune updates this field with a new user, the target table is correctly updated with the new value.
However, when the user is removed (i.e., the "assign to" field is emptied) on the Intune side, the "assign to" field in the target table is not cleared, and the old value remains.
This behavior occurs because ServiceNow's transform maps do not clear target fields by default when the source field is blank or null. By default, if a source field is blank or null, ServiceNow ignores it during transform map processing, which results in the old value persisting in the "assign to" field.
To resolve this issue, we tried using a conditional script in the transform map that explicitly checks for empty or null values and clears the "assign to" field in the target table when the corresponding source field is empty, but it did not work.
If anyone has encountered a similar issue or has insights into resolving this within the MS Intune integration, your guidance would be greatly appreciated. Thank you!
