From the Microsoft Dynamics CRM Blogs: Fixing status reasons; Option set labels via OData + Power Query; CRM 2013 Load Balancing; Early v. late binding performance

From the Microsoft Dynamics CRM Blogs:

• Fix Incorrectly Created Status Reasons in Dynamics CRM;
• Access Option Set Labels in Dynamics CRM OData Feeds via Power Query;
• Microsoft Dynamics CRM 2013 Load Balancing;
• Early Binding vs Late Binding Performance (Revisited)

Fix Incorrectly Created Status Reasons in Dynamics CRM

On the Magnetism blog, Roshan Mehta explains that the Status Reason field in Dynamics CRM is a special field that allows you to provide reasons for the status of a particular record. For example, an article can have a Status of "Active" and a Status Reason of "Awaiting Review," "Approved," "Published," etc. Likewise, an Article can have a Status of "Inactive" and a Status Reason of "Expired" or "Deleted." But, Mehta asks, what happens if you configure your Status Reasons incorrectly?

"I had recently made a mistake while configuring the Status Reason field such that a user could set an Article to Active - Deleted, which was not the desired functionality. The "Deleted" status reason should instead be linked to the "Inactive" state."

You can find out what Mehta did by reading the rest of the post here:

Access Option Set Labels in Dynamics CRM OData Feeds via Power Query

On his Surviving CRM blog, Jukka Niiranen says if you're using Dynamics CRM Online without direct access to the underlying SQL Server database, you might have wished for more flexible options ...