locked
Outbound System Scoping Filter not working with multi-valued attribute? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    Using FIM 2010 R2 SP1 (4.1.3441.0)

    Hi,

    I am trying to get an Outbound Sync Rule applied using Outbound System Scoping Filters. For that, I am evaluating a multi-value string attribute using the "contains" operator. FIM lets me do that, and on import/sync the rule shows up in the metaverse; however, the rule does not get applied to the intended objects as expected.

    When I modify the filter to use a single-valued string attribute, the rule does apply.

    I cannot find any restriction in the documentation on using multi-valued attributes. Has anyone run into this before (and solved it)?

    Thanks

    Chris

    Thursday, May 16, 2013 7:58 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    That is not supposed to work. The scoping filter is only intended for string values. It isn't documented because I didn't think of documenting it.

    What is the scenario where you need to operate on a multi-valued field?

    /Andreas

    • Marked as answer by Chris_Hh Thursday, May 16, 2013 4:14 PM
    Thursday, May 16, 2013 3:50 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Chris-

    I'd give PSS a call and have them look in to this.

    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com

    Thursday, May 16, 2013 2:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That is not supposed to work. The scoping filter is only intended for string values. It isn't documented because I didn't think of documenting it.

    What is the scenario where you need to operate on a multi-valued field?

    /Andreas

    • Marked as answer by Chris_Hh Thursday, May 16, 2013 4:14 PM
    Thursday, May 16, 2013 3:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Andreas, thanks for the clarification. The scenario uses a multi-valued attribute eduPersonEntitlement, which holds multiple string values (usually URN's) as entitlements to external systems or in external systems (through ADFS claim transforms). Using this attribute in a scoping filter seemed a logical and elegant method to me. However, I can still reach the same objective using set transitions/MPRs/workflows.

    Thursday, May 16, 2013 4:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Brian,

    Given Andreas' explanation I think PSS will not be able to help. Thanks anyway.

    Chris

    Friday, May 17, 2013 9:52 AM