You are developing a custom application that integrates Microsoft Business Solutions CRM Accounts with another system. The functional requirements state that the post-callout must update the account with an account number from the other system. Your application will use a dedicated user account to perform the update. While testing your post-callout you notice that it has entered an infinite loop. Which answer best describes the steps to take to resolve this problem?
Store the account GUID in a class variable. Test for the same GUID on subsequent PostUpdate events. If they match, do not update the account.
Use Thread-Local-Storage to store the account GUID. Test for the same GUID on subsequent PostUpdate events. If they match, do not update the account.
Test to see if the modified by field in the XML string passed to the PostUpdate event equals the dedicated user account used by your application.. If they are the same, do not update the account.
Set the TransactionComplete parameter of the PostUpdate event to true when updating the account number in your post-callout.
Want to practice for MB2-228 - Microsoft CRM 1.2 Extending Microsoft CRM with .NET ?