none
Skip this RRS feed

All replies

  • Tony-

    The method will only be called if your first join rule isn't satisfied on a disconnector that is being synchronized. You can run a preview on a disconnector to test this.


    Thanks,
    Brian

    Consulting | Blog | AD Book

    Monday, August 20, 2018 12:35 PM
    Moderator
  • Skip


    • Edited by TojoTojo Tuesday, September 25, 2018 12:33 PM
    Monday, August 20, 2018 12:46 PM
  • Once the connector is linked to a metaverse object, there will never be a join for it again. 

    Thanks,
    Brian

    Consulting | Blog | AD Book

    Monday, August 20, 2018 12:48 PM
    Moderator
  • Skip

    • Edited by TojoTojo Tuesday, September 25, 2018 12:32 PM
    Monday, August 20, 2018 12:53 PM
  • Join rules will only be evaluated when a disconnector is synchronized. Once that disconnector has been joined/projected to a metaverse object (and thus is now a connector), there will never be an evaluation of join rules for that connector. 

    Thanks,
    Brian

    Consulting | Blog | AD Book

    Monday, August 20, 2018 12:54 PM
    Moderator
  • Skip

    • Edited by TojoTojo Tuesday, September 25, 2018 12:32 PM
    Monday, August 20, 2018 1:09 PM
  • MapAttributesForJoin will fire if and only if the following are all true:

    1. The object is a normal disconnector.  As Brian has already mentioned, if the object is already a connector then it will not go through rejoin.  If the connector space object is an explicit disconnector you will not go through synchronization either (will not attempt join, project, provision).  You can determine if a connector space object is an explicit connector by searching the connector space for the object and seeing if explicit = true and connector = false

    2. The object being synchronized is the same object type as specified in the Join rules extension.

    3. The name in the join rule condition matches the same name in the rules extension.

    4. The value for the attribute being used for the join exists, that is, the value on the join attribute is not NULL.

    Also note that when using MapAttributesForJoin the join values are case sensitive, whereas doing a direct join without using a rules extension it is case insensitive.

    Hope that helps.

    Best,

    Jeff Ingalls

    Tuesday, August 28, 2018 1:30 AM