From the Microsoft Dynamics CRM/365 Blogs: Option sets; Autonumber; Relevance Search; License required?

From this week's Microsoft Dynamics CRM/D365 blogs:

• Dynamics 365 (v9): Multi Select Option Sets, C#, and SDK Versioning
• Dynamics 365 v9.0 Hidden Gems - #1 Autonumber
• A Quick Overview of Relevance Search in Microsoft Dynamics 365
• License Required to Install and Upgrade Solutions

Dynamics 365 (v9): Multi Select Option Sets, C#, and SDK Versioning

On his It Ain't Boring: Exploring Dynamics 365 blog, Alex Shlega wrote that currently there is not an SDK for Dynamics CRM v9.

However, he wanted to see how far he could get with the Multi Select Option Sets, and if he could work with them on the .NET side. He wrote that was the only remaining question in his previous post, Dynamics 365 (v9): Multi Select Option Set.

Shlega discovered that you could do it with the v8 SDK, even though it's a little more complicated than usual. He added that the Dynamics web service turned out to be "smarter" than he originally thought it was:

To some extent (I don't know exactly to what extent), it's backward compatible, and that kind of compatibility is built around the SdkClientVersion parameter that's included into the requests.

You can read the rest of Shlega's post here.

Dynamics 365 v9.0 Hidden Gems - #1 Autonumber

On his Work and Study Book - Dynamics 365 (CRM) Blog, Andre Margono wrote that there are a few hidden gems in the Dynamics 365 v9 update that could really prove useful in Dynamics 365 projects.