none
convert string value to reference RRS feed

  • Question

  • Hi

    From a CSV file I have an accountname in clear text (string value) that I want to sync with the manager attribute (reference) in MV and from there export to the Manager attribute (reference) in the FIM portal.

    I am using FIM 2010 R2.

    Any suggestions how this is possible ?

    Thanks

    Per

    Friday, February 22, 2013 8:25 AM

Answers

  • Okay.

    The best way to check this is to limit the scope. If you import both the employee and the manager from the CSV file, then you should have two objects in the metaverse and for the employee the value of the manager should be a clickable link that refers to the manager object. From you screenshot it could look like you don't have the manager's object in the metaverse? Try the following -

    1) On the CSV MA, make sure that the manager field is marked as a reference

    2) Make sure that you project a person object to the metaverse (after your join rule)

    3) Configure an import flow on the CSV MA for CS:Manager -> MV:manager

    4) Do a Full Import/Full Sync

    5) See that you get both objects into the metaverse

    6) Do a metaverse search and verify that the manager field of the employee is now a clickable link

    the CSV file should look something like this -

    AccountName;Manager
    xxaa;xxbb
    xxbb;xxcc
    xxcc;

    That should work as this is standard FIM functionality. Get that working and then move on to the portal export stuff later.


    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, February 26, 2013 9:36 AM
  • Per,

    where is the relationship information located / stored (manager)?

    When using files, you can feed reference information such as manager in form of AVP files into the system.

    Here is an example.

    This means, you may have to turn your CSV into an AVP using a script or you will have to create an additional AVP file that provides just the reference information.

    Cheers,
    Markus

     


    Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

    Friday, February 22, 2013 1:59 PM
  • The problem is that I can not get my manager value (eg. Manager=xxxbbb) to translate into a MV resource ID which is the correct format for the manager reference in the MV (eg. manager={16E5E3C6-6E6C-E211-9733-005056A97892})  

    Per, you don't need to translate it that way - this is what the sync engine does for you.

    What you need to do is to make sure that the references are tracked correctly in your data source – which could be the AVP file.

    Have you seen “Understanding Reference Attributes Processing in FIM” yet?
    The article might help to shed some light on it.
    One suggestion I have for you is to forget about your actual scenario for a moment.
    You can use just the inbound part from “HR” in the article I have referenced above to get a feeling for how references are processed.

    Cheers,
    Markus


    Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation


    Monday, February 25, 2013 8:39 PM

All replies

  • Per,

    where is the relationship information located / stored (manager)?

    When using files, you can feed reference information such as manager in form of AVP files into the system.

    Here is an example.

    This means, you may have to turn your CSV into an AVP using a script or you will have to create an additional AVP file that provides just the reference information.

    Cheers,
    Markus

     


    Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

    Friday, February 22, 2013 1:59 PM
  • You can also do this using a CSV file (if the attribute is singled valued)

    But for references to work the referred object needs to be included in the csv file and needs to be joined to the correct metaverse object for references to be imported correctly, for instance, if you have the following csv file, which includes 3 records with 2 headers:

    accountname, manageraccountname

    test1, test2

    test2,

    test3, test1

    You first need to join the records to the metaverse object using the accountname attribute, set the accountname as 'anchor' and set the manageraccountname attribute as reference, then you can flow this to the manager attribute.


    Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!

    Monday, February 25, 2013 7:14 AM
  • Hi Markus and Paul

    I have tried both methods, but I can not get it to work.

    When I synchronize I get an export to FIM with the input from the CSV or AVP but when i export to FIM there is no update.

    The problem is that I can not get my manager value (eg. Manager=xxxbbb) to translate into a MV resource ID which is the correct format for the manager reference in the MV (eg. manager={16E5E3C6-6E6C-E211-9733-005056A97892})  

    ?

    Per

    Monday, February 25, 2013 12:59 PM
  • When correctly applied the mv resource id will automatically set with the correct values.

    What is your setup? what information is within the file, do you have join rules in place do you see any updates when running a import on the csv/avp management agent?


    Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!

    Monday, February 25, 2013 1:17 PM
  • Hi Paul

    My csv contains the following :

    AccountName;Department;Manager;BD_homePhone
    xxxddd;BSY;xxxbbb;
    xxxggg;BIR;xxxaaa;+45 21455227
    xxxsss;BSY;xxxbbb;+45 61741318
    xxxeee;BIR;xxxaaa;

    Anchor is the accountname and I also join on accountname.

    In the import of the CSV file i get all 3 values into the CS. (as shown above)

    When I run the full sync on the CSV MA I get an outbound sync to FIM, where it updates the manager field with eg. xxxbbb

    But when I run an export in the FIM MA - no updates are done.

    I have a value in the manager field in my CSV connectorspace but in the manager field in the MV it is empty

    Monday, February 25, 2013 2:19 PM
  • Did you make sure the Manager field in de CSV MA is set to reference and the attribute flowing to the metaverse is also reference (and also in the FIM MA), do you have blue 'clickable' links in the metaverse then yes it should work, if not then the references are not set correctly.

    Can you show some screenshots from your configuration?


    Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!

    Monday, February 25, 2013 2:22 PM
  • Per,

    Make sure that you set the Manager attribute as a reference on the Property pages for your CSV MA. Also, make sure that you set the anchor on the MA to be the accountname. And make sure that the value of all Manager fields in the CSV has a value that references another record in the CSV.

    After that, you should be able to create a direct flow for your manager attribute

    CS:manager -> MV:manager

    and for your FIM MA

    MV:manager -> CS:manager

    Does the data go to the metaverse or is it only to the FIM portal that you have flow issues? Check precedence for the manager attribute if you have the data in the metaverse.

    Could you maybe post a snip from your CSV file and maybe a screenshot of the configuration of the MA?


    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt




    Monday, February 25, 2013 2:39 PM
  • The problem is that I can not get my manager value (eg. Manager=xxxbbb) to translate into a MV resource ID which is the correct format for the manager reference in the MV (eg. manager={16E5E3C6-6E6C-E211-9733-005056A97892})  

    Per, you don't need to translate it that way - this is what the sync engine does for you.

    What you need to do is to make sure that the references are tracked correctly in your data source – which could be the AVP file.

    Have you seen “Understanding Reference Attributes Processing in FIM” yet?
    The article might help to shed some light on it.
    One suggestion I have for you is to forget about your actual scenario for a moment.
    You can use just the inbound part from “HR” in the article I have referenced above to get a feeling for how references are processed.

    Cheers,
    Markus


    Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation


    Monday, February 25, 2013 8:39 PM
  • Here are screen dumps of the configuration

    Tuesday, February 26, 2013 7:49 AM
  • Tuesday, February 26, 2013 7:50 AM
  • And the import flow? Do you have a flow for Manager -> MV:manager ?

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, February 26, 2013 7:50 AM
  • Tuesday, February 26, 2013 7:50 AM
  • Tuesday, February 26, 2013 7:50 AM
  • Tuesday, February 26, 2013 7:51 AM
  • Tuesday, February 26, 2013 7:51 AM
  • Tuesday, February 26, 2013 7:51 AM
  • I do not get the manager data into the MV

    Content of the CSV file :

    AccountName;Department;Manager;BD_homePhone
    xxxddd;BSY;xxxbbb;
    xxxggg;BIR;xxxaaa;+45 21455227
    xxxsss;BSY;xxxbbb;+45 61741318
    xxxeee;BIR;xxxaaa;

    Tuesday, February 26, 2013 7:55 AM
  • After changing the configuration on the CSV MA, did you do a new Full Import and a Full Sync; sometimes it may even be necessary to clear the connector space and reimport to get the references in order after changing the schema.

    Also, you should be doing Import after any exports to confirm your exports.


    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, February 26, 2013 7:56 AM
  • Did you checked the precedence on the manager attribute, make sure it is set to equal or the CSV MA has higher precedence than any other MA that is importing manager, on one particular screenshot the metaverse shows empty.

    Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!

    Tuesday, February 26, 2013 7:57 AM
  • So the managers themselves are not objects in the CSV? If that is the case, you're in trouble as the referenced objects need to be in the same connector space. Otherwise, you'll have to flow the string/text value into the portal and do some lookups and updates there to turn it into a reference that you can flow to AD (if you have all objects in the FIM Portal/service).

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, February 26, 2013 7:58 AM
  • Soren is true, if you add a line in the csv that reads 

    xxxaaa;;;

    the references should be working (because xxxaaa will be joined to the correct mv object)


    Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!


    Tuesday, February 26, 2013 8:01 AM
  • And if you're unable to get the manager objects into the CSV, you could maybe be able to use my Lookup custom workflow to populate the manager reference in the portal

    https://fimactivitylibrary.codeplex.com/wikipage?title=Lookup%20Value&referringTitle=Documentation

    But thats a different thread :-)


    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, February 26, 2013 8:14 AM
  • Tried to add the following lines :

    xxxaaa;;;

    xxxbbb;;;

    But that just gave a sync error :

    Tuesday, February 26, 2013 8:42 AM
  • That sync error pertains to a different MA and should have nothing to do with the MA in question. Do a full sync and check the metaverse

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, February 26, 2013 8:46 AM
  • When i type in a manager on a user in the FIM portal the flow gets as follows :

    Tuesday, February 26, 2013 9:01 AM
  • Are you importing or exporting to the Portal? Looks like you're importing manager from the portal and that could be why you're not getting any exports to the portal. Also, check precedence for the manager attribute in the Metaverse Designer - is import priority correct there?

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, February 26, 2013 9:04 AM
  • The example was just to show how the attribute value looks when I update the manager field for a user in the FIM portal.

    I am trying to do the same from a CSV file so i do not have to type it in manual and for updating when changing (the change comes from another system)

    It seems to be the value of the field that is not right.

    Tuesday, February 26, 2013 9:25 AM
  • Okay.

    The best way to check this is to limit the scope. If you import both the employee and the manager from the CSV file, then you should have two objects in the metaverse and for the employee the value of the manager should be a clickable link that refers to the manager object. From you screenshot it could look like you don't have the manager's object in the metaverse? Try the following -

    1) On the CSV MA, make sure that the manager field is marked as a reference

    2) Make sure that you project a person object to the metaverse (after your join rule)

    3) Configure an import flow on the CSV MA for CS:Manager -> MV:manager

    4) Do a Full Import/Full Sync

    5) See that you get both objects into the metaverse

    6) Do a metaverse search and verify that the manager field of the employee is now a clickable link

    the CSV file should look something like this -

    AccountName;Manager
    xxaa;xxbb
    xxbb;xxcc
    xxcc;

    That should work as this is standard FIM functionality. Get that working and then move on to the portal export stuff later.


    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, February 26, 2013 9:36 AM
  • Did you manage to resolve this?

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Wednesday, February 27, 2013 10:01 PM