Skip to main content

Posts

Async Plugins vs. Power Automate Flows

CRM 2013: fn_GetLocalizedLabel in custom CRM SQL Report and LabelTypeCode parameter

Today I tried to migrate a custom CRM 4.0 SQL report to the a CRM 2013 SQL report. In the report designer I hit the preview button and received the following error: TITLE: Microsoft SQL Server Report Designer ------------------------------ An error occurred while executing the query. An insufficient number of arguments were supplied for the procedure or function dbo.fn_GetLocalizedLabel. OK, this means the SQL function "fn_GetLocalizedLabel" in CRM 4.0 used to have one parameter less than in CRM 2011 or CRM 2013. After comparing the paramter signatures with the SQL database version I found this definition: function [ dbo ].[ fn_GetLocalizedLabel ] (     @ ObjectId uniqueidentifier ,     @ ColumnName nvarchar ( 255 ),     @ LabelTypeCode int ,     @ LanguageCode int ) returns nvarchar ( 255 ) as begin     declare @ LocalizedLabel      nvarchar ( 255 )   ...

CRM 4.0: Update Rollup for MUI resets the user language settings after reprovisioning language pack

This week I had to install the UR21 on an old CRM 4.0 environment. I think it is very annoying to update every language pack for multiple CRM instances. And it gets even worse when you have to reprovision every language pack on like 10 different instances. Sure you could develop a tool that could do it for you, but it not worth as soon the customer will switch to CRM 2013. Finally, all languages were reprovisioned for each instance. But guess what happened now. All the user's language settings had been put back to the default language of the CRM instance. Now this will **** my customer off. Especially if you have some from a Western Europe country ;) Anyway, I had to find a quick and unsupported way to resolve this mess. Evoilá this is the script that made my day: UPDATE [ORGANIZATION_MSCRM].[dbo].[UserSettingsBase]    SET       [UILanguageId] = 1053       ,[HelpLanguageId] = 1053   ...