tag:blogger.com,1999:blog-8768186835369852617.post1032552011380076967..comments2024-03-19T00:20:36.503-07:00Comments on Life and Technology: Get out of the habit of using new ColumnSet(true); in your Dynamics CRM .NET CodeJamie Mileyhttp://www.blogger.com/profile/16109612970870135278noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8768186835369852617.post-71826618109085965382016-02-10T00:33:26.710-08:002016-02-10T00:33:26.710-08:00Hm, while that is of course true, I have learned (...Hm, while that is of course true, I have learned (painfully :D) early on that it's never a good idea to use the update call for a retrieved entity. I consider a best practice for myself to create a new object with just the fields I need updated.darksanderhttps://www.blogger.com/profile/00924142889717600729noreply@blogger.comtag:blogger.com,1999:blog-8768186835369852617.post-21989232904207085682016-02-08T08:56:50.738-08:002016-02-08T08:56:50.738-08:00Agreed... this is one of those situations for whic...Agreed... this is one of those situations for which I have been meaning to run SQL Profiler to view the impact. I would love to see the effect on the DB between choosing a few attribs vs * when you have custom indexes. <br />This can also make an impact on plugin Image registrations. Bringing back a plugin image with all attribs can have the same impact.<br />I am also uptight about registering for all attribute changes vs only those you care about... This does not seem to be a common issue with developers but its' definitely something to keep in mind!jim novakhttps://www.blogger.com/profile/02163338344959990227noreply@blogger.comtag:blogger.com,1999:blog-8768186835369852617.post-28389656221762318942016-02-07T08:51:50.657-08:002016-02-07T08:51:50.657-08:00well caught! me too lazy sometimes :) Yes performa...well caught! me too lazy sometimes :) Yes performance also goes slow in complex custom development.SAMAhttps://www.blogger.com/profile/11003504337130418293noreply@blogger.com