This statement holds true whether you are updating attributes through the SDK dlls or over web services. It doesn’t matter whether you’re coding for a plugin, workflow assembly, Silverlight app or some external custom application like a windows application or web application. The potential outcome in all the scenarios will be the same! What’s the outcome? Triggering other automation unwantedly!
Hopefully its not recalled as soon as it has be released like rollup 6. If your interested in working with the latest SDK you can download it here. The only release notes I’ve been able to find are the ones provided by Mitch Milans. They can be found here. Everything seems to be legit so […]
While creating a plugin today I wanted to compare attribute values from a pre image with attribute values from the input parameters. Typically I always use the == and != operators for comparison. This generally works fine for the .NET base value types but for the CRM reference types of OptionSetValue, Money and EntityReference it caused me an issue. I wasn’t getting expected results back!