Filter Required/Regarding (partylist data type) fields using JavaScript in Dynamics 365 / MS Dynamic CRM

What is Issue?

Sometimes we need to filter out the lookup fields according to business requirement. So generally we try to apply custom filter using client side scripting (JavaScript). This filtration works for normal lookup fields (datatype Lookup), but when it comes to fields like Regarding object,Required,Optional fields (PartyList Datatype fields) on Activity forms(Appointments/Phone call) the script fails. It won’t filter the field continues to show default results for Accounts .

The Reason-

You will face this issue because the party list shows the results for all the entities like Accounts, contacts, lead,User and depending on the entity selected in “Look for” in Lookup More result window.

Solution-

The Solution for this issue is to set the “Look For” value before filtering the lookup to limit the search according to business requirement. Use the following code to set the “Look For” in Lookup More Window-

LookFor

This will set Look For as well as will apply the custom filter to your field.

Enjoy MS CRM!!!

Ms Dynamics 365 :Plugin registration tool – Not able to connect to CRM Organization

What is the Issue?

When we try to connect MS Dynamics365 latest version (v9) using plug-in registration tool , it won’t connect the organisation showing some errors like-
1.pluginreg1

2.You don’t have permission to access any of the organizations in the Microsoft Dynamics CRM Online region that you specified. If you’re not sure which region your organization resides in, choose “Don’t know” for the CRM region and try again. Otherwise check with your CRM administrator.

The Reason-

The reason for these two errors are very different-

For issue 1- You don’t have latest version of sdk /Plugin registration tool.

For issue 2- You  are trying to connect to the org from the your private network with some particular domain.

Solutions-

Solution according to the issues-
For issue 1-
Download the latest plugin registration tool.
1. You can use msdn in which microsoft has provided power shell command to download the tool.
OR
2. Follow the step->
-Open Visual Studio
-Add new Project -> Class Library
-Right click on Project in Project explorer.
-Click on Manage Nuget Packages.
pluginreg2
-Search online for
Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool
PluginReg3
– Install the Nuget package and Close the window.
OR
-Alternative way to install nuget package you can use PM Console in Visual Studio-
-Use the following command-
PluginReg4
-This will download the latest Plugin Registration tool which needs to connect MS Dynamics 365 (V9.0)
-Now Open the Solution Location –
pluginreg5
-Navigate Location –
packages\Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.9.0.2.3\tools\
– You will find the plug in registration tool with latest SDKs.

Use this latest tool to connect MS Dynamics 365.

For issue 2-
If you are trying to connect CRM org with latest Plugin registration tool in your private network with some particular domain you will face the 2nd issue mentioned above.
To solve this issue you just need to open file “PluginRegistration.exe.config”
pluginreg6


And add the following Tag under the <Configuration> tag-
pluginReg7

Save file and close.
Now close the Plugin  Registration tool if any open and again start the tool. You will be able to connect your MS Dynamics 365 Organization.
Hope, this will help you.

C#: Unable to connect Dynamic365

What is the issue?

While coding with C#, developers struggles to connect with Dynamics 365. OrganizationService/ OrganizationServiceProxy object contains null and connection fails.

The Reason-

The reason behind this issue –
1. dll support
2. Wrong Connection String
3. Configuration settings
4. SSL/TLS setting

Solution-

solution according to the reason-
1. dll Support-
You should know which dlls are supported to connect Dynamics 365.
Many times the CRM versions differs and due to CRM upgrades the dlls used becomes outdated for new Versions. Currently many developers faces this issue if you are using Dynamics365 online version . Current version of CrmSDK is V9.0.0.7. and this should be used.
You can add reference of CrmSDK by using Nuget Package Manager-

NuCrmSDK

You can change the version according to recent updates by Microsoft.
2. Connection String-
Wrong connection string might be the problem and for Dynamics 365 online version you can use connection string like-

"https://<YourOrgName>.api.<CRMRegion>.dynamics.com/XRMServices/2011/Organization.svc"

<YourOrgName>– This is your Organization Name.
<CRMRegion>– This is the Region you choose while creating organization.

Also you can find this string navigating Customization-> Developer Resources in Dynamics 365.

Other way to connect CRM is providing each parameter Separately like-

 Microsoft.Xrm.Tooling.Connector.CrmServiceClient conn = new CrmServiceClient(uName, pwd, "NorthAmerica", _crmOrganizationName, isOffice365: true);

Also you need to provide Username and password(converted to secured password) Properly.
3.Configuration Settings-
Many times application throws an exception like “Metadata contains a reference that cannot be resolved” .
You provides the connection string properly, every thing is correct but still you found the OrganizationService/ OrganizationServiceProxy showing null.
This happens in some particular domain networks. In this case you have to enable the Proxy setting and for this add the following tag under the configuration tag to your Web.Config /app.config file-

<system.net>
<defaultProxy useDefaultCredentials=”true” enabled=”true”>
</defaultProxy>
</system.net>

This will only use the credentials provided by you in connection string.
4. SSL/TSL settings-
Your application fails to connect Dynamics365 CRM if it is using some particular security protocol. To connect successfully , you need to explicitly mention the security by adding the following line just before the connection establishment lines-

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

Use Tls12/SSL/Tls11 according to security protocol used by Dynamics365 .

Hope this will be helpful to connect your organization.

Changes not reflecting on forms while importing managed solution to organization in MS Dynamic CRM

What is the Issue?

After importing managed solution to the organization, changes on the forms not reflects.
Example- MS Dynamic CRM developer made some changes on form which is already exists in organization,like changed display name of field on form or added some function on onChange event of some field, but when imported this changes through managed solution the labels not changed or function is not added on OnChange Event of field.

The Reason-

You will face this issue in case of unmanaged changes over managed entities in the organization.These managed entities maintains the customization even after importing new changes.

Solution-

We can divide the issue in two parts.
1. New events added to the form components.
2. The exiting field properties changed on the form.

The solution for issue 1-
These changes can be moved overwriting existing the managed solution which already contains the entity form which you want to update.

The solution for issue 2-
The simple solution for the first issue is to add new tab on form and move the updated fields to the new tab and format this tab as previous one.
Also, In this case, you can move the changes using same way mentioned for issue 1.

These both issues will never occur if you maintain the version of managed solution.
While deploying changes to MS Dynamic CRM try to maintain the version of managed solution.You can avoid creating new solution each time.It will avoid many failures which occurs during solution import or the updates on entities.

To maintain version and version history using the ‘Description’ and ‘Version’ fields of solution Information.

ImportManagedSolution

Asynchronous Processes/Wrokflows Stuck in InProgress/Waiting status in MS Dynamic CRM

What is the Issue?

CRM developer/User once in a life faces the issue regarding Asynchronous Processes stuck in same status i.e. InPrgress/Waiting/Pausing/Canceling.You can see the system job status is not changing.

AsyncWF

The Reason-

The main reason behind this issue  –

  1. Many jobs are in waiting status.
  2. Asyncoperationbase table become full due to many succeeded/canceled jobs occupied space.
  3. Asynchronous processes settings are not proper.
  4. The asynchronous workflows are not configured properly.

Solution-

The solution for this issue –

  1. Very first step is to restart the  Microsoft Dynamics CRM Asynchronous Processing Service. This might work in many cases.
  2. Many Jobs are in waiting status->
    you can update the job status to canceled and completed by creating console application or from database-
    a. Create the console and use the script –
    CancelWFProgramatically
    b. Using Database Query-
    Note- You should create restore(Checkpoint) point first before working on database directly to rollback changes if needed.
    CancelWFDB
    You can use “where statusCode=10 –Waiting”.
  3. Asyncoperationbase table become full due to many succeeded/canceled jobs occupied space –
    You need to cleanup the database by deleting the succeeded and canceled jobs-
    Make sure that only the following Async operation types are deleted if the state code of the types is 3 and the status code of the types is 30 or 32:

    • Workflow Expansion Task (1)
    • Collect SQM data (9)
    • PersistMatchCode (12)
    • FullTextCatalogIndex (25)
    • UpdateContractStates (27)
    • Workflow (10)

    CleanupScript
    If script took very long time then you should stop the script and rebuild the indexes for AsyncOperationBase as well as PrincipalObjectAccess tables. And run the script again.

  4. You can check if the values are optimal-
    • AsyncItemsInMemoryHigh
    • AsyncItemsInMemoryLow
    • AsyncStateStatusUpdateInterval
    • AsyncMaximumThreadsPerCPU
    • AsyncSelectInterval
    • AsyncSelectParallelism
    • AsyncThrottlingConfiguration
    Also you can check the ‘AsyncSdkRootDomain’ setting from  [MSCRM_CONFIG].[dbo].[DeploymentProperties]
    WFsetting1
    Recommended value of ‘AsyncSdkRootDomain’ should be same as ‘ADSdkRootDomain’. Or you can put server name as value.
    WFsetting2
  5. And Finally you can check your asynchronous work flow logic.
    There are many possibilities the workflows are stuck due to internal logic.

You have to restart the  Microsoft Dynamics CRM Asynchronous Processing Service after executing any above step.