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.
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,
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
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
Cheers both,
It's the out of box Generic LDAP Connector. The article referenced above states: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?
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.
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
Cheers,