Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
reference attribute - externalsource to metavearse

Answered reference attribute - externalsource to metavearse

  • Friday, February 15, 2013 4:23 PM
     
     
    Sign In to Vote
    0

    I have a delimited text file and I am trying to change the reference attribute in metaverse through ISR.

    Should my input file has the value or the resourceid of the reference object? In both the cases, what should be the datatype of the input attribute?

    Thanks,



    • Edited by fim_sc Friday, February 15, 2013 4:24 PM
    • Edited by fim_sc Friday, February 15, 2013 4:24 PM
    •  
     

All Replies

  • Friday, February 15, 2013 7:24 PM
     
     Answered
    Sign In to Vote
    0
    On your MA, change type of attribute to Reference - and the value of the reference attribute should point to another record with the anchor/id of the reference attribute. Type should be the same as the anchor attribute

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

    • Proposed As Answer by Ross Currie Tuesday, February 19, 2013 4:40 AM
    • Marked As Answer by fim_sc Tuesday, February 19, 2013 2:24 PM
    •  
     
  • Tuesday, February 19, 2013 4:51 AM
     
     
    Sign In to Vote
    0

    Søren is spot on. The reference is determined in the Connector Space and then maintained as it is flowed in to the Metaverse and out to any end systems.

    Your CS might look something like this:

    EmpID, Name, Manager
    001,Bil,
    002,Joe,001

    Make Manager a reference type in the MA config, then flow it directly to a reference type in the Metaverse.

    Note that for this to work, the referenced object must also join/project to the Metaverse. Eg, if 001 was a disconnector for some reason, no value would flow to the Manager attribute in the MV as the reference would not be resolved.

    I find this is particularly useful in group management scenarios where a role may have a user reference but that user doesn't meet your criteria for MV projection/joining (there will be no MV reference to map to), or where the user object does not appear in the connector space (no reference will be made in the connector space).

    - Ross Currie

     

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