The error you're seeing (UnSupportedLanguageException
with language ID 1043) indicates that Dataverse tables created with Dutch as the default language aren't supported for this operation. The language ID 1043
corresponds to Dutch (Netherlands).
Here’s how you can address this:
- Set a Supported Language (e.g., English - 1033)
If possible, update the default language of your Dataverse environment to English (ID: 1033). This ensures compatibility with the API you're calling.
- Go to Power Platform Admin Center.
- Select the environment with the Dataverse tables.
- Under Settings > Languages, add or change the default to English (1033).
- Duplicate Tables in English
- Create a duplicate of the problematic tables but set the base language to English during creation.
- Migrate data from the Dutch tables to the new ones using Power Automate or Dataflows.
- Force Language Override (If Supported by API)
Some APIs allow specifying the language in the request body or header. Try explicitly setting the language to English like this:
{
"language": "en"
}
If no such parameter exists, this method won’t apply.
- Translate Table Fields
If the issue is related to specific fields, use Power Automate or custom code to translate the Dutch field names to English.
If changing the language isn’t feasible for the entire environment, consider raising a support ticket with Microsoft to inquire about Dutch language support timelines.
The error you're seeing (UnSupportedLanguageException
with language ID 1043) indicates that Dataverse tables created with Dutch as the default language aren't supported for this operation. The language ID 1043
corresponds to Dutch (Netherlands).
Here’s how you can address this:
- Set a Supported Language (e.g., English - 1033)
If possible, update the default language of your Dataverse environment to English (ID: 1033). This ensures compatibility with the API you're calling.
- Go to Power Platform Admin Center.
- Select the environment with the Dataverse tables.
- Under Settings > Languages, add or change the default to English (1033).
- Duplicate Tables in English
- Create a duplicate of the problematic tables but set the base language to English during creation.
- Migrate data from the Dutch tables to the new ones using Power Automate or Dataflows.
- Force Language Override (If Supported by API)
Some APIs allow specifying the language in the request body or header. Try explicitly setting the language to English like this:
{
"language": "en"
}
If no such parameter exists, this method won’t apply.
- Translate Table Fields
If the issue is related to specific fields, use Power Automate or custom code to translate the Dutch field names to English.
If changing the language isn’t feasible for the entire environment, consider raising a support ticket with Microsoft to inquire about Dutch language support timelines.