Hello!

I have MA for csv file.

When I do Full import and Full Sync to metaverse, in metaverse attribute Manager is clear.

Preview Full Sunc - Attribute Manager - Applied Delete and Final Value is Deleted.

Users have ID.

Manager in csv - ID.

In Csv MA Manager is Reference(DN) attribute.

Why I get clear attribute in metaverse?

Is Manager in MV??

You need 2 Syncs, one to import all users and a second pass will make the referential correlation to Managers.

Nosh:

During import attribute flow if a reference is made to a Metaverse object that doesn't exist the source object is marked for a reference retry. After the sync has made a pass on all of the objects and given all of the objects a chance to join or project to the Metaverse, then the sync will reevaluate all of the objects marked for a reference retry.

Alex:

First double check that the manager object exists in the Metaverse.

Second what is the anchor attribute in the CSV MA? Is it ID?

Third, what exactly is in the Manager attribute is it the ID of the manager?

What I am trying to say is that the reference attribute has to have the value of the anchor attribute on the object to which it points.

For example let's say you have an EmployeeID as well as Employee Number (happens sometimes especially after mergers or switching HR systems).

This simple table illustrates the point. If EmployeeID is the anchor then this is correct as Joe Idaho will show up as the manager for Steve Old. If however, EmployeeNumber is the anchor then Steve Old's manager won't be linked in the Metaverse.

Hello!

My problem is resolved!

I think about, issue been in the csv file. In the csv file need have all users. Is it correct?  

Yes, you need both user and his manager in the same file.

I believe we mentioned this many times, although in different ways.

It would be wise to let the community know that you are newbie next time you ask questions, so they know what language to use.