Hello, I was working in our dev instance and upon creating a new Metaverse attribute, I received the error "The specified metaverse schema has too many attributes." It appears that we have 454 attributes. Can anyone confirm that this is the maximum number of metaverse attributes? Thanks, Greg

I can't confirm on maximum number of attributes in Metaverse - this will have to be confirmed by someone from product team. But looking at how Metaverse is implemented I think that the problem you are hitting is that your metaverse object, based on its schema is getting bigger then single page in SQL database.

Hey Greg, I'm with Tomasz on not knowing how many attributes are supported, but at the same time I have not ever run into this issue. Can you give a quick background on what you are trying to do that requires you to have so many MV attributes? It could be an interesting business case or we might be able to suggest a different approach? AAlmero Steyn (http://www.puttyq.com) [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or "Helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

I would be quite surprised if FIM / ILM is sensitive to fragmenting a row over multiple pages... nothing in SQL Server prevents ordinary row data from exceeding 8KB, and SQL Server will tolerate *many* more columns than this in a single regular table. My suspicion is that FIM contains an artificial limitation of ~500 metaverse attributes, with the difference between 454 and 500 being made up with system attributes. I've never run up against this limit in FIM because no client of mine has asked for such a huge number of attributes. I wonder if someone is trying to pump the entire contents of their HRMS through...