none
Unique value on the export in C# RRS feed

  • Question

  • Hi all

    I'm wanting to export a value to the CS which I want to be unique.

    I've read a few pages regarding how this can be done using custom worksflows etc, but I'm wanting to do the comparison this based on what's in the CS rather than FIM/MV, as there's more objects (unrelated to FIM) in there that may already have this generated value.

    I originally found the MV class utils.findmventries:

    https://msdn.microsoft.com/en-us/library/windows/desktop/ms698827%28v=vs.85%29.aspx

    I'm wondering if there's something just like this but for the CS or is there a better way?


    • Edited by jontelling Thursday, May 14, 2015 7:37 PM
    Thursday, May 14, 2015 4:05 PM

All replies

  • Workflow is useful when you want to perform a uniqueness check in a connected data source, but it can't be used to perform a uniqueness check in a connector space. Might be worth having a look at the IMVSynchronization.Provision() method to see if there's something you can do in there prior to creating a new connector.

    Tom Houston, UK Identity Management Practice

    Thursday, May 14, 2015 5:50 PM
  • As Thomas said, this need to be done in the Classical rules extension. The sample you present is used to query the Metaverse. 

    I don't remember the syntax, but it is something like this

    connectorspace["MA_NAME"].contains("NAME OF OBJECT")


    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Nosh Mernacaj Thursday, May 28, 2015 6:52 PM
    Thursday, May 14, 2015 6:29 PM
  • Thank you for your replies.

    I'll have a read and see what I can come up with. 

    Sorry if I wasn't too clear (I was passing the time while in a meeting, hehe).
    I'm more than happy to build this in the classical way (I find coding the sync rules a better option anyway).

    I'll be back, :)

    Edit, to add, the CS doesn't have anything to join on, as everything from FIM is new, it's a case of old and new living in the same area, we did it in reverse of the normal as it's a brand new CS. Fim provisions first followed by old data. :)

    • Edited by jontelling Thursday, May 14, 2015 7:44 PM
    Thursday, May 14, 2015 7:40 PM
  • You cannot access connectorspace libraries from Portal Workflow, so not even a choice.

    This can only run on Provisioning DLL or Extension Rules.


    Nosh Mernacaj, Identity Management Specialist

    Thursday, May 14, 2015 7:42 PM
  • I understand that, sorry if I gave you the impression I wanted to run this in the portal as a workflow as I don't.

    Edit, it's looking more or less as though this is a provisioning rule only, as from my understanding when the sync starts only the single CS object is loaded, rather that than the other way around (I originally thought the MV was loaded and CS iterated rather than the CS loaded and the MV iterated).


    • Edited by jontelling Thursday, May 14, 2015 9:27 PM
    Thursday, May 14, 2015 8:37 PM
  • I guess we are on the same page then.

    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Nosh Mernacaj Thursday, May 28, 2015 6:39 PM
    Thursday, May 14, 2015 8:58 PM