Skip to main content

XrmToolBox: AutoNumberUpdater - new StateCode filter

CRM 2013: The language code is not a valid language for this organization

Lately it occurred that a CRM 4.0 was upgraded to CRM 2011 and to CRM 2013 afterwards.
When working with solution import and export under 2013 it happened that this error occurred while trying to reimport a modified unmanaged solution to the same organization:
The language code xxxx is not a valid language for this organization.
This error is due to the fact that the language packs from the CRM 4.0 system were never been uninstalled properly before the migration was done.

A temporary unsupported workaround can be achieved by the following steps:

- Open Organization_MSCRM database
- Open Table MetadataSchema.OrganizationLanguagePack in Edit mode

In the picture below you can see that all languages are set to enabled in the column "IsEnabled".



- Go back to CRM and try to import and publish your solution again
- After success go back to SSMS and disable all languages of version 4.x or 5.x

Comments

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...

Power Automate: Avoid Apply to Each for List rows action (DataVerse)

If you do not want to use the Apply to Each loop after a Dataverse List rows action you can use the following in a Dynamic Content / Expression box to directly use a field's value in e.g. Compose action: first(outputs('List_rows')?['body/value'])?['apx_fullpath'] instead of apx_fullpath you can use whatever field name you need for the entity that's been queried before.

How to add your personal PowerBI Dashboard as a system dashboard

New Approach: Attention: Microsoft added this feature out of the box, so that the manual approach below is not required anymore. More to this can be found here: https://powerapps.microsoft.com/en-us/blog/power-bi-embedded-as-system-dashboard-in-model-driven-apps-preview/ Old Approach: The general guideline on how to create a personal dashboard is described in this article: https://docs.microsoft.com/en-us/powerapps/user/add-powerbi-dashboards But what if you want to rollout a global PowerBI dashboard for all users? With some tweaks you can manage it to make it work… 1. After you have created your personal dashboard you need to extract the formxml of that dashboard with this URL query in a browser tab: https://org.crm4.dynamics.com/api/data/v9.1/userforms?$select=name,formxml&$filter=type eq 103 and name eq 'Ticket Status' Replace… type = 103 => PowerBi Dashboard name = 'Your PowerBI Dashboard Name' In the result copy the XML part out of the "formxm...