Deployment pipeline problems with Live Connect

[Mary78]

HI all

I´m having problems with Live connect semantic model when using Deployment pipeline.
Things work as they should if I in desktop, connect one of the tabular models dev, tst or prd and publish to coresponding WS and connect to gateway. But things stopp working if I deplopy dev to tst or tst to prd (with corrct rule).
I´m getting this:
Error executing the query because the cube or some internal structures have not been processed (or do not exist).

There are some columns in dev & tst that don´t exist in prd can this be the issue?

Best regards
/Måns

[rohit1991]

Hi @Mary78

The error means Power BI couldn’t load or process the semantic model because the production version doesn’t match the schema from dev/test. Even small differences in tables, columns, or internal structures cause it. 

To fix it:

1. Make sure the semantic model schema is identical across environments before deploying.

2. After deployment, process or refresh the model in the target workspace so internal structures are rebuilt. 

3. Double-check your deployment rules and gateway mappings to ensure they're pointing to the correct datasets.

[Akash_Varuna]

@Mary78 Yes, schema mismatches can cause issues even with Live Connect. Ensure schemas are consistent across environments, process the dataset after deployment, and verify that deployment rules and gateway mappings are correct.

[Mary78]

@Akash_Varuna Big thanks for answer, are you sure this is also true when using a "live connect" not import?

[Akash_Varuna · Accepted solution]

Hi @Mary78 The issue occurs because the prd environment's semantic model has missing columns compared to dev and tst, leading to schema mismatches and unprocessed internal structures.The schema mismatches leads to this kind of error.

To resolve this, align the schema across environments or adjust queries to avoid referencing missing columns. After deployment, process the model in the prd workspace to update internal structures. Also, verify that Deployment Pipeline rules and Gateway configurations are correctly mapped to the respective environments.