I forgot to invite you at Dynamics 365 Bootcamp in Zurich, next Friday and Saturday (June, 8th – 9th, 2018).
we can meet and talk about technologies, Microsoft Dynamics 365 and more, more, more…
or you can follow my speech 🙂
See you next weekend
Ops.. the link 🙂 http://365saturday.com/dynamics/zurich-switzerland-bootcamp-2018/
public Microsoft.Xrm.Sdk.EntityCollection UserTeams(Guid UserID)
{
QueryExpression query = new QueryExpression("team");
query.ColumnSet = new ColumnSet(true);
LinkEntity link = query.AddLink("teammembership", "teamid", "teamid");
link.LinkCriteria.AddCondition(new ConditionExpression("systemuserid", ConditionOperator.Equal, UserID));
try
{
return service.RetrieveMultiple(query);
}
catch (Exception ex)
{
// Do your Error Handling here
throw ex;
}
}
The code is the following:
public static bool IsTeamMember(Guid teamID, Guid userID, IOrganizationService service)
{
QueryExpression query = new QueryExpression("team");
query.ColumnSet = new ColumnSet(true);
query.Criteria.AddCondition(new ConditionExpression("teamid", ConditionOperator.Equal, teamID));
LinkEntity link = query.AddLink("teammembership", "teamid", "teamid");
link.LinkCriteria.AddCondition(new ConditionExpression("systemuserid", ConditionOperator.Equal, userID));
var results = service.RetrieveMultiple(query);
if (results.Entities.Count > 0)
{
return true;
}
else
{
return false;
}
}
Today I need to get all activities related with a specific user. The way it to easy: We can use FetchXM or Query Expression. I usually prefer use Query Expression.
The code is easy:
private List<Entity> GetAssociatedActivities(EntityReference regarding)
{
QueryExpression query = new QueryExpression { EntityName = "activitypointer", ColumnSet = new ColumnSet(new string[] { "activitytypecode" }) };
query.Criteria.AddCondition("regardingobjectid", ConditionOperator.Equal, regarding.Id);
query.Criteria.AddCondition("statecode", ConditionOperator.NotEqual, 1); //ignore completed
EntityCollection collection = _sdk.RetrieveMultiple(query);
return collection.Entities.ToList();
}
That’s all.
Today I had a timeout error on my application when I tried to use PublishAllXmlRequest .I resolved to use a single PublishXmlRequest in this way:
#region Publish FormXMl
//Publish entity for which formxml has been changed
PublishXmlRequest publishRequest = new PublishXmlRequest();
publishRequest.ParameterXml ="<importexportxml>" +
" <entities>" +
" <entity>" + entityName + "</entity>" +
" </entities>" +
" <nodes/>" +
" <securityroles/> " +
" <settings/>" +
" <workflows/>" +
"</importexportxml>";
try
{
organizationService.Execute(publishRequest);
}
catch (Exception ex)
{
throw new ex
}
#endregion
Today I start to create a tool to help me with some ordinary activity in the upgrade process to CRM2016. I needed a way to migrate DCP entity in the Mail Merge Template. The first problem that I found, is the possibility to enable “Note” in the entity and the second problem was to insert the Note Area inside the main form. The check of the property inside the entity is not enough because we need to edit manually the form. The ckeck enabled the Note Button in edit Form:
I wanted an automatic process. After scounting I found this solution:
private void EnableMailMergeTemplateAnnotation(IOrganizationService service)
{
//Check if note area exists in the entity
if (CheckNoteExist(service))
{
Log.Info("Enable Note - the note panes exists in the form ...");
}
else
{
//Get Entity Metadata for the entity mailmergetemplate
RetrieveEntityRequest retrieveBankAccountEntityRequest = new RetrieveEntityRequest
{
EntityFilters = EntityFilters.Entity,
LogicalName = "mailmergetemplate"
};
RetrieveEntityResponse retrieveMailMergeTemplateMetaData = (RetrieveEntityResponse)service.Execute(retrieveBankAccountEntityRequest);
EntityMetadata mailMergeTemplate = retrieveMailMergeTemplateMetaData.EntityMetadata;
// Enable Notes
UpdateEntityRequest enableNoteRequest = new UpdateEntityRequest
{
Entity = mailMergeTemplate,
HasNotes = true
};
service.Execute(enableNoteRequest);
//Update Form
UpdateEntityForm("mailmergetemplate", service);
//Publish Update
PublishAllXmlRequest publishRequest = new PublishAllXmlRequest();
service.Execute(publishRequest);
}
}
public void UpdateEntityForm(String entityLogicalName, IOrganizationService service)
{
QueryExpression q = new QueryExpression("systemform");
q.ColumnSet = new ColumnSet("formxml");
q.Criteria.AddCondition(new ConditionExpression("type", ConditionOperator.Equal, 2));
q.Criteria.AddCondition(new ConditionExpression("objecttypecode", ConditionOperator.Equal, "mailmergetemplate"));
var entities = service.RetrieveMultiple(q);
if (entities != null)
{
string mainForm = entities.Entities.First().Attributes["formxml"].ToString();
// Definition of a custom tab containing the custom attributes created in this sample
String noteRow = @"<row/>
<row/>
<row>
<cell id=""{33537195-ad98-07d8-7267-2e93e712905d}"" showlabel=""true"" rowspan=""15"" auto=""false"" colspan=""2"">
<labels>
<label description=""Note Text"" languagecode=""1033"" />
</labels>
<control id=""notescontrol"" classid=""{06375649-c143-495e-a496-c962e5b4488e}"" />
</cell>
</row>
<row />
<row />
<row />
<row />
<row />
<row />
<row />
<row />
<row />
<row />
<row />
<row />
<row />
<row />
</rows>
</section>
<section name=""Categorization""";
if (mainForm.Contains("notescontrol"))
{
Log.Info("Note exists in the form...");
}
else
{
string newForm = mainForm.Replace("</rows></section>
<section name=\"Categorization\"", noteRow);
//Updateing the entity form definition
entities.Entities.First().Attributes["formxml"] = newForm;
//saving the bank account form
service.Update(entities.Entities.First());
}
}
}
And with this code my life is more easy.
Today I needed to get the Current User inside a workflow activity. In CRM 2001 process it is not possible to get current user and in some cases a reference can be necessary in order to set the right user.
A Custom Workflow Activity can be created for this purpose, taking advantage of the InitiatingUserId property.
public class GetCurrentUser : CodeActivity
{
[Output("Current User")]
[ReferenceTarget("systemuser")]
public OutArgument<EntityReference> CurrentUser { get; set; }
protected override void Execute(CodeActivityContext context)
{
IWorkflowContext workflowContext = context.GetExtension<IWorkflowContext>();
CurrentUser.Set(context, new EntityReference("systemuser", workflowContext.InitiatingUserId));
}
}
Now from our workflow activity we have the current user.
Sometimes I need to search what is a database associated at an existing organization. It is simple: From CRM Server, we need to ope SQL Server tools and execuete this query:
By running this query within MSCRM_CONFIG database we should be able to easily identify each organization:
SELECT [DatabaseName]
,[FriendlyName]
,[SqlServerName]
,[SrsUrl]
,[State]
,[UniqueName]
,[UrlName]
,[IsDeleted]
FROM [MSCRM_CONFIG].[dbo].[Organization]
That’s all…
I migrated the solutions from CRM2011 to CRM2013 but I found a big problem with Multilookup: It does not work… I tryed to use the solution inside this post https://mscrmmindfire.wordpress.com/2014/05/20/crm-2013-manipulate-look-up-to-show-multiple-entity-record/ but does not work..
Customer type Lookups in Dynamics CRM have always been an interesting and powerful feature that allows you to associate records of multiple entities with entities like Cases, Orders, etc. PartyList Lookups are similar to Customer type lookups, except for the fact that it allows you to have access to a vast array of entities. They are generally available in Activities like Appointments, Phone Calls, etc.
Sometime or the other, you might have had the requirement to modify customer type lookup in CRM to restrict records to a particular entity. For example, you might want to restrict the end user from selecting Accounts while placing an Order from the “Customer” Lookup. Well, there’s a way to achieve that in CRM using JavaScript. It isn’t exactly a supported one. But chances of Rollups breaking it is very less.
Things are a bit different in CRM 2013. In CRM 2011 and even CRM 4.o, the DOM was a litte bit different. But CRM 2013 has its own brand new DOM structure. So, the code differs from that of CRM 2011. If you simply want to get to the code to implement, you can move directly to the next section. If you want to know why that code is required, read on.
Consider we want to restrict the Cusom lookup to a specific entity, Account. If you’re using Internet Explorer, press F12 to open up the Developer Tools. Search for “new_testfield_i” and you’ll find something as follows.
Now, this “new_testfield_i” is basically the magnifying glass image in the “TestField” lookup button. It consists some interesting properties that determine what entities will be displayed in the lookup form. However, we are interested in only a handful of them in order to get our job done. They are “lookuptypes”, “lookuptypeIcons”, “lookuptypenames” and “defaulttype”. Having a closer look at them pretty much explains what each property signifies.
So, now that we have identified what needs to be changed where, let’s get to the coding part of it. Basically, the idea here is to append “_i” after the Customer type lookup field name. Once you get that element, change its properties to get the desired result.
If you have followed the earlier section, you’d know why the following code snippet is required and what exactly it does. Just to be on the same page, the following code will allow only “Account” records to be displayed in the “Regarding” lookup field (in the Phone Call entity).
document.getElementById("new_testfield_i").setAttribute("lookuptypes", "1");
document.getElementById("new_testfield_i").setAttribute("lookuptypeIcons", "/_imgs/ico_16_1.gif");
document.getElementById("new_testfield_i").setAttribute("lookuptypenames", "account:1:Account");
document.getElementById("new_testfield_i").setAttribute("defaulttype", "1");
Well, don’t think it’s done yet! Although the above code might work most of the times, you might find it failing sometimes. Why? Because the entire DOM of Dynamics CRM 2013 is loaded in an asynchronous manner. Hence, the point where your script executes, the field “Regarding” might not have been rendered yet! Let’s add this small fix for it to work perfectly.
setTimeout(function() {
document.getElementById("new_testfield_i").setAttribute("lookuptypes", "1");
document.getElementById("new_testfield_i").setAttribute("lookuptypeIcons", "/_imgs/ico_16_1.gif");
document.getElementById("new_testfield_i").setAttribute("lookuptypenames", "account:1");
document.getElementById("new_testfield_i").setAttribute("defaulttype", "1");
}, 1000);
Now, that was if you wanted to restrict a Customer lookup field to a single entity. What do you do if you want to allow multiple entities, and restrict only a few? It’s simple. See the following code to get it.
setTimeout(function() {
document.getElementById("new_testfield_i").setAttribute("lookuptypes", "1,2");
document.getElementById("new_testfield_i").setAttribute("lookuptypeIcons", "/_imgs/ico_16_1.gif?ver=-475068199:/_imgs/ico_16_2.gif");
document.getElementById("new_testfield_i").setAttribute("lookuptypenames", "account:1:Account,contact:2:Contact");
document.getElementById("new_testfield_i").setAttribute("defaulttype", "1");
}, 1000);
The result now is as follows with Account and Contact being the only allowed Entities.
Today I need to execute a method every time open a Contact record.
Usually this would be frowned upon because this code could easily present a performance issues, especially if the data you’re gathering is hosted on an external resource.
In the off-change you do need to do this, here is the solution:
First, create a new Plugin and sign the assembly with a key:
public void Execute(IServiceProvider serviceProvider)
{
// Obtain the execution context from the service provider.
Microsoft.Xrm.Sdk.IPluginExecutionContext context = (Microsoft.Xrm.Sdk.IPluginExecutionContext)
serviceProvider.GetService(typeof(Microsoft.Xrm.Sdk.IPluginExecutionContext));
if (context.Depth == 1)
{
IOrganizationServiceFactory serviceFactory = (IOrganizationServiceFactory)serviceProvider.GetService(typeof(IOrganizationServiceFactory));
IOrganizationService service = serviceFactory.CreateOrganizationService(context.UserId);
// Obtain the target entity from the input parmameters.
EntityReference entity = (EntityReference)context.InputParameters["Target"];
ColumnSet cols = new ColumnSet(
new String[] { "lastname", "firstname", "address1_name" });
var contact = service.Retrieve("contact", entity.Id, cols);
if (contact != null)
{
if (contact.Attributes.Contains("address1_name") == false)
{
Random rndgen = new Random();
contact.Attributes.Add("address1_name", "first time value: " + rndgen.Next().ToString());
}
else
{
contact["address1_name"] = "i already exist";
}
service.Update(contact);
}
}
}
Next, hop over to the Plugin Registration Tool (included with the CRM SDK) and register the plugin:
What you’ll end up with in this example is:
On first open of the record:
On all future opens of the record:
