CRM 2016 – Page 11 – Nishant Rana's Weblog

Using Advanced Rest Client with Web API in CRM 2016

Hi,

To test Web API query we can make use of Advanced Rest Client chrome extensions.

https://chrome.google.com/webstore/detail/advanced-rest-client/hgmloofddffdnphfgcellkdfbfbjeloo

Get the Service Root URL

Launch Advanced Rest Client in Chrome
Put the URL copied.
Here we would also need to set headers, content type and Authorization.

To get the Access token
Log in to https://xrm.tools/AccessToken with your CRM Credentials.
Select CRM Organization

Copy the Access Token and use it for Authorization Header in Advanced Rest Client

Click on Send and to get the response

Update the query and click on SEND

More details here

https://msdn.microsoft.com/en-us/library/gg334767.aspx

Hope it helps.

New Features CRM 2016 Update 1 – Customer attribute

Hi,

With CRM 2016 Update 1 now we have got this option of creating custom attribute of data type Customer for any entity à system as well as custom.

This in turn will create 2 new relationships with account and contact entity.

Hope it helps.

Fixed: Translations not working in a field in Header in CRM 2016.

Recently we faced a strange issue with translations. It was showing correct translated value in the Form, however the same field in the Header was showing the label in English instead of German.

In Development environment it was working properly only in TEST we were facing this issue after deployment.

Then just to give it a try, I opened the form for customization, removed the City field form Header and added it back and did publish.

Surprisingly it started showing correct translated label in the header.

Hope it helps..

The ‘distinct’ attribute is not declared error while trying to import solution in CRM 2016 (and earlier)

Hi,

Got this error while trying to import a managed solution in CRM 2016 Online.

During analysis we figured out that it was pointing to one of the charts created for System User Entity. It seemed like chart’s xml was modified after export and then imported. The xml definition of the chart contained distinct keyword.

Removing the distinct keyword from the Chart definition and importing it back and then importing the managed solution with this updated chart got imported without any error.

Hope it helps..

Fixed: Cannot add a Root Component 00000000-0000-0000-0000-000000000000 of type 20 because it is not in the target system error while importing managed solution in CRM 2016.

Hi,

Today we faced this issue while importing managed solution extracted from our Dev Environment to Test Environment (CRM 2016 Online Update 1).

As suggested by few of the posts online, the culprit was the System Customizer role. We removed it from our solution and then imported it back and it got imported successfully.

Helpful Post

http://crmkid.com/tag/cannot-add-a-root-component/

Hope it helps..

IPluginExecutionContext Depth is 2 in Create Plugin during Import of records in CRM 2015 (and earlier)

We had one of our plugins on Create of Opportunity however during the import of the Opportunity record it was not working properly. We had the Depth check in our plugin code to check for infinite loop as the same plugin was being used for Update also.

After some debugging we realized that Depth value is 2 instead of 1 during import.

To test this, we created a sample plugin for create of Test entity record and then imported the Test entity records.