none
Convert Attribute Value Types RRS feed

  • Question

  • We're planning to manage groups in an LDAP data source with the LDAP MA. These groups have an attribute 'uniqueMember' that holds its members. The LDAP MA detects this as a String, so we'll need to convert it to a Reference during import using a MA rules extension and the MapAttributesForImport method. The issue we're seeing is when we attempt to configure advanced attribute flow mappings in the LDAP MA "Defining a rules extension import attribute flow to a metaverse reference attribute is not allowed". Have I misunderstood something here?

    Tom Houston, UK Identity Management Practice

    Thursday, February 19, 2015 8:37 PM

Answers

  • No, you just cannot convert any value from source to reference in metaverse.

    As a workaround, create an SQL agent to export users to any table and build a view, where you can import a reference value.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    • Marked as answer by Thomas Houston Friday, February 20, 2015 4:15 PM
    Thursday, February 19, 2015 9:34 PM
  • Hi,

    I'm sure this is only related to non-reference attributes, things like multi-value to single-value (non-ref) or integer to string values and maybe datetime formats.

    There is no possibility to have advanced attribute flows on reference attributes in the product since it was released as MIIS in 2003 (and MMS before that of course).

    So you have to work around this behavior with things like Dominiks SQL solution or writing your own MA maybe.

    -Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    • Marked as answer by Thomas Houston Friday, February 20, 2015 4:15 PM
    Friday, February 20, 2015 4:02 PM

All replies

  • No, you just cannot convert any value from source to reference in metaverse.

    As a workaround, create an SQL agent to export users to any table and build a view, where you can import a reference value.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    • Marked as answer by Thomas Houston Friday, February 20, 2015 4:15 PM
    Thursday, February 19, 2015 9:34 PM
  • Thanks Dominik,

    No, you just cannot convert any value from source to reference in metaverse.

    Do you know what this MSDN article is referring to, suggesting that converting from String data types to Reference data types is supported using CreateDN?

    Cheers,


    Tom Houston, UK Identity Management Practice

    Friday, February 20, 2015 7:12 AM
  • Hello,

    this method does not help you, since as you state in your question you can not set values to reference attribues with an advanced flow.

    If I remember correctly the mentioned method is for creating a DN to use in provisioning.

    -Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Friday, February 20, 2015 9:41 AM
  • Reference attribute can only work when you can define them as such in the connector space, which LDAP agent is this? a custom build LDAP agent or the one from FIM?

    FIM does not allow to configure Reference attribute in import/export flows when you are targeting a non reference attribute, Peters option is an alternative to get this working



    Need realtime FIM synchronization and advanced reporting? check out the new IM Sequencer 6.0 at http://www.imsequencer.com, it supports FIM 2010 R2, Omada Identity Manager, SQL, File, AD, FTP or Powershell real time synchronization!


    Friday, February 20, 2015 2:12 PM
  • Cheers both,

    Reference attribute can only work when you can define them as such in the connector space, which LDAP agent is this? a custom build LDAP agent or the one from FIM?

    It's the out of box Generic LDAP Connector. The article referenced above states:

    When you import objects from a connected system to the FIM Synchronisation Service database (metaverse), the imported objects might have attribute values that are of a data type that you must convert to a different data type to be compatible with other objects in the metaverse. You can use a rules extension to convert the type of the attribute when it is imported into the metaverse.

    I'm a bit confused because this article suggests it's possible.

    Tom Houston, UK Identity Management Practice

    Friday, February 20, 2015 3:52 PM
  • Hi,

    I'm sure this is only related to non-reference attributes, things like multi-value to single-value (non-ref) or integer to string values and maybe datetime formats.

    There is no possibility to have advanced attribute flows on reference attributes in the product since it was released as MIIS in 2003 (and MMS before that of course).

    So you have to work around this behavior with things like Dominiks SQL solution or writing your own MA maybe.

    -Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    • Marked as answer by Thomas Houston Friday, February 20, 2015 4:15 PM
    Friday, February 20, 2015 4:02 PM
  • Ok no probs, thanks for clarifying this guys.

    Cheers,

    Tom Houston, UK Identity Management Practice

    Friday, February 20, 2015 4:06 PM