Home > General

Everybody loves to use InfoPath forms. And let’s face it, we all wish we could just take them and put them into CRM. This post delves into how I integrated InfoPath & CRM to dynamically allow InfoPath forms received by email into CRM records. It is still under development, but the source code has been partially tested and works.

Click to continue reading
Click Here To View Post With Syntax Highlighting

CRM Activity Feeds are here! They are great. Microblog away.

Click to continue reading
Click Here To View Post With Syntax Highlighting

Searching for appointments using the SOAP Web-Service from Silverlight can be tricky if you don’t know to initialize the empty collections. Once their initialized, scheduling is a breeze.

Click to continue reading
Click Here To View Post With Syntax Highlighting

I get a lot of questions about what is a supported change or what is an unsupported change. Dynamics CRM is an extremely customizable system and provides tools to facilitate customization. So just what is supported or unsupported?

Click to continue reading
Click Here To View Post With Syntax Highlighting

Recently I needed to create some AD users for my CRM demo environment, and since I hate doing tedious repetative tasks I ended up using a powershell script. I thought I would share the script so that other people doing demos don’t create users 1 by 1.

Click to continue reading
Click Here To View Post With Syntax Highlighting

This afternoon I was at the Microsoft Dynamics CRM booth at Convergence when someone asked me about required fields in CRM 2011. They wanted to know how to make fields required, but have different forms with different required fields for the same entity.

First, in CRM 2011, when you make a field required by editing the field, you are making it required for all forms.

If you want to make a field required just for a particular form, you can use a form onload event to change the requirement level. One of the great things about CRM 2011 is just how much is exposed to JScript through Xrm.Page. There are methods on the attribute to get the required level and set the required level. Let’s suppose for example that we want to make the First Name required, but only on this form, then we could use the following onload function with the parameters ‘required’, ‘firstname’ to make the field required. If we needed to add multiple fields, then we would just specify them after ‘firstname’, such as ‘required’,'firstname’,'address1_city’.

function updateRequirementLevel()
{
    var level = arguments[0];
    for (var i=1; i < arguments.length; i++)
    {
        var attribute = Xrm.Page.data.entity.attributes.get(arguments[i]);
        attribute.setRequiredLevel(level);
    }
}

That will make each field you specify after the level, required or recommended based on the level you pass as the first parameter. Calling the function updateRequirementLevel('required','firstname'); will make the firstname required.

Click Here To View Post With Syntax Highlighting

Unfortunately, CRM does not currently support adding the queue to a case advanced find. However, that doesn’t mean it can’t be done. Follow the steps in this article to modify your fetchXML and your layoutXML to have the queue name show up in the advanced find.

Click to continue reading
Click Here To View Post With Syntax Highlighting

Just in case you need to get the id of an element in CRM and you are new to CRM development or IE development, the IE developer toolbar is great tool and huge help. You can check out this video on how to access it and hopefully it is enough of a teaser to convince you to start using it and play with it.

Click to continue reading
Click Here To View Post With Syntax Highlighting

Here is a video tutorial of how to take a case advanced find, edit the query, troubleshoot errors in SQL Management Studio, and update your excel query.

Click to continue reading
Click Here To View Post With Syntax Highlighting

© 2011 MSCRM Blogger

This site does not necessarily represent the views of Microsoft. The material posted on this blog are provided AS-IS, and you are to use the content at your own risk. Some of the code and information on this site may use unsupported methods. If you experience any problems using the information provided through this website, please post a comment and we will do our best to assist you, however, we can in no way guarantee support or resolution.

Microsoft Dynamics®, Silverlight®, Visual Studio®, and the corresponding logos are a registered trademarks owned by Microsoft Corporation. MSCRM Blogger has made every effort to supply trademark information about company names, products, and services mentioned on this blog. All third party trademarks are the property of their respective owners. Any rights not expressly granted herein are reserved.