Why attribute that is not present in object in metaverse, but present in MA connector space is not deleted there? RRS feed

  • Question

  • I have attribute flow between metaverse and MA where there is direct export from metaverse attribute "AA" to MA attribute "AB"

    Person object has no attribute "AA" in metaverse. But has attribute "AB" in connector space.

    Why it is not deleted on export? I looked in log and I see that metaverse is exporting value on that attribute, but why? If that attribute is not present in metaverse, from where the value is coming from?

    Wednesday, March 15, 2017 3:57 PM

All replies

  • You are not allowing null exports. Make sure this box is checked.

    Nosh Mernacaj, Identity Management Specialist

    Wednesday, March 15, 2017 5:04 PM
  • I've done that. At first it seems good. I run export, all empty values are deleted. Then import shows no updates on those fields because on both sides they are empty.

    But after Full Sync, I get pending export on those fields to delete again, but it shows that both sides are empty. What can be the problem now?
    If on both sides are null values, why it wants to delete them again, unless on MA side, value gets updated to empty string somehow.
    Friday, March 17, 2017 8:40 AM