Like CRM version info, this also shows up in Jewel Ribbon (as shown in following Screenshot)

Clicking on “Custom App Version Info” will show up window with Version Information in it

Information shown in Pop-up window in dynamically read from XML based Web Resource.

Here is how to do it.

1. Import unmanaged solution available here ShowAppVersion_1_0_0_0_ForShipping.zip
2. Export a Solution with Application Ribbon in it.
3. Extract customization.xml file from exported .zip solution.
4. Find RibbonDiffXml element in customization.xml file
5. Paste following XML string under <CustomActions> tag

1. Zip solution file and import it in CRM.

For changing content of Version Info, edit versioninfo_/XML/AppVersion.xml file

General practice can be adding versioninfo_/XML/AppVersion.xml file, every time there is new export created for deployment.

Hope this utility is some way helpful to you.

By configuring Security Roles we can disable these buttons from certain Users.

In Security Role, Entity Process should be configured to revoke read permissions

However in some cases we wanted to completely hide these buttons along with its Group. CRM does not hide the buttons even if we revoke Read permissions from Process entity. At the most it disables the button in Ribbon.

We can completely hide the Process group globally by using HideCustomAction, but then its is hidden from every user, even System Administrator cannot see it. So we have to do Ribbon customization to conditionally hide the Process group from certain User.

In following blog I have explain how I achieved it using entity based Ribbon customization.

Steps

1. Create a CRM Solution with number of entities on which Process Group in Ribbon needs to be hidden and Export this solution.

2. From exported .zip file extract customization.xml file and open it in suitable editor, my favorite is Visual Studio.

3. Under <CustomActions> which is under<RibbonDiffXml> paste following XML code

4. Replace XXXXX with entity logical name

5.Under <CommandDefinitions> paste following XML colde.

6. Replace XXXXX with entity logical name

7. Under <DisplayRules> under <RuleDefinitions> paste following XML code.

This rule basically checks whether User has Workflow Execution Permissions at Organization level. It will hide Process Group from all users who do not have Workflow Execution permissions.

8. Replace XXXXX with entity logical name

9. Save all these changes, Zip it back and Import the solution.

10. Open Security Role go to Customization tab and remove Execute Workflow Job access.

11. Now user will not see the Process tab

One of the advantage of this approach is Ribbon buttons are hidden based on Security Role settings. Based on requirements Display conditions can be further modified.

Such records can be shown as Sub-Grid or on Form Sub-Grid. However at times we might have to show up data from related entities where there is no CRM relationship exists between the entities. This scenario is more prominent where there is integration between multiple CRM instances.

I found one way to do this. Following URL can be used to set a Read-Only CRM Entity form

http://SERVER Name/ORG NAME/userdefined/areas.aspx?

Query String Parameters

Example:

http://CrmWeb01/PWB/userdefined/areas.aspx?oId=%7bC671558A-34C5-4473-9344-94E85D7540AC%&oType=10000&pagemode=iframe&security=852023&tabSet=new_partner_new_cert_MPartner

Calling URL in IFrame: In above given URL query parameter oId is only parameter which needs to be dynamically set depending upon parent entity Id. For this I created a HTML Web Resource and added a IFrame in it. Following JavaScript function reads GUID value and sets it in URL

Screenshot.

Here is how it looks

Hope this helps you.

To avoid these repeating steps for each solution I created a small utility to export solution using CRM SDK.

This solution is available at CodePlex

[Updates 11-Feb-2012] Updated version 1.4.0.0 is now uploaded on CodePlex, it has better Connection Control which allows Connection with On-Premise, Online and IFD deployments.

Its very simple utility, opens with Windows Form

After entering CRM URL it loads all the Unmanaged solution into Grid View

Once loaded one can set folder path where backup needs to be saved and select Solutions that needs to be exported from Grid View

Clicking “Export Selected Solution” will save.zip files to selected folder location.

File name used for saving .zip file is [Solution’s Unique Name]_[Date Time in MM_dd_YYYYT_HH_mm format]. For example: Default_01_08_2012_T22_22.zip. Having DateTime stamp ensure that each time separate copy is maintained.

In such cases <HideCustomAction> is of less helpful as it globally hides the Ribbon element.

In this Walkthrough I am trying to demonstrate on of such scenario.

Scenario: A CRM Entity form has has Many-To-One relationship with multiple entities. Each of these entities are having Sub-Grid to show CRM entity in List form. Now we wanted to hide Contextual (List) tab for Sub-Grid entity from Main form of some of the entities.

Step 1:

Create a CRM 2011 Solution with entity for which Ribbon in Contextual Tab needs to be hidden. In this case entity name is new_cpvertical

Step 2:

Open ExportRibbonXml for the entity new_cpvertical. You can find this xml at SDK folder \samplecode\cs\client\ribbon\exportribbonxml\bin\Debug\ExportedRibbonXml. If RibbonXml for your entity is not available you can execute the solution exportribbonxml.sln and create one.

Step 3:

In RibbonXml, locate Tab element with Id as “Mscrm.SubGrid.new_cpvertical.MainTab” and copy entire Tab element with all its decendants.

Step 4:

Open customization.xml file from Solution you exported in Step1, and add Tab element copied in Step 3 under

Note that Location value for CustomAction is same as MainTab id.

Step 5:

Copy Command="Mscrm.SubGrid.new_cpvertical.MainTab" and all the Rules that has been referenced in Command.

Step 6:

Copy <TabDisplayRules> element under <RuleDefinitions> as shown below

Note: TabCommand should be same as CommandDefinition Id used under CommandDefinition

Step 7:

Create a new DisplayRule as shown below

Note: EntityName value is name of the PrimaryEntity where Sub-Grid is placed. Depending upon how many such entities need to be configured you can add Or to it.

Step 8:

Call this DisplayRule in Command ="Mscrm.SubGrid.new_cpvertical.MainTab"

Step 8:

Save the Customization, zip it back to Solution file and Import solution in CRM and Publish the Customization.

Here is how it looks with Contextual Ribbon hidden

With Contextual Ribbon (Note there is a List Tools Ribbon tab)

After hiding Contextual Ribbon (Note there is NO List Tools Ribbon tab)

Hope this helps

When we share this link to form and when user opens it, it opens a complete CRM form which has Ribbon bar, based on form type it can have a left hand Navigation bar. So its standard for that User gets to see.

There might be requirement where we have to show Read-Only copy of form (and not the Report page).

I found one way to do this. Following URL can be used to set a Read-Only CRM Entity form

http://SERVER Name/ORG NAME/_forms/print/custformprint.aspx?

Query String Parameters

Following is example of such URL

http://SERVER Name/ORG NAME/_forms/print/custformprint.aspx?allsubgridspages=false&formid=c2813dee-bc93-446b-aa20-7b727e5e6ac8&id=%7bD0A97532-1A3A-E011-9584-00155DC94520%7d&objectType=10031

Sample form: This is how Read-Only form looks like.

I have developed a CRM 2011 WebResource which will render self-joined Entity data in Tree View structure and which can be used to assigned to Lookup attribute on CRM 2011 form.

This Utility has 3 parts

1. Mechanism to render data from Self-Joined entities and convert it to XML Web Resource form.

2. On CRM form bind XML Web Resource data to TreeView control

3. Wiring event to populate Lookup attribute on CRM form when User select one of the Tree View Node.

Demo Screen 1

This WebResource is easily portable on CRM Form and it needs just one JavaScript call to set Lookup Attribute for which data need to be rendered.

Let me know if anybody interested in having CRM Managed Solution for this WebResource and I will be glad to share it.

Any ideas to improve this TreeView control is welcomed.

[Updates: 11/03/2011]

Thanks all those who showed interest in TreeView utility. I am currently working on Packaging the Utility into CRM 2011 Managed Solution, once completed with Testing I will share the Managed Solution

[Updates: 11/07/2011]

Finally I could complete packaging Beta releases for two separate Projects !!!

These projects are now available in CodePlex. In case you come across any issues send me an email.

CRM 2011 TreeView for Lookup

CRM 2011 TreeView for Dependent Picklist

It would have been good if User don’t have to click and can see Lookup entity fields data in Child form itself. CRM does provide Entity Mapping which allows to Pre-populate mapping attributes at the time of creation of Child record, however it has its own limitations. To overcome some of the limitations of Entity Mapping I have created a Web Resource Utility which can be found at CRM 2011 Attribute Mapping

I also developed more light weight Web Resource Utility which does not required any Entity Mapping and still give Lookup Entity field data on CRM 2011 main form.

Following screen shot demonstrates the utility

Demo Screen:1

Each Lookup field can have their corresponding Web Resource on form. With the help of my JavaScript library CRM Customizer can decide attributes of the Lookup entity to be shown on form in tabular format.

Web Resource can be placed anywhere on the form.

Demo Screen: 2

If Lookup attribute is empty, Utility will still show the Empty Web Resource.

Demo Screen: 3

Utility does cover error situations. In case CRM customizer have incorrectly set parameters in JavaScript Library or if columns got deleted from Lookup attribute after it is configured in child form JavaScript library, utility does show appropriate message to take corrective action.

Instructions

Managed Solution contains following components

1. lookupr/Scripts/jquery_1.6.4.min.js

2. lookupr/Scripts/SDK.RetrieveData.js

3. lookupr/Scripts/LookupPreviewScript.js

4. lookupr/Lookup_Preview.htm

Steps

1. Open the form on which you wanted to put Lookup Preview.

2. Add a Web Resource to form

1. Select Web Resource as lookupr/Lookup_Preview.htm
2. Give Name and Label to Web Resource, note exact name of WebResource for later use.
3. In “Formatting” tab select Number of rows, minimum 2 rows are required, but depending upon data length this number can be increased.
4. Unselect “Display border”.

3. Save the Customization.

4. In form Properties, select JavaScript web resources as shown below

5. Event Handler

On Form OnLoad even select library as lookupr/Scripts/LookupPreviewScript.js and function as LoadLookPreviewDelayed

Function LoadLookPreviewDelayed takes following arguments

1.Web Resource Name : This is Name of Lookup_Preview.htm that was give in earlier step

2. Lookup Attribute Id: AttributeID of Lookup Attribute for which Lookup Preview is required.

3. Attribute Set: This is pipe (|) separated list of Label and attribute name from Lookup entity which needs to be shown in Lookup Preview. Label and Attribute Name must be separated by#

Example for Attribute Set is ‘Job Title#jobtitle|EmailId#emailaddress1|Telephone#telephone1|Language#new_preferredlanguage|DoNotEmail#donotemail’

Video Demo

Download CRM Managed Solution 

Download CRM Solution

This is Silverlight 4 Web Resource Solution

Out of Box Functionality
Entity mapping facilitates data entry when creating new records that are related to a parent record. When a Form for a new record that is not associated with a parent record is opened, all the fields in the Form are blank. If there are any required relational constraints to another entity, those fields must be manually filled in before the record can be saved. This is why it is usually easier for the user to add new records from the Parent record
This out of box feature has following limitation
Mapping only works when a new record is created in the context of a parent record. Mapping does not apply if you create a new record outside the context of a parent record.

Solution Provided by Attribute Mapping Utility (Download CRM Solution)
Attribute Mapping Utility allows User to carry out Mapping of Lookup fields from Child form. As against out of box feature this mapping can be done either in Create or Update form.
Highlights

1. Ribbon Button is available in All Entity Forms.
2. Ribbon Button is enabled and disabled as per User Access Rights on Entity
3. Utility automatically read Attribute Mapping metadata stored in CRM. No added configuration is required to do.
4. Utility automatically reads Lookup fields on Form and its Mapping Attributes.
5. Silverlight pop-up allows user to select Lookup fields for which mapping is needed
6. Silverlight pop-up give option to see trace

Demo Screenshots

Ribbon Button for Attribute Mapping

Attribute Mapping Pop-up: Pop-up window shows List of Lookup controls placed on visible on form

Attribute Mapping Pop-up: There are 3 buttons on pop-up window

1. Submit: This button will map all selected Lookup attributes and it will show Trace window to show some more details. This button will not automatically close the Pop-up window.

2. Submit & Close: This button will map all selected Lookup attributes and automatically close the Pop-up window.

3. Close: This will simple close Pop-up window without mapping any Lookup attributes.

In following walkthrough I am demonstrating how to use EnableRule in Ribbon to call JavaScript function which will do Asynchronous call to CRM using REST and how to set Enable and Disable Ribbon Button

Assuming that Ribbon Customization is done and CustomRule is calling JavaScript function on EnableRule.

Following is how JavaScript. Here I am checking if logged in User is associated with current Entity record using Connections.

///<reference path=”XrmPage-vsdoc.js”/>
//Global Parameter
var isPartnerTeamMember = false;
var PageUI; 

function GetServerUrl() {

    var customServerURL = document.location.protocol + “//” + document.location.host + “/” + Xrm.Page.context.getOrgUniqueName();

    return customServerURL;

}

function CheckUserAccessOnPartner(PrimaryEntityTypeName, partnerObjectTypeCode, SelectedEntityTypeName, partnerId) {

    if (isPartnerTeamMember) {

        return true;

    }

    else {

        PageUI = window.top.opener.parent.Xrm.Page.ui;

        var context = Xrm.Page.context;

        var serverUrl = GetServerUrl();

        var userId = context.getUserId();

        var ODataPath = serverUrl + “/XRMServices/2011/OrganizationData.svc”;

        var retrieveReq = new XMLHttpRequest();

        retrieveReq.open(“GET”, ODataPath + “/ConnectionSet?$select=ConnectionId,Record1Id,Record1ObjectTypeCode,Record2Id,Record2ObjectTypeCode&$filter=Record1ObjectTypeCode/Value eq ” + partnerObjectTypeCode + ” and Record2ObjectTypeCode/Value eq 8 and Record1Id/Id eq guid’” + partnerId + “‘”, true);

        retrieveReq.setRequestHeader(“Accept”, “application/json”);

        retrieveReq.setRequestHeader(“Content-Type”, “application/json; charset=utf-8″);

        retrieveReq.onreadystatechange = function () {

            retrievePartnerConnectionsCallBack(this);

        };
        retrieveReq.send();
        return false;
    }
}

function retrievePartnerConnectionsCallBack(retrieveReq) {

    if (retrieveReq.readyState == 4 /* complete */) {

        if (retrieveReq.status == 200) {
            //Success
            var responseData = JSON.parse(retrieveReq.responseText).d;

            if (responseData != null && responseData.results != null && responseData.results.length > 0) {

                for (i = 0; i < responseData.results.length; i++) {

                    var record2Id = “{” + responseData.results[0].Record2Id.Id + “}”;

                    if (record2Id.toLowerCase() == Xrm.Page.context.getUserId().toLowerCase()) {

                        isPartnerTeamMember = true;

                        if (PageUI != null) {
                            PageUI.refreshRibbon();
                        }
                        break;
                    }
                }
            }
        }

        else {
            //errorHandler(retrieveReq);
        }
    }
}

 Key Point to note in above Script

1. I am using Global variable to defined return value (isPartnerTeamMember) which is by default set to false.
2. As first step I am checking isPartnerTeamMember and returning if it is true else calling REST query.
3. In REST callback I am calling Xrm.Page.ui.refreshRibbon() method, which will reevaluate function and this time it will find isPartnerTeamMember as true and it will be returned from there.
4. One of the important thing to note here is if you have having Ribbon button on SubGrid or associated view Xrm.Page.ui will be null for this you have to use window.top.opener.parent.Xrm.Page.ui (Thanks Daniel Cai !! for figuring out this)

Hope this Helps