Hi,
Recently one of our users got the below error while trying to merge Lead record.
The user was having the Merge rights. However, the user was missing Share rights on the Lead entity. He already had create, write, delete, append and append to rights.
More details here
https://msdn.microsoft.com/en-us/library/gg334602.aspx?f=255&MSPPError=-2147217396
Giving Share rights fixed the issue.
Hope it helps..
We recently configured the Data Export Service and while creating the export profile, some of the entities were not appearing there.
We had the Change Tracking Enabled for them.
This is what it was showing to us.
Trying after few hours we got all our entities there
I think it might be caching or there is some pull mechanism that took time to detect that change at the Data Export Service side. Not sure though.
Please drop your comments if you have also faced this and know the exact reason for that.
Hope it helps.
We would run into this issue while trying to connect to Dynamics 365 Version 9.0 from a client application.
It is because Customer Engagement Platform (version 9.0) only supports TLS 1.2.
More details here
How we can fix it à
We need to add the following line of code to our existing code
public static OrganizationServiceProxy GetOrganizationServiceProxy()
{
ClientCredentials clientCredentials = new ClientCredentials();
clientCredentials.UserName.UserName = "username";
clientCredentials.UserName.Password = "password";
// Set security protocol to TLS 1.2 for version 9.0 of Customer Engagement Platform
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
return new OrganizationServiceProxy(new Uri("https://orgname.crm.dynamics.com/XRMServices/2011/Organization.svc"),
null, clientCredentials, null);
}
Helpful post
Hope it helps..
We had this issue in past when we started getting below error in most of the entities of Click Dimensions.
The issue can occur if the password would have expired or changed for the Service Credentials account of Click Dimensions.
Go to Settings à ClickDimensions Settings à Service Credentials.
In our case it wasn’t changed but we were still getting the issue. The only way we were able to fix it was to specify a different account for the Service Credentials.
Hope it helps.
We got the below while sending SMS from Click Dimension. We were using Bulk SMS as our SMS connector for Click Dimension.
When we opened the Text Messages record we figured out that we were getting “The remove serve returned an error (403) Forbidden.
This occurred because we had our credit with Bulk SMS already consumed.
The issue got fixed when bought the credits again with Bulk SMS.
Hope it helps.
Hi,
Recently we had a requirement to convert Fetch XML query of certain views to SQL. Basically, we wanted to validate it again the source DB from which we push the data inside Dynamics 365.
For this we can use the below managed solution,
https://fetchxml2sql.codeplex.com/
The tool is built using Silverlight so will only work in IE.
The other tool is that we can use is one of the most useful plugins – Fetch XML Builder of XRM Tool Box.
Below video explains how to use them
https://www.youtube.com/watch?v=OESJxa3bwrU
And in case you’d feel like converting fetch xml to SQL we have
Hope it helps..
Nishant Rana's Weblog 