microsoft / microsoft/Dataverse-skills
update_table fails in non-English environments: "The language code 1033 is not a valid language for this organization"
- Dominant language
- No language data
- Stars
- 226
- Forks
- 61
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 7
Description
**Setup:** Plugin `dataverse` 1.10.0 (claude-plugins-official, Claude Code), CLI `@microsoft/dataverse` 1.0.63 as stdio proxy against the GA endpoint (`/api/mcp`).
**Environment:** Dataverse environment with base language **German (1031)**, English not enabled.
**Repro:**
1. `create_table` with a string column → **works fine**, labels are created correctly in the org's base language.
2. `update_table` on the same table, adding one integer column (with `newDisplayName` supplied) → fails:
> The language code 1033 is not a valid language for this organization (correlation ID: 605c95f8-3792-42fa-9975-d16d0e1b6c45)
**Expected:** Labels for added columns should use the organization's base language, as `create_table` already does.
**Impact:** Adding columns to existing tables is impossible in any organization whose base language is not 1033 (English) — which is the default situation for most non-US customers. Since `create_table` handles the locale correctly, the hardcoded LCID seems specific to the add-column path of `update_table`.
Contributor guide
Research direction
Start with the update_table add-column path and compare its label-language handling with create_table, using the reported German (1031) Dataverse environment and reproduction steps. Confirm the change by adding a column with newDisplayName and verifying that labels use the organization’s base language without the 1033 error.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100