Passing Multiple values to a multivalue attribute in a Synchronization Rule RRS feed

  • Question

  • Hi Guys

    I have a scenario where i need to pass some default values to a multivalued attribute, how can I pass multiple values to a multivalued attribute in an outbound Synchronization Rule?

    Regards Furqan Asghar

    Sunday, February 10, 2013 11:04 AM


All replies

  • As far as I'm aware, you can't actually do this via Portal-configured Sync Rules.

    You'll need to configure a rules extension in the FIM Sync Service within the MA Configuration | MCTS: FIM 2010

    Monday, February 11, 2013 6:27 AM
  • Thanks a lot Ross

    I thought so too, but then I was hoping that I was wrong and there MUST be some way around this you folks might have used.

    So rules extension it is then, eh!

    Regards Furqan Asghar

    Monday, February 11, 2013 8:04 AM
  • I've never done it, but I mainly use the Sync Service for my flows anyway.. gave it a quick shot in a dev environment and couldn't see how. This post from Henrik back in 2010 says it can't be done:

    It may have changed since then in an update/release, but I doubt it.

    - Ross Currie | MCTS: FIM 2010

    • Proposed as answer by Ross Currie Monday, February 11, 2013 8:34 AM
    • Marked as answer by Furqan Asghar Monday, February 11, 2013 8:59 AM
    Monday, February 11, 2013 8:34 AM
  • But isnt a multivalue just an array of values?

    In any case we cant use sync rules to manage the FIM MA.

    If we build an array of telephonenumbers and store it it in Portal OfficePhone attribute.

    flowing attribute OfficePhone -> MV -> ADMA telephoneNumber will flow all elements of the array in the SyncRule... I would HOPE!

    Monday, February 11, 2013 9:09 AM
  • Ah Harold

    Actually i need an initial flow to a Multivalued attribute, like Roles. the initial values depend on the Employees Grade, so for each employee grade i would flow the default roles.

    As a work around this problem i now have to pass a string of roles sperated by some sort of delimeter and then convert it to multivalues in my advanced export flows.

    or may be create a custom activity to get these values into a multivalued attribute in the workflowdata and then pass that workflow attribute into the sync rule as a parameter.

    I hope the latter works, as i am going to try that first.

    Regards Furqan Asghar

    Monday, February 11, 2013 1:44 PM
  • Failing a workflowdata attribute working, you could always store it in a local attribute in the FIM Portal schema, then flow that.

    If you could write custom functions, you could write a custom function that could do it. Too bad you can't write custom functions

    But this is a perfect example of why I don't use the FIM Portal to do my EAF/IAFs. Having to write a custom workflow activity just to flow a multivalue attribute is severe overkill imo.

    - Ross Currie | MCTS: FIM 2010

    Tuesday, February 12, 2013 1:42 AM