Tuesday, July 28, 2015

CRM 2011/2013/2015 Javascript: Get Logged in User Full Name

CRM 2011

 function getUserFullName() {  
   var serverUrl = getCrmServerUrl();  
   var userRequest = GetRequestObject();  
   userRequest.open("GET", serverUrl + "/SystemUserSet(guid'" + Xrm.Page.context.getUserId() + "')?$select=FullName", false);  
   userRequest.setRequestHeader("Accept", "application/json");  
   userRequest.setRequestHeader("Content-Type", "application/json; charset=utf-8");  
   userRequest.send();  
   if (userRequest.status === 200) {  
     var retrievedUser = JSON.parse(userRequest.responseText).d;  
     var userFullName = retrievedUser.FullName;  
     return userFullName;  
   }  
   else {  
     return "";  
   }  
 }  
 function getCrmServerUrl() {  
   if (Xrm.Page.context.getClientUrl) // CRM 2011 UR 12+ and CRM 2013  
   {  
     serverUrl = Xrm.Page.context.getClientUrl() + "/";  
   }  
   else // CRM 2011 UR 11 or below  
   {  
     serverUrl = Xrm.Page.context.getServerUrl();  
   }  
   // Adjust URL for differences between on premise and online  
   if (serverUrl.match(/\/$/)) {  
     serverUrl = serverUrl.substring(0, serverUrl.length - 1);  
   }  
   return serverUrl + "/XRMServices/2011/OrganizationData.svc";  
 }  
 function GetRequestObject() {  
   if (window.XMLHttpRequest) {  
     return new window.XMLHttpRequest;  
   }  
   else {  
     try {  
       return new ActiveXObject("MSXML2.XMLHTTP.3.0");  
     }  
     catch (ex) {  
       return null;  
     }  
   }  
 }  


CRM 2013/2015

Xrm.Page.context.getUserName()

Thursday, July 9, 2015

How to Analyze the Performance of Dynamics CRM

The Performance Tool offers a simple and efficient method to analyze (and improve) the performance of Microsoft Dynamics CRM online and on premise environments.
You do need to have CRM 2013 SP1(or above) or 2015. It can be used on both forms and views.
The following steps activates this hidden feature.
Open a CRM form from your browser (IE or Chrome). For example, open an Account form.
Press Ctrl + Shift + Q to view the performance analyzer. This analyzer pop up window appears on your browserAnalyze Performance of CRM
To activate the tool, click the Enable button.
Press F5 to refresh your CRM form. The Performance analyzer will close.
Press Ctrl + Shift + Q to open the performance analyzer
Analyze performance of Dynamics CRM

What does this mean?

The different sections are all code that is triggered prior to a user having a functioning form to work on.
When an environment has many customizations, plug-ins, business rules, iframes or subgrid on a form, this is a great way to determine how quickly it is loading.The time is a breakdown of milliseconds.
In addition to the graphical view, when you click the “Select Major” button you’ll also see the breakdown in a text format.
  • Form Load Start (> 0 ms)
  • Read-Ready (> 1272 ms)
  • Initialize Controls – ViewportInlineEditControlInitializer (> 4583 ms)
  • Initialize Controls – NonViewportFormBodyInlineEditInitializer (> 4954 ms)
  • Initialize Controls – DeferredQuickFormInlineEditInitializer (> 5106 ms)
  • Onload Handler Start (> 5406 ms)
  • Onload Handler Finish (> 5579 ms)
  • Form Full Controls Init (> 5663 ms)
Finally, it is a good idea to disable the tool by clicking the “Disable” button when you have completed your analysis.

How to Close a Form in CRM 2013 using javascript

With reference to CRM 2013 SDK, following is the code snippet to close the form.

Xrm.Page.ui.close();

Please note the following important points.

"The HTML Window.close method is suppressed. To close a form window you 

must use this method. If there are any unsaved changes in the form the user 

will be prompted whether they want to save their changes before the window closes." 

( Ref: CRM 2013 SDK )


Whereas if we need to save the record using javascript, 

we could use the same methods which we were using in CRM 2011.

Xrm.Page.data.entity.save( null | "saveandclose" |"saveandnew" );

 

Arguments values:


save()

If no parameter is included the record will simply be saved. This is the equivalent of using the 

Save command.


save("saveandclose")

This is the equivalent of using the Save and Close command.


save("saveandnew")

This is the equivalent of the using the Save and New command.

( Ref: CRM 2013 SDK )

Monday, July 6, 2015

Loading dependent jscript libraries in ribbon button’s execution CRM 2013

I have a ribbon button on my “Quote” main grid .

I am calling function “sayHello” which is in my web resource “Quote_ribbon” by defining custom action like below.


FunctionName=”sayHello”
Now the problem is, I need to call another method from my “sayHello” function, which is in other web resource “common”.

Solution :-
The solution is simple. We can add all the required libraries to node like below
 FunctionName=”isNaN” 
Note – Since requires a function name, pass “isNaN”.

If you refer 3rd party libraries like jquery or XRMToolkit in your library then just add those in the actions.

Make sure you use the correct order when configuring the ribbon actions.

The dependent script files has to be ordered before the actual script file.


Wednesday, July 1, 2015

Report Parameter Error(the value expression for the query parameter refers to non-existing report parameter . letters in the names of parameters must use the correct case)

 I use the @Region in the dataset query, then modify the parameter name from Region to region, then modify the @Region to @region in the dataset query. When we render the report, it throws an error message that “The Value expression for the query parameter '@region' refers to a non-existing report parameter 'Region'. Letters and names of parameters must use the correct case.” But we couldn’t find anything about Region in the Report Data tab.

the query parameter @region still use the =Parameters! Region.Value as value in the XML file. Even after removing them from the Data tab, the fields might still be in the and section.  Right-click the report in the Solution Explorer and go to "View Code" and double-check if Region is still present in those sections of the XML.
What's more, the issue may be caused by the cache. Please try to delete the reportname.rdl.data file in the report project folder before preview the report.