We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Assistance Required to Identify Why Assigned To Field Is Not Updating for a Few Intune-Integration

Harsh3842
Tera Contributor

2 hours ago

Hi All,

We have an integration with Microsoft Intune that populates records in the Hardware [alm_hardware] table. During my investigation, For example, let's say there are approximately 100 records received from Intune, the Assigned To field is being populated successfully for 97 records, while 3 records are not getting updated.

I have performed the following checks so far:

What I Have Verified

  1. Data Source

    • Verified that the data is being received correctly from Intune.
  2. Import Set Table

    • Confirmed that the records are being imported successfully.
    • The Import Set status shows Processed.
  3. Robust Transform Map

    • Verified that the Transform status shows Completed.
    • In the RTE Entity Operation related list, I can see that the User Lookup operation is configured.
    • The source fields:
      • u_userprincipalname
      • u_userdisplayname
    • are mapped to the target field:
      • assigned_to_user
  4. IRE Analysis

    • I checked the available IRE payloads for the affected records.
    • However, I do not see any payloads containing the relevant Serial Number or Configuration Item information for these three records.
    • Because of this, I am unable to perform an IRE Simulation to understand the decision-making process.

My Current Understanding

Since the integration is working correctly for 97 out of 100 records, the mapping and overall transform logic appear to be functioning as expected.

One possible conclusion I reached is that these three records are manually updated and perhaps that is preventing subsequent updates from the integration source.

However, this raises a question:

Shouldn't incoming data overwrite the existing values during the transform process if the record meets the identification criteria?

If my understanding is incorrect, could someone please clarify how Robust Transform Maps and IRE handle manually modified records in such scenarios?

Environment Comparison

To rule out configuration issues, I compared the behavior across environments:

  • DEV Instance

    • All three affected serial numbers are updated correctly.
    • The Assigned To field is populated successfully.
  • UAT and PROD Instances

    • The same records are not getting the Assigned To field updated.

Because of this discrepancy, I reviewed and compared:

  • Scheduled Jobs
  • Transform Maps
  • Scripts
  • Related configurations
  • IRE Rules

So far, I have not identified any significant differences between DEV, UAT, and PROD. Of course, it is entirely possible that I may have missed or overlooked something during the comparison.

Questions for the Community

Could anyone please help me understand the following:

  1. What could cause the Assigned To field to update for the majority of records but consistently fail for only a small subset of records?
  2. Can a previously manual update prevent future updates from Intune or the Robust Transform process?
  3. Are there any IRE, CMDB, Data Manager, Reconciliation, Data Source Rule, or Robust Transform behaviors that could explain why DEV updates these records while UAT and PROD do not?
  4. Since no IRE payload is available for these records, are there alternative troubleshooting methods that could help identify where the update is being blocked?
  5. Is there anywhere else I should be looking that is commonly overlooked in similar situations?

At this point, the data is successfully reaching the Import Set table and the transform process completes without errors, but the target Assigned To field is not being updated for these specific records. Any insights, suggestions, or troubleshooting recommendations would be greatly appreciated.

Thank you in advance for your assistance.

0 Helpfuls
  • 50 Views
0 REPLIES 0