Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.

Reply
P108
Frequent Visitor

changing the model culture of an existing Power BI Project (.pbip)

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:

  1. Changed Options > Regional Settings > Model language in Power BI Desktop. This was blocked (expected for an existing model).

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

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

1 ACCEPTED SOLUTION
VijayP
Super User
Super User

 
@P108 

Try this. New PBIP from Scratch + TMDL Copy-Paste

This is the clean-room migration approach:

  1. Create a brand new .pbip with Power BI Desktop's Global Options set to German (Germany) before adding any tables.
  2. In the new model's TMDL, culture: de-DE will be set from the start.
  3. Copy your table TMDL files from the old project's tables/ folder into the new project's tables/  folder.
  4. Copy relationships.tmdl , roles, and other artifacts across.
  5. Open the new .pbip in Desktop — it loads with de-DE from the beginning, so the engine won't reject the culture.

    This is the most reliable TMDL-native approach, tbut it requires revalidating measures and relationships after the merge.

 




Did I answer your question? Mark my post as a solution! Appreciate your Kudos!!
MY Blog || My YouTube Channel || Connect with me on Linkedin || My Latest Data Story - Ageing Analysis

Proud to be a Super User!


View solution in original post

3 REPLIES 3
Kagiyama_yutaka
Advocate III
Advocate III

Existing pbip cannot change its model‑culture and creating a new de‑DE pbip and moving the objects across.  

Future_To_BI
Resolver I
Resolver I

Hi @P108 

try to create a new Power BI model with the desired culture:

  1. Create a new PBIP/PBIX file.

  2. Before creating any model objects, set:

    • File → Options → Regional Settings → Model language = German (Germany) (de-DE).

  3. Create the new model.

  4. Migrate the existing content (queries, tables, relationships, measures, roles, calculation groups, etc.) to the new model.

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

VijayP
Super User
Super User

 
@P108 

Try this. New PBIP from Scratch + TMDL Copy-Paste

This is the clean-room migration approach:

  1. Create a brand new .pbip with Power BI Desktop's Global Options set to German (Germany) before adding any tables.
  2. In the new model's TMDL, culture: de-DE will be set from the start.
  3. Copy your table TMDL files from the old project's tables/ folder into the new project's tables/  folder.
  4. Copy relationships.tmdl , roles, and other artifacts across.
  5. Open the new .pbip in Desktop — it loads with de-DE from the beginning, so the engine won't reject the culture.

    This is the most reliable TMDL-native approach, tbut it requires revalidating measures and relationships after the merge.

 




Did I answer your question? Mark my post as a solution! Appreciate your Kudos!!
MY Blog || My YouTube Channel || Connect with me on Linkedin || My Latest Data Story - Ageing Analysis

Proud to be a Super User!


Helpful resources

Announcements
May Power BI Update Carousel

Power BI Monthly Update - May 2026

Check out the May 2026 Power BI update to learn about new features.

Fabric SQL PBI Data Days

Data Days 2026 coming soon!

Sign up to receive a private message when registration opens and key events begin.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.