Hello!
I would like to export information from a referenced object during export flow but the referenced object is not part of the connector space object of the affected management agent. This is my demo configuration:
testEmployeeData:
- employeeId (anchor)
- personId (reference to testPerson object)
- telephoneNumber
- uid
testPerson:
- displayName
- givenName
- sn
- uid (anchor)
- employeeData (multi-value reference to testEmployeeData recors; can be null)
I have an SQL agent ("HR") that imports person and employeeData objects into the metaverse. The references seem to work as I can see them in the Sync Service Manager and they point to the right objects too. Now I would like to access some of the referenced objects' data during export attribute flow. I have configured an export-only "Persons" agent that should export the personal data into an attribute-value file. This is what I would like the export flow to look like:
displayName <- testPerson.displayName
employeeId (multi-value) <- testEmployeeData.employeeId (*)
firstName <- testPerson.firstName
lastName <- testPerson.sn
uid <- testPerson.uid
The problem is now the advanced attribute flow marked with (*). The testPerson.employeeData field contains a multi-valued reference to all matching employeeData records which contain the employeeId. The output file should contain all matching employeeIds instead of the reference values (GUIDs) but I can't get this to work. When I try to configure an advanced export flow rule flowing testPerson.employeeData to person.employeeId I just receive an error message stating that metaverse reference attributes cannot be defined as source attributes.
Do I have to create an appropriate connector space object for this to work? Or is there some other way to dereference objects in order to get certain attributes? By the way, the person connector space object in the "Persons" agent is created by
provisioning code based on testPerson metaverse objects.
Regards,
Philipp