Skip Ribbon Commands
Skip to main content

Brite Global Blogs

:



Sign In
December 31
Happy Holidays

Happy Holidays from the Brite Global team. We would like to thank all of our customers and our partners for your business in 2011. We wish you a great holiday season and we are looking forward to working with you in 2012.

We would like to thank you and wish you, your family and friends a Happy and joyful New Year.

Your friends at Brite Global

July 19
Deploy a Report Builder 3.0/VS 2010 Report on SSRS 2008 (Not R2)

Visual Studio 2010 and Report Builder 3.0 RDL reports use a new schema that is not supported by SQL Server 2008 Reporting Services. They are designed to work only with SSRS 2008 R2. Currently there is no way to publish a VS2010 Report on SQL Server 2008 without some modifications to the RDL code.

In order to publish the RDL in SSRS 2008, the following steps have to be performed:

1. Open the RDL file (not project) with Visual Studio or an Xml Editor.

2. Replace the report namespace occurrences from 2010 to 2008:

<Report xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner" xmlns:cl="http://schemas.microsoft.com/sqlserver/reporting/2010/01/componentdefinition" xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition">


Should be replaced with:

<Report xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner" xmlns:cl="http://schemas.microsoft.com/sqlserver/reporting/2008/01/componentdefinition" xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition">

3. Report the following Xml Tags (Keep the Xml between the Tags)
<ReportSections>

<ReportSection>

</ReportSection>

</ReportSections>


4. Save the Xml file and publish the report. This should now work with SSRS 2008.

July 13
Displaying Associated Views from Other Entities

Sometimes, just as we would have a Navigation link that displays an IFRAME, we would like to display a View from another entity in there.

The Solution is pretty simple. We create the navigation links, provide the Url of the of the Related Entity View and finally use the loadIsvArea JavaScript function to display the results, as shown in the example below.

The following example displays the Activities and Closed Activities of a custom entity in of the Marketing List Form. The function receives as a parameter the ID of the record that I want to display and the entity type code (etc) of the related entity.

function SetInteractions(listid, etc)
{

   var items = Xrm.Page.ui.navigation.items.get();

     for (var i in items)

   {

      var item = items[i];

      var label = item.getLabel();

      var id = item.getId();

           if (label == "Activities")

      {

         var urlActivities = encodeURI("areas.aspx?formid=56ac0775-3315-4971-9b61-9fa6548d8935&navItemName=Activities&oId=" + listid + "&oType=" + etc + "&pagemode=iframe&security=65591&tabSet=areaActivities");

         urlActivities = serverUrl + "/UserDefined/" + urlActivities;

                var navActivities = document.getElementById(id);

         navActivities.onclick = function () { loadIsvArea(Mscrm.CrmUri.create(urlActivities), false); }

          }

      if (label == "Closed Activities")

      {

         var urlHistory = "areas.aspx?formid=56ac0775-3315-4971-9b61-9fa6548d8935&navItemName=Closed%20Activities&oId=" + listid + "&oType=" + etc + "&pagemode=iframe&security=65591&tabSet=areaActivityHistory";

         urlHistory = serverUrl + "/UserDefined/" + urlHistory;  

         var navHistory = document.getElementById(id);

         navHistory.onclick = function () { loadIsvArea(Mscrm.CrmUri.create(urlHistory), false); }

      }

   }

}

 

Note: The solution above applies to Microsoft Dynamic CRM 2011

January 20
Microsoft Dynamics CRM 2011 Launched

Microsoft Corp. CEP Steve Ballmer announced on Monday, January 17​​, 2011 the worlwide availability of Micorosft Dynamics CRM Online, the cloud version of the new Microsoft Dynamics CRM 2011 release that delivers new levels of productivity for sales, service and marketing organizations. The on-premises and partner-hosted versions of Microsoft Dynamics CRM 2011 will be globally available on February 28, 2011.

Microsoft Dynamics CRM Online is available today at a promotional prive of $34/user/month for the first 12 months of service to qualified customers that sign up by June 30, 2011.

Read full press release here.

November 24
Multiple Record Editing in CRM 2011

Microsoft Dynamics CRM 2011 allows modifications of records and activities in bulk.
You can specify multiple records and then select Edit, which will allow to Edit certain fields that are shared among multiple records.

The records that are going to be used for Multiple Record Editing must be of the same type.
In the case of activities, you can edit multiple tasks, or multiple e-mails for example together.

Step 1: Select the records that you want to edit

Step 2: Click on the Edit Button on the ribbon

Step 3: Modify the fields that you want to change for ALL records

Step 4: Save the records and view the new results

November 05
Integrate Google Maps (or Bing) with CRM 2011

Integrating Google Maps or Bing Maps with Microsoft Dynamics CRM is a requirement that we often come across.
This blog will demonstrate how to add a new button to the CRM account entity and when clicked it will display the map of the address in a new browser window.

This example worked of course with CRM 4.0, but we would like to show you how to do this in CRM 2011 (can be implemented online or on-premise)

The first thing that we need is to do is find a 16x16 image and a 32x32 image to place on the ribbon, as well as create a javascript file and function that will open up the new window.
The following function will retrieve the fields from the account form and pop up a new window:

function showGoogleMap() {

 

// Get the values from the form

var street1Field = Xrm.Page.data.entity.attributes.get("address1_line1");

var address = street1Field.getValue();

 

var cityField = Xrm.Page.data.entity.attributes.get("address1_city");

address = address + ', ' + cityField.getValue();

 

var stateField = Xrm.Page.data.entity.attributes.get("address1_stateorprovince");

address = address + ' ' + stateField.getValue();

 

var postalField = Xrm.Page.data.entity.attributes.get("address1_postalcode");

address = address + ' ' + stateField.getValue();

 

address = address.replace(/ /g, "+");

 

 

var url = 'http://maps.google.com/maps?f=q&source=s_q&hl=en&vps=1&jsv=156c';

url = url + '&q=' + address;

 

window.open(url);

}


Note that we are using the new Xrm.Page namespace in our Javascript function.
Now save the javascript file, and we will upload the files (Web Resources) to our CRM Server.

  • In your CRM application, Click on Settings and then click on Solutions under the Customization section.
  • Click on New to create a new Solution. In the popup window enter the Display Name, Name and Published:

  • Save the Solution.
  • Under Components -> Entities, click on Add Existing Entity, and add the account entity
  • Click on Web Resources and add the javascript file

  • Do the same for the two image files.
  • When complete, your solution's web resource should look something like this:

  • Click on Publish All Customizations, and then Save and Close

The next step that we need to do is to modify the Customizations Xml file, so that the button appears on it and assign the images and scripts to the button. In order to do that we need to export the Solution, and modify it in an Xml Editor (or Notepad). In this case, we would recommend an Xml Editor.

  • In the Solutions Window, select the accountSolution Solution, and click on Export.
    Since you already published your customizations, you can skip the first wizard page and click Next.
    • Click Next in the Export System Settings (Advanced) Page (do not check any of the boxes)
    • For now, keep the Package Type as Unmanaged, and click Next
    • Click on Export, Save the file and Extract the file.
  • Open the customizations.xml file in Microsoft Visual Studio

Locate the RibbonDiffXml section and paste the following code on top of it

<RibbonDiffXml>

<CustomActions>

<CustomAction Id="RentRoll.account.form.ShowMap.CustomAction" Location="Mscrm.Form.account.MainTab.Workflow.Controls._children" Sequence="268">

<CommandUIDefinition>

<Button Id="RentRoll.account.form.ShowMap.Button" Command="RentRoll.account.form.ShowMap.Command" LabelText="$LocLabels:RentRoll.account.ShowMap.LabelText"
ToolTipTitle="$LocLabels:RentRoll.account.ShowMap.LabelText" ToolTipDescription="$LocLabels:RentRoll.account.ShowMap.ToolTip"
TemplateAlias="o1" Image16by16="$webresource:rr_MapIt16" Image32by32="$webresource:rr_MapIt32" />

</CommandUIDefinition>

</CustomAction>

</CustomActions>

<Templates>

<RibbonTemplates Id="Mscrm.Templates"></RibbonTemplates>

</Templates>

<CommandDefinitions>

<CommandDefinition Id="RentRoll.account.form.ShowMap.Command">

<EnableRules>

<EnableRule Id="RentRoll.account.Clients.EnableRule"/>

<EnableRule Id="RentRoll.account.form.FormStateNotNew.EnableRule"/>

</EnableRules>

<DisplayRules>

<DisplayRule Id="RentRoll.account.form.FormStateNotNew.DisplayRule"/>

<DisplayRule Id="RentRoll.account.Clients.DisplayRule"/>

</DisplayRules>

<Actions>

<JavaScriptFunction Library="$webresource:rr_PropertyFormScripts.js" FunctionName="showGoogleMap" />

</Actions>

</CommandDefinition>

</CommandDefinitions>

<RuleDefinitions>

<TabDisplayRules />

<DisplayRules>

<DisplayRule Id="RentRoll.account.form.FormStateNotNew.DisplayRule">

<FormStateRule State="Create" InvertResult="true"/>

</DisplayRule>

<DisplayRule Id="RentRoll.account.Clients.DisplayRule">

<CrmClientTypeRule Type="Web"/>

</DisplayRule>

</DisplayRules>

<EnableRules>

<EnableRule Id="RentRoll.account.Clients.EnableRule">

<CrmClientTypeRule Type="Web"/>

</EnableRule>

<EnableRule Id="RentRoll.account.form.FormStateNotNew.EnableRule">

<FormStateRule State="Create" InvertResult="true"/>

</EnableRule>

</EnableRules>

</RuleDefinitions>

<LocLabels>

<LocLabel Id="RentRoll.account.ShowMap.LabelText">

<Titles>

<Title languagecode="1033" description="Show Google Map" />

</Titles>

</LocLabel>

<LocLabel Id="RentRoll.account.ShowMap.ToolTip">

<Titles>

<Title languagecode="1033" description="Display a Google Map for the selected property" />

</Titles>

</LocLabel>

</LocLabels>

</RibbonDiffXml>


Notes:
The prefix used in this sample is RentRoll, you can use a different prefix, but make sure that it matches all the way through
You can modify the above xml to better fit your needs.
Make sure that the web resource names match the names in the web resources section of the xml file

  • Save the Xml file.
  • Select all the files that you previously extracted, and zip them into a new file
  • In your CRM solutions Window, Click on Import
    • In the wizard page click Browse…, and select the newly created zip file.
    • Click Next a couple of times until the import is complete.
    • When done, Publish All Customizations, and Close

The last step is to let the CRM account entity know to use the javascript file for the form events:

  • Click on Workplace and under Customers select Accounts
  • On the ribbon, click on the Customize Tab, and then click on Form
  • Click on the Form Properties button
  • In the Events Tab Add the javascript library to the form
  • Click OK
  • Publish the Form, and click on Save and Close

Now is testing time.
Click on any of your accounts (or other entities) to open up the account form
You should see the Show Google Map button on the form.

Click on the Show Google Map button, and a new window should open up with a map of the address on that form.

Good luck!!!


 

November 05
Report Viewer Control not displaying data when deployed IIS7

This issue sometimes happens when you deploy a web application that contains report files on IIS7.
The reports work fine in the development environment, but once published nothing appears in the results.
The report window will either complete and show zero pages or the "Report is being generated" message will show up:

The problem is that the web browser is unable to locate Reserved.ReportViewerWebControl.axd, even though the http handler might be included in the web.config file.

To verify that this is the problem, open fiddler web debugger in your Internet Explorer session and check for any 404 errors with the Reserved.ReportViewerWebControl.axd url.

To resolve this issue we have to manually add the http handler to the web site in IIS. Report Viewer 2008 Redistributable with SP1 should be installed of course.

  1. Open IIS.
  2. Click on the web site that you want to add the Handler Mapping to
  3. Double Click on the Handler Mappings

  4. From the actions Task Menu click on Add Managed Handler

  5. Enter the following information in the Add Managed Handler Window:
    Request Path: Reserved.ReportViewerWebControl.axd
    Type: Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Name: Reserved-ReportViewerWebControl-axd

  6. Click OK and you're done.

 

September 17
Lookup Filtering in CRM 2011

One of the issues that CRM had was how to filter records in a lookup control that is dependent on another control on the form. An example of this would be if I use the account and contact entity and have a connected entity in between such as maybe a position.

I will use an example of Property Management where I have Properties (account) and Tenants (contact), and a connected entity in between called Rental Unit.

The first step that I want is to add two fields to the contact form, one for property and one for unit:

Now that the fields are on the form, I need to use the Related Records Filtering feature in CRM 2011 to only show the related records in the steps below:

  • Open the Tenant (contact) form, and click on the Customize Ribbon Tab.
  • Select Form from the Design Tab group to open the Tenant form in Design Mode
  • Select the lookup control that you want to filter the results for, and click on the Change Properties button in the Edit Group of the Ribbon.
  • The field Properties webpage dialog will open.
  • One the Display Tab check the "Only show records where:" under the "Related Records Filtering" section.
  • Select the required values from the drop downs. In our case it would be:
    Property (Tenants) Contains Property (Units)

  • Save the Form
  • Publish the contact (Tenant) entity.

When you click on the Units lookup after you have selected the Property, only the Units for the selected property will appear:

 

September 10
Microsoft Dynamics CRM 2011 Public Beta Released

Microsoft has released the much awaited Microsoft Dynamics CRM 2011 public beta, formerly known as V.Next today. Microsoft Dynamics CRM 4.0 was a huge jump in enterprise scalability, performance and a true multi-tenant architecture. Microsoft Dynamics CRM 2011 takes that release and builds in usability, a ribbon like interface, more of a flat User Interface that requires fewer clicks and better visualizations.

The main key features include:

  • Familiar experiences through a next-generation native Outlook client, Microsoft Office contextual ribbon, role tailored design and user personalization.
  • Intelligent experiences through guided process dialogs, inline data visualizations, performance and goal management and real-time dashboards.
  • Connected experiences through cloud development, Windows Azure integration, contextual SharePoint document repositories, teamwork and collaboration and the Microsoft Dynamics Marketplace.

 

Learn more at crm-2011.com

September 02
Publishing a Web Part to a Production SharePoint Environment

After developing the web part in Visual Studio and testing it in the development or testing environment, we need to publish the web part to the production machine.

The first thing that we need to do is copy the wsp file from the development machine to the production machine.
The wsp file is located in the bin/Debug or bin/Release directory of your Visual Studio Project.

The first steps are to copy the file and deploy it.

  • Copy the file to the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN directory on your SharePoint Production Server.
  • Open Command Prompt and Change the Directory using the following command: cd "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\"
  • Add the solution to the SharePoint Central Administration by entering the following command:
    stsadm –o addsolution –filename "webpartname.wsp" (replace webpartname.wsp with the name of your web part)

Open SharePoint Central Administration, and in the left navigation menu click on System Settings
Under Farm Management, click on Manage farm solutions.


You should now see your web part in the list of web parts. Click on your web part name .

Click on the Deploy Solution link above the web part information.
 

You will have the possibility to deploy this solution to a particular site or all sites under that server.

After the solution has been deployed, go to your SharePoint site:

  • Make sure you are logged into the site
  • Click on the Site Actions
  • Click on Site Settings
  • Under Site Collection Administration, click on Site collection features
  • Find the web part on the list of available web parts, and click Activate.

Your web part should now be available for use on your site.


 
 

1 - 10Next
 

 About this blog

 
Welcome to the  Brite Global Blog. Here you will find content related to new and existing technologies, company, news and events.

Powered By SharePoint 2010