This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
I'm trying to change the model culture of an existing Power BI Project (.pbip) from en-US to de-DE. The model was originally created with en-US and I need to correct it afterward.
What I tried:
Changed Options > Regional Settings > Model language in Power BI Desktop. This was blocked (expected for an existing model).
Edited TMDL files manually:
Changed culture: en-US to culture: de-DE in model.tmdl
Renamed cultures/en-US.tmdl to cultures/de-DE.tmdl
Updated ref cultureInfo
Still received this error:
"Culture and Collation properties of the Model object may be changed only before any other object has been created."
Tried with an effectively empty model to bypass the restriction:
Kept only:
database.tmdl
model.tmdl
roles/
cultures/de-DE.tmdl
Removed:
tables/
relationships.tmdl
DAXQueries/
TMDLScripts/
diagramLayout.json
Also set Global Options > Model language = German (Germany).
Result: same error every time.
The log indicates Power BI recognized the model as empty:
Model Default Mode: Empty
Workbook Package Info: 1* - de-DE, Query Groups: 0
Is there a supported way to change the culture/model language of an existing PBIP/TMDL model after creation? If not, what is the recommended migration approach?
Solved! Go to Solution.
Try this. New PBIP from Scratch + TMDL Copy-Paste
This is the clean-room migration approach:
This is the most reliable TMDL-native approach, tbut it requires revalidating measures and relationships after the merge.
Proud to be a Super User!
Existing pbip cannot change its model‑culture and creating a new de‑DE pbip and moving the objects across.
Hi @P108
try to create a new Power BI model with the desired culture:
Create a new PBIP/PBIX file.
Before creating any model objects, set:
File → Options → Regional Settings → Model language = German (Germany) (de-DE).
Create the new model.
Migrate the existing content (queries, tables, relationships, measures, roles, calculation groups, etc.) to the new model.
Reconnect or migrate reports as needed.
For large models, tools such as Tabular Editor can significantly simplify the migration process by allowing metadata objects to be copied from the old model into the new one.
Try this. New PBIP from Scratch + TMDL Copy-Paste
This is the clean-room migration approach:
This is the most reliable TMDL-native approach, tbut it requires revalidating measures and relationships after the merge.
Proud to be a Super User!
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 23 | |
| 21 | |
| 21 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 55 | |
| 53 | |
| 45 | |
| 26 | |
| 24 |