Since OData endpoint was released with CRM 2011 I used CRM OData Query Designer developed by MVP fellow Rhett Clinton. Today I was working on brand new online instance of CRM 2015 and… I was not able to import lovely tool into CRM with message that solutions developed for CRM 2011 could not be imported into CRM 2015. I started to look for alternatives and found brilliant solution developed by other MVP fellow – Jason Lattimer. The great advantage of CRM REST Builder is that you can get complete code of calls using different frameworks developed for Dynamics CRM. So try, use and love this tool – CRM REST Builder.
Thursday, December 25, 2014
Wednesday, October 08, 2014
Microsoft CRM 2013: Currency exchange rates actualization
In this article I will share with small add-on I developed for one of my customers.
Let’s assume that you are employee of company that uses CRM with several currencies. Of course you want to have actual information in your system and currency exchange rates should be current. Microsoft CRM allows to have in system one base currency and many other currencies. Every currency has exchange rate field that is used for calculation of base fields of your currency fields but there is no out-of-box possibility to actualize exchange rates.
Let’s assume that you are employee of company that uses CRM with several currencies. Of course you want to have actual information in your system and currency exchange rates should be current. Microsoft CRM allows to have in system one base currency and many other currencies. Every currency has exchange rate field that is used for calculation of base fields of your currency fields but there is no out-of-box possibility to actualize exchange rates.
Labels:
Custom Workflow,
Microsoft CRM 2013,
Workflow
Saturday, September 27, 2014
Reporting for Dynamics CRM: Error while loading code module: “Microsoft.Crm.Reporting.RdlHelper…”
Let’s assume that you’ve created report for Dynamics CRM using Report Wizard and opened it with BIDS to add changes that are not available with Report Wizard (it could be anything – adding of images, change of fonts or layout…).
Once you’ve opened a report and applied change of course you want to recheck changes. In case you will get error that is shown on following screenshot you can find steps that will allow to build and test report in BIDs without any issues:
Once you’ve opened a report and applied change of course you want to recheck changes. In case you will get error that is shown on following screenshot you can find steps that will allow to build and test report in BIDs without any issues:
Friday, June 13, 2014
Dynamics CRM 2013: Step-by-step creating dialog windows
In my previous post I shared how to use Microsoft CRM internal function to show dialog window in Dynamics CRM 2013 inline style. In this post I will write step-by-step guide how to build own dialogs in CRM 2013 style.
Labels:
Java Script,
Microsoft CRM 2013,
Undocumented,
Unsupported
Monday, May 26, 2014
Show your dialog in CRM 2013 modal style
With CRM 2013 we have got one working window without any pop-up windows (lookups, dialogs, e.t.c.). But… only for standard features. What to do in case you wanted to use the same approach with modal windows as CRM does it? I walked through SDK and found following article - http://msdn.microsoft.com/en-us/library/jj602956.aspx#BKMK_OpenWebResource. I tried the code but I have got wrapped window.open method. After some investigations I found how CRM does it:
if (typeof Custom == "undefined") { Custom = { OpenDialog: function (webresource) { var $v_0 = new Mscrm.CrmDialog(Mscrm.CrmUri.create(webresource), window, 370, 370, null); $v_0.show(); }, __namespace: true }; }
and usage is following:
Custom.OpenDialog("/webresources/new_webresource.htm");
You can use this approach but remember that this code uses undocumented methods so it could be broken with any rollup.
Labels:
Java Script,
Microsoft CRM 2013,
Undocumented,
Unsupported,
WebResource
Tuesday, February 18, 2014
Monday, February 10, 2014
MS CRM 2013: OOB BingMaps control shows ‘click here to view map’ – what to do?
This article can help you to activate this feature for On Premise deployment only! This would not work for Online!
If you see something similar when you open your CRM Organization that means that for some reason MS decided to limit your possibility to see location of contact, account or other record on map:
To fix it do following steps:
1. Connect to SQL Server where DBs are located.
2. Open SQL Management Studio and execute following query against your CRM DB:
That will give you locale code of your organization. Now you need to convert this value to culture name (for example using this post) – in my case ru-RU.
3. Execute following query against MSCRM_Config DB:
That will give you the list of locales for which BingMaps would work (in my case it was cs-CZ;da-DK;nl-BE;nl-NL;en-AU;en-CA;en-IN;en-GB;en-US;fi-FI;fr-CA;fr-FR;de-DE;it-IT;ja-JP;nb-NO;pt-BR;pt-PT;es-MX;es-ES;es-US;sv-SE).
4. Write and execute script to update list of locales using following template:
In my case:
5. Make iisreset and try to open form where bingmaps was not shown before. If you’ve done everything right map had to appear:
PS This modifications are unsupported and mentioned changes can harm your deployment. Use it own risk.
If you see something similar when you open your CRM Organization that means that for some reason MS decided to limit your possibility to see location of contact, account or other record on map:
To fix it do following steps:
1. Connect to SQL Server where DBs are located.
2. Open SQL Management Studio and execute following query against your CRM DB:
Select LocaleId From Organization
3. Execute following query against MSCRM_Config DB:
Select NVarCharColumn From ServerSettingsProperties Where ColumnName = 'AvailableBingMapLocales'
4. Write and execute script to update list of locales using following template:
Update ServerSettingsProperties Set NVarCharColumn = 'Value from step 3;Value from step 2' Where ColumnName = 'AvailableBingMapLocales'
Update ServerSettingsProperties Set NVarCharColumn = 'cs-CZ;da-DK;nl-BE;nl-NL;en-AU;en-CA;en-IN;en-GB;en-US;fi-FI;fr-CA;fr-FR;de-DE;it-IT;ja-JP;nb-NO;pt-BR;pt-PT;es-MX;es-ES;es-US;sv-SE;ru-RU' Where ColumnName = 'AvailableBingMapLocales'
PS This modifications are unsupported and mentioned changes can harm your deployment. Use it own risk.
Labels:
BingMap,
Microsoft CRM 2013,
T-SQL,
Trick,
Unsupported
Subscribe to:
Posts (Atom)




