none
Classic Rule Extension: can a single attribute import flow modify multiple metaverse objects? RRS feed

  • Question

  • I'm importing groups from an external source using two tables, one containing department and person objects and another defining which people are a member of which groups (each person is only a member of one group)

    The groups are fine, the MA successfully creates "Departments" in the metaverse, with person objects linked in as members, but what I would like to do now is take the department description and place it into the user's "department" attribute.

    Is it possible to use a single import flow to make changes to multiple metaverse objects?  If so, how?

    Cheers,

          Ian


    Monday, November 9, 2015 3:03 PM

All replies

  • Absolutely.

    And it is more times then not that this is the case.

    I am not sure how the question relates to your summary of what you have done so far, but I leave that to you.

    How? Simple import flow.  FirstName --> FirsName, FirstName --> GivenName.  This is a simple example.


    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Nosh Mernacaj Monday, November 9, 2015 4:02 PM
    Monday, November 9, 2015 4:02 PM
  • I understand how you can have a single connector space attribute mapped to multiple attributes on a single metaverse object.  What I'm less clear on is how I can take a single attribute and map it to attributes on different target metaverse objects.

    Eg.  CS.Group.description -> MV.Group.Description

     -> MV.Person.Department

    Cheers,

       Ian

    Monday, November 9, 2015 5:45 PM
  • Ian,

    I believe you need 2 MAs for that, But I am still not clear what the goal is and what the data source looks like.

    If you are trying to automate Group membership in this MA, you need something more then what you are asking for.


    Nosh Mernacaj, Identity Management Specialist

    Monday, November 9, 2015 7:38 PM
  • I understand how you can have a single connector space attribute mapped to multiple attributes on a single metaverse object.  What I'm less clear on is how I can take a single attribute and map it to attributes on different target metaverse objects.

    Eg.  CS.Group.description -> MV.Group.Description

     -> MV.Person.Department

    Cheers,

       Ian


    There isn't an easy way to do this in the sync engine. What you might look at is changing your User table to a view and calculating it in SQL. This way you'll have an easy attribute flow coming in to the Sync Engine.

    Thanks,
    Brian

    Consulting | Blog | AD Book

    Tuesday, November 10, 2015 2:02 PM
    Moderator