Skip to main content

XrmToolBox: AutoNumberUpdater - new StateCode filter

Post a Comment

CRM 4.0: Unable to re-provision CRM 4.0 MUI after UR10 to UR21 upgrade

Today I tried to re-provision the CRM 4.0 MUI after an UR21 Upgrade coming from UR10.

Sadly, every time trying to provision the language I retrieved an error. Turning on the error log this allowed me to find the real problem that I was facing here:

Violation of PRIMARY KEY constraint 'XPKLocalizedLabel'. Cannot insert duplicate key in object 'MetadataSchema.LocalizedLabel'.

The error occured while trying to execute the follwoing SQL Statement:
INSERT INTO LocalizedLabel ( LocalizedLabelId,
LanguageId,
ObjectId,
ObjectColumnName,
Label,
InProduction,
CustomizationLevel ) VALUES ( '0bd8a218-2341-1033-898a-0007e9e17ebd',
1033,
'0ad8a218-2341-db11-898a-0007e9e17ebd',
'DisplayName',
'Preferred Customer',
1,
System )

checking on web search I found this page:
http://msdn.microsoft.com/en-us/library/ee704626.aspx

The page specifies the following allowed values for the CustomizationLevel column:

ValueDescription
0Indicates that the visualization is a system (out-of-box) visualization.
1Indicates that the visualization is a custom visualization. Custom visualizations are the newly created or modified visualizations.
2Indicates that the visualization is a deleted (but unpublished) visualization.

Next check I did was to see what the above ObjectId will show me on a table select:
select * from LocalizedLabel
 WHERE [ObjectId]='0ad8a218-2341-db11-898a-0007e9e17ebd'

This resulted in 4 rows, 2 in each language I have installed on the system.
Major difference was the CustomizationLevel columns, besides some GUIDs.
So I thought I compare this column with the table values (0, 1 and 2).
There was one entry per language that had the value 2. So this is some deleted or unpublished stuff.

Next step was to do a complete database backup, as my next action could have impacted the CRM system in a way that I do not want.

My guess was that the rows with CustomizationLevel = 2 cause some issues here.

Therefore I went ahead and shot off the following query:
 DELETE FROM MetadataSchema.LocalizedLabel WHERE customizationlevel = 2

The SSMS told me that 187 records where deleted. OK this might be good or bad.
Next step was to check my system.

Hey, there you go. I can now activate the second language again. No error any more.
Playing around a little with the system did not show any anomalies. Seems like this fixed it, but I will have to watch this in the near future.

At least the day was saved.



Labels:

Comments

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...
16 comments
Read more

Regarding SPFieldMultiLineText (Add HTML/URL content to a field) programmatically

I recently tried so set some HTML content in a SharePoint list column of type SPFieldMultiLineText. My first approach was this piece of code: SPFieldMultiLineText field = item.Fields.GetFieldByInternalName( "Associated Documents" ) as SPFieldMultiLineText; StringBuilder docList = new StringBuilder(); docList.Append( " " ); foreach (DataRow docRow in addDocs) { DataRow[] parent = dr.Table.DataSet.Tables[0].Select( "DOK_ID=" + docRow[ "DOK_MGD_ID" ].ToString()); if (parent != null && parent.Length > 0) { docList.AppendFormat( " {1} " , parent[0][ "FilePath" ].ToString(), parent[0][ "Title" ].ToString()); } } if (docList.Length > 0) { // remove trailing tag docList.Remove(docList.Length-5, 5); } docList.Append( " " ); string newValue = docList.ToString(); item[field.Title] = newValue; What this code does is to get all associated documents to the main document and to add these docu...
1 comment
Read more

XrmToolBox: AutoNumberUpdater - new StateCode filter

Mayank Pujara's AutoNumberUpdater plugin for the XrmToolBox is a great tool to add missing auto number values to an auto number field for an entity/table. In his blog you can find more details about the original version of his plugin: https://mayankp.wordpress.com/2021/12/09/xrmtoolbox-autonumberupdater-new-tool/ For my purposes I had to update accounts with missing account numbers, but in my use case this should only be done for those accounts that have the status value "Active".   As this plugin did not have this feature I quickly implemented it and Mayank merged my changes to his plugin source code. You can download the new version 1.2024.0.1 in the Tool Library of the XrmToolBox.
Post a Comment
Read more