Home/ Questions/Q 6694657
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T06:07:38+00:00

I’m developing against MS CRM 2011. And I find out there are a lot

  • 0

I’m developing against MS CRM 2011. And I find out there are a lot of pain points including borderline broken, half arsed LINQ support.

That aside the latest one has to do with a lot of built-in fields that’s been hidden away, deprecated and/or unused as far as the user is concerned. However from developer’s perspective, we have no idea that these fields are deprecated. The context generated by crm util still generates these properties. So what ends up happening is that developers code against properties/relationship/entities that has been deprecated on a number of occassion.

So now the question is, is there a way to interrogate the crm services for a list of fields/properties that aren’t in any form for every entity? What more is there a way to interrogate the crm services for all unused entities (for lack of a better word). These could be entities that are orphaned, hasn’t been updated in a while and/or empty etc.

I hoping with such a list the developers will know what to look out for as opposed to coding blindly against the crm context, which has been a source of frustration.

Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Well I don’t think you’d want to just generate code for fields that are on forms – I use “hidden” fields for flags all the time.

    There is a way to make crmsvcutil generate only the entities you want:

    http://erikpool.blogspot.com/2011/03/filtering-generated-entities-with.html

    Sounds like you are a bit frustrated, but don’t give up quite yet. There are definitely architectural decisions that I question, but all of the plumbing that I don’t have to write makes up for it. Dynamics CRM is like any other technology, but I love it more than I hate it. 🙂

    • 0