Hi all, I need to add approximately 400 custom attributes to the metaverse object type "person". Is there any other way to add these attributes than clicking my self 400 times through the "Add Attribute to Object Type" window in the Metaverse Designer? I'm looking for something like a bulk import. The attribute names are currently stored in an excel sheet. Thank you for your support in advance Chris

Chris, as I understand it there is no supported mechanism for bulk schema update in the sync engine. If you build the schema once in a development environment, you can then use the schema import/export capability to build subsequent environments. Cheers,Tom Houston, HP Enterprise Services - UK Identity Management Practice

I dont see a proper option here as well. Maybe you could utilize AutoIT to support your approach. Regards, Moritz

400 is quite a large number of custom attributes. Perhaps if you give us an idea what those attributes are for, we might have ideas how to accomplish the same result with less. Without knowing the scenario, it's not impossible to know for sure, but people on here love a challenge :)Frank C. Drewes III - Consultant: Certified Security Solutions - My blog: http://www.css-security.com/author/fdrewes

400 is quite a large number of custom attributes. Perhaps if you give us an idea what those attributes are for, we might have ideas how to accomplish the same result with less. Without knowing the scenario, it's not impossible to know for sure, but people on here love a challenge :) Frank C. Drewes III - Consultant: Certified Security Solutions - My blog: http://www.css-security.com/author/fdrewes I need to synchronize nearly every attribute of a AD user object. That is why I need to add about 400 attribute to the MV person object. Did anyone try to have that amount of import and export flows (about 800 over all) configured in the sync engine? Thanks Chris

When you set this up I would thoroughly recommend you first COPY the default MV.person to a new object class (say myPerson) and then extend that. Frank is right though - this is a very curious scenario, as 400 is way more than normal. What do you wish to synchronize ALL of these attributes to if you don't mind me asking? I've worked with many sync projects, but the biggest metaverse attribute collection would have been less than 50 in even the largest of them. This number of attributes sounds like a performance problem waiting to happen ...Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

As I wrote here http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/0c6501ff-8807-4817-97f9-2dfb4e3571b2 this is necessary in a migration project where the migration solution can not synchronize the attributes.

You can always export a simple MV schema to a XML file (with sample data types you need), look at the structure, do your magic, and import it. Of course you would have to ignore the: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! !! The contents of this file should not be edited. !! Any such modifications to this file may result in errors during import. !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! But it should do the trick if you do it right :) Piotr

Thanks for that. I've done it that way. But I would not recommend doing it. It was a bit of a hazle to get the XML schema right.

Hi Bob, we came down to about 200 attributes without any performance problems at all. FIM is working as expected. Best regards Christian

Good to hear. I prefer to work with a normalised schematic though and I'm thinking that your user object must be highly denormalised to have that many atts. If you are storing say department Id and department location details on the user object for instance then that can lead to a lot of data duplication and reliance on string value set filters when FIM really wants to work with references. See my technet wiki article on this to see what I mean ... there are pros and cons to either approach.Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine