none
Ambiguous accountname

    Question

  • hi,

    we have application HRIS, this application are store user data. the goal is to provision user to AD from HRIS data source.

    HRIS data source type is TXT file (Delimited, contain displayname, employeeid,accountname, and email), so we create CSV Delimited MA, FIM MA, and AD MA, the anchor is employee id. Inbound Synchronization rule CSV relationship is using accountname..

    During Synchronization, we got error: "Ambiguous accoutname", this happen becuase there 2 line user in TXT MA with same accountname different employeeID. HR staff told me that this user is same, so we deleted 1 line in data source CSV delimited MA.

    then we run Delta Import (no error), and then Delta Sync in CSV Delimited MA but then same error "Ambiguous accountname" still appear.

    can anyone explain how to solve this error?

    how to delete the user in MV?

    Thanks.

    Endrik


    Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    • Modifié Endrik jeudi 9 mai 2013 10:38
    jeudi 9 mai 2013 10:37

Réponses

  • s the error you get "ambiguous-import-flow-from-multiple-connectors"?

    Is employee ID the same as accountname?

    There are two things you need to keep in mind:

    1) Your anchor has to be a unique attribute (no two records the same)

    2) Your join attribute should also be unique so that only one object in the CSV should ever join to a Metaverse object.

    ambiguous-import-flow-from-multiple-connectors means that two connector space objects have joined to a single Metaverse object and FIM doesn't know which connector space object to import from.

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    • Marqué comme réponse Endrik vendredi 10 mai 2013 10:54
    jeudi 9 mai 2013 11:19

Toutes les réponses

  • s the error you get "ambiguous-import-flow-from-multiple-connectors"?

    Is employee ID the same as accountname?

    There are two things you need to keep in mind:

    1) Your anchor has to be a unique attribute (no two records the same)

    2) Your join attribute should also be unique so that only one object in the CSV should ever join to a Metaverse object.

    ambiguous-import-flow-from-multiple-connectors means that two connector space objects have joined to a single Metaverse object and FIM doesn't know which connector space object to import from.

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    • Marqué comme réponse Endrik vendredi 10 mai 2013 10:54
    jeudi 9 mai 2013 11:19
  • hi Ross, 

    employee ID and Account name is different. 

    the anchor is employeeid and it's unique, the error happen because there same accountname. here the line CSV:

    First Name|Last Name|Display Name|Office|E-Mail|Account Name|Employee ID
    Endrik|Lie|Endrik Lie|KC Jakarta|endrik.Lie@contoso.co.id|endrik.lie|2650
    Endrik|Lie|Endrik Lie|KC Medan|endrik.Lie@contoso.co.id|endrik.lie|0014

    In FIM Portal, only one user with account name endrik.lie.

    Then I delete employeeID 0014 in CSV file and run again Delimited CSV MA with step below:

    1. run delta import (success),

    2. delta sync (completed with error), the error:ambiguous-export-flow-to-single-valued-attribute

    do you have idea how to fix it?

    thanks.

    Endrik


    Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    jeudi 9 mai 2013 11:49
  • When you ran the delta import, did it report a delete?

    Try running a full import... or, clearing the connector space and re-importing.

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    jeudi 9 mai 2013 12:30
  • Hi Ross, 

    When you ran the delta import, did it report a delete? no, didn't report a delete when delta import in CSV MA, only report success and unchanged... can you tell me why this happen?

    Yah, tomorrow I'll try full import. Clearing the CS will be last action, since the data is almost 25.000 user will take a lot time to deleted and re-import.

    Thanks, 

    Endrik


    Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    jeudi 9 mai 2013 12:36
  • If there is no ChangeType column in the data, there is no way to delete an object in a file MA with a delta import.  Once you have a duplicate in the connector space, you have to import the delete to get rid of it or you will continue to get the errors.

    A full import would be much more efficient and less disruptive than clearing the connector space.  In either case, make certain that the file you run the full import on has all your data, however!  If your CSV files are really just "deltas" than a full import run on one of them could delete a large amount of data and you probably don't want that.  If your CSV files fully represent the data in your HRIS, running a full import won't really take any longer than a delta import except for a brief period where the deletions are processed.

    Delta imports with a changetype column would be best, but full imports work fine for this scenario if you have the full file.  I have a file MA that runs a full import larger than 25k rows every morning that takes less than 10 minutes.  You can still run a delta sync after a full import and process only the changes picked up.

    With this kind of design you'll want to make sure that you don't continue to get duplicate rows in your import files. 

    Chris

    jeudi 9 mai 2013 16:06
  • Hi Endrick,

    Listen As Ross told You , You have to run "Full Import" thn it will show User "Delete".

    Now Why is that so ?

    When First you ran Delta Import It took both users into Connector space and Then As you are useing accountName into RelationShip criteria. So it gave error on Sync not at import. If that users had same Anchor ID thn you should have got this error on import only.

    Secondly, Why it is still showing error after user deletion from source & not showing any delete action on Delta Import?

    In my opinion it should not shown Delete action on delta import. You are still getting this error bcoz that entry is still present in the connector space.As per my Experience We should always create Full Import  for source to keep everything upto date.

    vendredi 10 mai 2013 00:08
  • Hi Ross and All, 

    it's works. Delete the line then Full Import.

    Thanks.


    Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    vendredi 10 mai 2013 10:54
  • Glad it worked out for you.

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    vendredi 10 mai 2013 14:20