Dynamics CRM Usergroup Sydney Returns!

The Sydney CRM usergroup was reopened last night(Microsoft building, North Ryde). Organised by Catherine Eibner and Guy Riddle, the event will be held every 4th Tuesday of every month.

This has been a long anticipated step forward for the Sydney CRM users and consultants and a great place to meet people in your field of business.

This month's discussions were over the newly release CRM Accelerators (presented by Guy), with detailed discussions on Notifications, eService and Events Management. The remaining Accelerators will be discussed next month.

Visit www.mscrm.com.au for more information and upcoming meeting event dates.

No need to retrieve entity in order to update attribute values

Scenario:

We have an existing account with a known GUID and would like to update their phone number.

Solution:

Common sense and traditional logic would often suggest to first open the specific account record, make modifications to all specific attributes, followed by update and close the entity:

ColumnSet cols = new ColumnSet();
cols.AddColumn("telephone1");
account myAccount = new account();
myAccount = oService.Retrieve(EntityName.account.ToString(), myAccountID, cols) as myAccount;
myAccount.telephone1 = "02 1234 1234";
oService.Update(myAccount);

The above code, though it works, contains a number of entirely unnecessary steps. For a far more efficient code block, see the following with an identical outcome:

account myAccount = new account();
myAccount.accountid = myAccountID;
myAccount.telephone1 = "02 1234 1234";
oService.Update(myAccount);

Note that there is no need to retrieve the targeted record before making modifications. As long as we set the entity ID to an existing GUID, the CRM SDK will take care of the rest. The stored value in the "telephone1" attribute will be replaced with the new value for the specified account GUID "myAccountID".