Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-10920

Import with "Missing objects: Update" rule clears the value of "Attribute to edit" if external Data Locator value have changed

      Issue Summary

      Import with "Missing objects: Update" rule clears the value of "Attribute to edit" if external Data locator value has changed. This is happening despite the fact the object has not been missing.

      This is happening only for existing objects that have been updated (changed) by the import (for example, if some mapped attribute gets modified during the import).

      Steps to Reproduce

      1. Make sure your Object has an attribute that will be used with "Missing objects: Update" Import rule
      2. Create an import that will:
        • Have "Missing objects: Update" rule configured
        • Select your attribute in "Attribute to edit" field, and set "New value of attribute to edit" to the desired value.
        • Set your desired threshold
      3. On the external source, edit some value of a Data Locator, so that this change will get reflected on the Insight attribute after the sync
      4. Run the import manually

      Expected Results

      The modified data coming from Data Locators get synced to Insight attributes, and "Attribute to edit" will not change since the object is not missing (hence, no need to update the attribute).

      Actual Results

      The modified data coming from Data Locators get synced to Insight attributes, but also, value of "Attribute to edit" gets cleared (current attribute value gets removed).

      Example:

      • We have "Status" attribute that becomes set as Active when a Person gets sync with LDAP import:
      • LDAP import configuration that will set "Status" to Inactive if the Person is missing after the threshold has been reached:
      • After the "User principal name" gets changed on the directory side, and after we sync the LDAP import, the "User principal name" Insight attribute gets changed, "Status" value also gets cleared, which is not expected:

      Notes

      • Tested with CSV and LDAP import, possible that other import types are affected.
      • Affected attribute types are Status and Boolean, possible that other attribute types are affected.

      Workaround

      Create an Automation rule that will restore the cleared value to its original value. This can be used only if existing objects have a predefined, known value for the attribute that is supposed to be changed by "Missing objects: Update" rule.

      For example, this Automation rule will set cleared value for "Status" attribute to Active, which was the value that gets cleared by the import:

        1. screenshot-1.png
          screenshot-1.png
          45 kB
        2. screenshot-2.png
          screenshot-2.png
          13 kB
        3. screenshot-3.png
          screenshot-3.png
          17 kB
        4. screenshot-4.png
          screenshot-4.png
          54 kB

            [JSDSERVER-10920] Import with "Missing objects: Update" rule clears the value of "Attribute to edit" if external Data Locator value have changed

            There are no comments yet on this issue.

              4dcffb92068e Orest Busel (Inactive)
              mfilipan Marko Filipan
              Affected customers:
              5 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: