I have quite a long journey to hands-on Dynamics CRM (around six years and still counting), and I have a confession to make. I never use OrganizationServiceContext ever! This class will allow you to retrieve Dynamics CRM data using the infamous LINQ (Language-Integrated Query) which more convenient compare using to FetchXml/QueryExpression/QueryAttribute.

The first thing that we must be aware, all the queries that we will run against OrganizationServiceContext, will be converted to QueryExpression based on this official documentation. So, you need to know that there are limitations like the groupby, aggregate, last, and a limited where (right is a column, left only accept value) based on this documentation.

Generated The OrganizationServiceContext

There are multiple ways to generated the necessary classes (it's the same thing if we want to use early-bound classes that you can check on here). Or you always can go to our favorite XrmToolBox and download either Albanian Early Bound or Early Bound Generator by Daryl LaBar.

Once the files are generated, you can use them on your project.

Initialize OrganizationServiceContext

To start retrieving your data, you only need to pass the IOrganizationService to the OrganizationServiceContext:

 var context = new CrmServiceContext(service);

Here are the sample of the queries I wrote:

Sample Queries

You can check for all the samples of retrieving using the query here.

Small Mistakes That Lead to Performance Issue

When we query using Linq, we tend to select the entity itself. But, when we do this, we actually retrieve all columns and it will degrade the performance. So the better way to select is using this way:

 Console.WriteLine("account2"); var accounts2 = (from a in context.ContactSet 				 orderby a.FullName descending 				 select a).ToArray();  Console.WriteLine("account3"); var accounts3 = (from a in context.ContactSet 				 orderby a.FullName descending 				 select new { a.Id, a.FullName }).ToArray();

The result can be seen below:

account3 have more better performance

The second tip is to always ToArray() or ToList() the query once you want to get the data. If we are not executing it directly, then when we re-access again the query, it will take data from the database again instead of in the memory data.

To prove this behavior, I made a simple OrganizationService decorator:

 public class LoggerService : IOrganizationService { 	public IOrganizationService Service { get; }  	public LoggerService(IOrganizationService service) 	{ 		Service = service; 	}  	public EntityCollection RetrieveMultiple(QueryBase query) 	{ 		var start = DateTime.Now; 		var result = Service.RetrieveMultiple(query); 		var end = DateTime.Now;  		Console.WriteLine($"Start: {start:hh:mm:ssfffff}. End: {end:hh:mm:ssfffff}. Total: {(end - start).TotalMilliseconds}");  		return result; 	}  	public OrganizationResponse Execute(OrganizationRequest request) 	{ 		var start = DateTime.Now; 		var result = Service.Execute(request); 		var end = DateTime.Now;  		Console.WriteLine($"Start: {start:hh:mm:ssfffff}. End: {end:hh:mm:ssfffff}. Total: {(end - start).TotalMilliseconds}");  		return result; 	}  	#region Not Being Used 	public void Associate(string entityName, Guid entityId, Microsoft.Xrm.Sdk.Relationship relationship, EntityReferenceCollection relatedEntities) 	{ 		throw new NotImplementedException(); 	}  	public Guid Create(Microsoft.Xrm.Sdk.Entity entity) 	{ 		throw new NotImplementedException(); 	}  	public void Delete(string entityName, Guid id) 	{ 		throw new NotImplementedException(); 	}  	public void Disassociate(string entityName, Guid entityId, Microsoft.Xrm.Sdk.Relationship relationship, EntityReferenceCollection relatedEntities) 	{ 		throw new NotImplementedException(); 	}  	public Microsoft.Xrm.Sdk.Entity Retrieve(string entityName, Guid id, ColumnSet columnSet) 	{ 		throw new NotImplementedException(); 	}  	public void Update(Microsoft.Xrm.Sdk.Entity entity) 	{ 		throw new NotImplementedException(); 	}
at

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.