I am looking for a good way to store constants and their values which are not necessarily attibutes on the user object. These are mostly parameters that I use in my custom expressions in function evaluator activities in the workflows or in sync rules. As an example, to determine and map a person's AD account domain from AD to FIM, the following expression is used - IIF(Eq(Left(ConvertSidToString(objectSid),Len_SID_1),"S-1-X-XX-XXXXXXXXXX-XXXXXXXXX-XXXXXXXXXX"),"DOMAIN_PARTITION_1", IIF(Eq(Left(ConvertSidToString(objectSid),Len_SID_2),"S-1-Y-YY-YYYYYYYYYYY-YYYYYYYYYY-YYYYYYYYYY"),"DOMAIN_PARTITION_2",...... and so on I want to be able to store these Len_SID_1, S-1-X-XX-XXXXXXXXXX-XXXXXXXXX-XXXXXXXXXX, DOMAIN_PARTITION_1 values as constants rather than hardcoding the complete data in custom expressions, sync rules etc each time in each environment (prod and non-production). For this particular example, I would have liked to store S-1-* information conatined in domain configuration information and I can't (unless I use description field). What is then the general recommendation for managing these types of data in FIM? Thanks. Anu

Bump, This is an excellent question and I am interested in what others have done to solve this problem. -Jeremy

I ended up creating Constant Specifier (but this needs association still to User and an Attribute of User). It was not exactly what I wanted but it came close. There must be a better way to doing this still. Anu

Bump, anyone has another solution for this, I'm also searching for a solution to store such value, which are best different in all Stages (Dev, Test, Prod) and will not be deployed by the FIM-Powershell deployment scripts. In old code extensions we use xml files to store such value (DN suffixes for LDAP and other things for example) How will / can i do this in FIM ? thx, Peter