http://blogs.msdn.com/mikemill/archive/2006/02/14/532121.aspxIt was interesting to see Mitch Milam's post about the metadata browser. This was a little tool I put together pre-V1.0 ship, but which didn't make the schedule until V3. Mitch points out the "published" component which displays the entity metadata inen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/mikemill/archive/2006/02/14/532121.aspx#534194Fri, 17 Feb 2006 20:20:01 GMT91d46819-8472-40ad-a661-2c78acb4018c:534194Inside MS-CRMIt's stuck in LegalLand right now. It's not really Legal's fault either. When I put the original prototype...http://blogs.msdn.com/mikemill/archive/2006/02/14/532121.aspx#534748Sat, 18 Feb 2006 18:39:55 GMT91d46819-8472-40ad-a661-2c78acb4018c:534748mitchmMJ, <br> <br>That was you? &nbsp;Cool. &nbsp;It really is a neat tool and I have been using it regularly. <br> <br>Feature Request: <br>If you could add the display name to the Attribute matrix, that would make my life a bit easier. <br> <br>I have noticed that I sometimes end up changing the Attribute's display name after creation to match better with existing business process rules and it would be nice to have both values listed so I know exactly what is what. <br> <br>Thanks, Mitchhttp://blogs.msdn.com/mikemill/archive/2006/02/14/532121.aspx#536387Wed, 22 Feb 2006 01:17:42 GMT91d46819-8472-40ad-a661-2c78acb4018c:536387mikemillWould you believe it was written as a dev tool before we started 1.0 development? Would you believe that a static version of it shipped in the 1.0 SDK as well? <br> <br>I need to go dig into the MD cache's XML again to see if the display name is there. I think that's why I didn't add it to the list in the first place. If it's there I'll post a message about how to add it (hint: there's an XSL that generates the list, the entity definition, and the XSD).http://blogs.msdn.com/mikemill/archive/2006/02/14/532121.aspx#538242Fri, 24 Feb 2006 02:14:48 GMT91d46819-8472-40ad-a661-2c78acb4018c:538242mikemillTurns out the as-shipped metadata cache that the MD browser uses for its source XML doesn't include the display name. I might have a fix for that... actually you can think of it as a re-implementation of the browser. I've got the basics of a reasonable public MD cache in place, I just need to retarget the MD browser to use it (or to inject the display name values on the fly). <br> <br>It's interesting that the attribute description is in the serialized metadata, but not the display name. Hmm...http://blogs.msdn.com/mikemill/archive/2006/02/14/532121.aspx#1742252Thu, 22 Feb 2007 18:35:50 GMT91d46819-8472-40ad-a661-2c78acb4018c:1742252Microsoft Dynamics CRM Team Blog<p>There is a little known feature in CRM 3.0 called the Metadata Browser. You can find this feature by</p> http://blogs.msdn.com/mikemill/archive/2006/02/14/532121.aspx#1742260Thu, 22 Feb 2007 18:38:27 GMT91d46819-8472-40ad-a661-2c78acb4018c:1742260Microsoft Dynamics CRM Team Blog<p>There is a little known feature in CRM 3.0 called the Metadata Browser. You can find this feature by</p>